Omnigent(@omnigent_ai):If you keep custom agents in a Git repo and run Omnigent on more than one machine, install an agent once with omnigent agent add and pick it from the new-session picker on every host you use. Until now, a custom agent only became available by running a session with its spec file, and it belonged to that session. Installed agents are stored on the server under your account, so they sit beside the built-in agents on every host, with no server restart. GitHub installs ask you to confirm first, since the repo’s config runs in your sessions. 👉 Learn more:

2026.10.23 14:48

If you keep custom agents in a Git repo and run Omnigent on more than one machine, install an agent once with omnigent agent add and pick it from the new-session picker on every host you use. Until now, a custom agent only became available by running a session with its spec file, and it belonged to that session. Installed agents are stored on the server under your account, so they sit beside the built-in agents on every host, with no server restart. GitHub installs ask you to confirm first, since the repo’s config runs in your sessions. 👉 Learn more: