Install a custom agent once from GitHub and use it on every host
If you keep custom agents in a Git repo and run Omnigent on more than one
machine, you can now 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 different: they are stored on the server under your account, so they sit beside the built-in agents on every host, with no server restart. Re-adding an agent with the same name replaces your copy in place, and sessions already using it pick up the new version on their next turn (terminal sessions when they relaunch). Workers, skills, guardrails, and supporting files in the agent directory all come along.
Point the command at a local agent directory, a YAML file, a .tar.gz bundle,
or a GitHub repo as owner/repo. For a repo, --list previews the agents it
contains, @name installs just one, and a /tree/<branch> URL pins a branch
or tag. GitHub installs ask you to confirm first, since the repo's config runs
in your sessions; --yes skips the prompt.
# List the agents in your GitHub repo (acme/agents is an example)
omnigent agent add acme/agents --list
# Install one agent from that repo by its name
omnigent agent add acme/agents@orion
# Install from a branch or tag of your repo
omnigent agent add https://github.com/acme/agents/tree/main/orion
# Install from a local agent directory you created
omnigent agent add ./orion
# List the agents you have installed
omnigent agent list
# Remove an installed agent
omnigent agent remove orionIn the web UI, open the agent picker's custom agents, choose Create custom
agent, then Import bundle and pick a .tar.gz of an agent directory. The agent
installs and is selected for the new session. See the
Custom Agents guide for how to write the agent
itself.
Enjoying Omnigent? If this is useful to you, give us a star on GitHub ⭐. Come say hi on Discord, or check the latest release.