Skip to content
Recaply.
Sign inSubmit a tool

LearnTutorials

OmnigentTutorialsOpen Omnigent

Run and share coding agents with Omnigent

Run Claude Code or Codex through Omnigent to cap spending, switch agents mid-task and share a live session with your team, in under 30 minutes.

By Recaply EditorsIntermediate27 min6 stepsUpdated

A hand holds up a key ring with three keys hanging from it

What you need

  1. Step 1: Install Omnigent

    4 min

    One script installs the omni command, and running it again later upgrades you.

    1. Open a terminal and run the two commands below, one after the other.
    2. The omni setup wizard looks for logins and keys you already have. Confirm the ones for Claude Code, Codex or both.
    3. If the wizard asks for a default, pick the login you use most.
    Run this
    curl -fsSL https://omnigent.ai/install.sh | sh
omni setup

    You should see the setup wizard listing the credentials it found, each ready to confirm.

    The terminal can't find the omni command?

    The installer adds omni to your PATH, and only new windows load that change. Open a new terminal window and run omni setup again.

  2. Step 2: Start your agent inside Omnigent

    3 min

    Your agent runs in the terminal as usual, and the same session opens in a browser you can share later.

    1. In your project folder, run omni claude. For Codex, run omni codex instead.
    2. Open http://localhost:6767 in your browser.
    3. Give the agent a small task, like the one below, and watch both windows.
    Your prompt
    Read the files in this project and write a short README.md that explains how to install and run it.

    You should see the same conversation in the terminal and the browser, updating together as the agent works.

    The agent asks you to log in?

    Omnigent reuses each agent's own login. Run claude auth login for a Claude plan or codex login for a ChatGPT plan, or add an API key with omni setup.

    Keep API keys in omni setup or your environment, never in files you commit or share.

  3. Step 3: Set a spending limit

    3 min

    A cost policy sits outside the agent, so it still holds when a long task runs away.

    1. In the web UI, click the info button (i) at the top of the page.
    2. In the Policies section, click + and pick Session Cost Budget.
    3. Enter a soft limit, such as 5, and a hard limit, such as 20, in dollars. Then click Add.

    You should see Session Cost Budget listed under Policies, next to the session's running cost.

    You can't find the policy list?

    Ask for it in the chat: "Add a session cost budget. Ask me at $5 and block expensive models at $20." Then approve the change.

    Past a soft limit, the agent asks before its next tool call. Past the hard limit, it blocks expensive models such as Opus until you switch to a cheaper one.

  4. Step 4: Hand the task to another agent

    3 min

    In Omnigent, a session belongs to you, not to one agent, so a second agent can pick up the whole history.

    1. In the web UI, open your session and click Clone session.
    2. Pick Codex as the agent for the copy. Started in Codex? Pick Claude Code.
    3. Ask the new agent to review the work so far, or to finish it.

    You should see a second session that holds the full conversation so far, now answered by the other agent.

    The other agent isn't in the list?

    Omnigent can only offer agents it can sign in to. Run codex login or claude auth login, or add a key with omni setup, then clone again.

    You can't change the agent of a running session. The clone leaves the first session as it was, so you can compare the two.

  5. Step 5: Put Omnigent on a shared server

    12 min

    Teammates can't reach a server that runs on your laptop, so sharing needs one in the cloud.

    1. In Railway, import the Omnigent repo from GitHub and add a Postgres plugin to the project.
    2. In the omnigent service's Variables, add DATABASE_URL set to ${{Postgres.DATABASE_URL}}. Then redeploy.
    3. Copy your server's URL and run the two commands below with it.
    Run this
    omni login https://[YOUR SERVER URL]
omni host https://[YOUR SERVER URL]

    You should see your sessions in the browser at your server's URL, on any device where you sign in.

    The deploy fails with "DATABASE_URL is required"?

    Adding Postgres doesn't connect it to the app by itself. Add the DATABASE_URL variable as shown above, then redeploy.

    omni login signs you in to the server. omni host registers your laptop, so the server can send agent work to it.

  6. Step 6: Share the live session

    2 min

    A teammate can watch the agent work, or help steer it, from a browser with nothing to install.

    1. Open the session from your server's URL and click Share.
    2. Pick Read to let them watch, or Edit to let them send messages and answer approvals.
    3. Send them the link.

    You should see your teammate in the session, seeing each message and tool call as it streams.

    The Share button is missing?

    The server's admin can limit sharing or turn it off. If that's you, check the session sharing settings.

    Edit lets a person run code on the machine that hosts the session. Give it only to people you trust.

You get

Claude Code and Codex running through Omnigent, with a spending limit, a way to switch agents mid-task and live sessions your team can join

Try next

Install an agent skill in any AI coding agent6 steps · 5 minDebug your website with the Safari MCP server5 steps · 17 minWrite and test an AGENTS.md file with Claude Code6 steps · 45 min

Did this guide work for you?

Sources

0 of 6Next: Install Omnigent