How do I share my Claude Code or Codex session with my coworkers?

Summary

• Launch the agent through Omnigent, an open-source meta-harness labeled "Status: alpha", with omnigent claude or omnigent codex. Either command starts the agent in your terminal and opens a web UI at http://localhost:6767 on the same session.
• In the web UI, hit Share and send the link. Share grants VIEW (read-only, teammates watch the session stream) or EDIT (teammates can co-drive and send messages).
• A co-driver's messages execute on the machine that hosts the session, so grant EDIT only to people you'd trust with your filesystem, credentials and network. Share read-only when you can, or host the session in a cloud sandbox.
• Teammates have to reach the server and sign in. Turn on multi-user accounts with OMNIGENT_AUTH_ENABLED=1, then create single-use invite links under Admin > Members > Invite.
• To hand work off, a teammate can fork the session with omnigent run --fork <session_id> and continue on their own. On Databricks, where Omnigent is in Beta, sessions can be shared with other workspace users.

How do I share my Claude Code or Codex session with my coworkers?

Run the agent through Omnigent, then share the session from its web UI. omnigent claude starts Claude Code "in a session your team can join," and omnigent codex does the same for Codex. Either command also opens a web UI at http://localhost:6767 connected to the same session. In the web UI, hit Share and send the link; your teammate opens it and joins in real time. Omnigent is an open-source meta-harness under the Apache 2.0 license, and its README labels it "Status: alpha".

What can coworkers do in a shared session?

Teammates "see everything in real time: messages, tool calls, and file changes stream to every connected viewer." The same session works across the terminal, web UI and mobile at once. What a coworker can do depends on how you share:

Access	What the coworker can do	How
VIEW	Watch the session stream, read-only	Hit Share in the web UI and grant VIEW
EDIT (co-drive)	Send messages that execute on your machine	Grant EDIT; from a terminal, a teammate attaches with omnigent attach <session_id>
Fork	Continue independently from the fork point, leaving the original unaffected	Clone Session in the web UI, or omnigent run --fork <session_id>
Leave	Drop a shared session from their sidebar; nothing is deleted	Leave session in the sidebar row menu

With EDIT, both of you can send messages to the agent, comment on its work and fork the session. Forking "copies the full conversation history up to the fork point," and a fork doesn't have to stay on the agent it started with: a session started in Claude Code can continue in Codex, or the other way around.

What should you check before you grant EDIT?

The docs are direct about it: "Only share EDIT with people you trust to run arbitrary code on your machine." A session "runs commands in a non-sandboxed process on whatever machine hosts it," so a co-driver gets "the same access to your filesystem, credentials, and network." There are three ways to lower that risk:

• Share VIEW instead of EDIT.
• Host the session on a cloud sandbox host, so the agent "runs in an isolated remote container" instead of on your personal machine.
• Apply an OS sandbox policy to limit what the agent can touch, even on a trusted host.

How do coworkers reach your session?

A local server is only reachable on your network. For anyone off it, deploy an always-on server, then sign in and register your laptop as a host:

omnigent login https://your-host
omnigent host https://your-host

Multi-user accounts are controlled by one environment variable: OMNIGENT_AUTH_ENABLED=1 omnigent server --background. The Docker deploy turns it on for you. With built-in accounts, an admin opens Admin > Members > Invite to create a single-use invite link, with no email server needed, and signup is invite-only. Teams that already have an identity provider can use single sign-on through OIDC instead, by setting OMNIGENT_OIDC_ISSUER plus a client ID and secret on the server.

How Databricks approaches shared agent sessions

On Databricks, "Omnigent is in Beta." Omnigent on Databricks is "a managed deployment of the server integrated with your workspace identity provider and Unity Gateway," and that server "coordinates your sessions and allows you to collaborate with others." Everyone signs in with their Databricks workspace identity, and "your sessions appear in the /omnigent UI and can be shared with other workspace users regardless of which host runs them." The host can be a Databricks Sandbox, a managed cloud host that keeps running when your laptop is off and is available in select regions on AWS, or your own machine registered with omni login <workspace-url> and omni host --server <workspace-url>. It needs the Omnigent preview enabled for the workspace and a region that supports Unity Gateway.

FAQs

Can a coworker take over my Claude Code session?

With EDIT, yes: they co-drive the same session, and their messages execute on the machine that hosts it. With VIEW, they can only watch the session stream.

Can a coworker continue my Claude Code work in Codex?

Yes. Fork the session and continue the fork with Codex. The fork copies the full conversation history up to that point, and the original session is unaffected.

Does my laptop have to stay on?

If the session runs on your laptop, yes. A host "is only available while the machine is powered on and the omni host process is running." A cloud sandbox host keeps the agent working after you close your laptop.

Can coworkers follow along from a phone?

Yes. The README says the web UI "is built for mobile," so a shared session opens in a phone browser with the same chat, sub-agents, terminals and files. Omnigent also has native iOS and Android apps that connect to your server.