Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/omnigent-ai/omnigent/llms.txt

Use this file to discover all available pages before exploring further.

Omnigent supports real-time multi-user collaboration on live agent sessions. Teammates can watch an agent work, send it messages, take over the keyboard, or branch off their own copy of a conversation — all without any extra infrastructure beyond the Omnigent server.
Teammates must be able to reach the server. A local server is only reachable on your local network. For anyone outside your network, deploy an always-on host — see the deployment guide.

​
Sharing a session

Hit Share in the web UI to get a shareable link to your current session. Anyone with the link (and an account on the same server) can open it in their browser and watch your agent work and chat with it in real time — messages, sub-agents, terminals, and files all stay in sync.

​
Co-driving

A teammate can attach to your running session from the terminal. Their messages execute on your machine, which is great for pairing or handing the keyboard to a domain expert mid-investigation: 
omnigent attach <session_id>
Replace <session_id> with the ID shown in the web UI or returned by omnigent server status. Both you and your teammate can send messages; the agent sees them in order.

​
Forking

Clone a conversation from any point and continue independently on your own machine: 
omnigent run --fork <session_id>
The fork picks up from the current state of the conversation. You get your own copy to explore a different direction, test a hypothesis, or replay the session with a different model — without affecting the original.

​
Setting up multi-user accounts

Multi-user mode is controlled by a single environment variable: 
OMNIGENT_AUTH_ENABLED=1 omnigent server start
The Docker deploy turns it on automatically — OMNIGENT_AUTH_ENABLED defaults to 1 in the Docker Compose config, so you don’t need to set it explicitly.

​
Inviting teammates

1

Sign in as admin

Open the web UI (e.g. http://localhost:6767) and sign in as admin. The password is printed on first run and saved locally.
2

Open the invite flow

Navigate to Admin → Members → Invite to create a single-use invite link. No email server is needed.
3

Send the link

Share the invite link with your teammate. They open it, set a password, and they’re in. Signup is invite-only — there is no self-registration.

​
SSO / OIDC

To let teammates sign in with the accounts they already have, set OMNIGENT_OIDC_ISSUER together with a client ID and secret on your deployed server and restart:
VariableExample value
OMNIGENT_OIDC_ISSUERhttps://accounts.google.com
OMNIGENT_OIDC_CLIENT_IDyour client ID
OMNIGENT_OIDC_CLIENT_SECRETyour client secret
Omnigent supports any standards-compliant OIDC provider, including Google, GitHub, Okta, and Microsoft. The deploy guide also covers domain allowlists and the header auth proxy mode for environments where Omnigent sits behind a reverse proxy that handles authentication.
For remote collaboration across the internet, deploy a server with a stable public URL. One docker compose up on any VPS is enough — see the deployment overview.

Build docs developers (and LLMs) love

Get started for freeTalk to us