Cloud sessions

A Claude Code cloud session, on the web or in the app on your phone, starts in a fresh container every time: no browser opens there, and no sign-in is kept. omni signin cannot run in it, so without more the loop builds your PRDs while their page, their questions and their approvals go silent.

A token fixes that. You make it once, on your laptop or on your profile page, and paste it in your cloud environment as OMNI_TOKEN. From then on, every session started in that environment is signed in as you, with the same rights you have on the Omni page and nothing more. This page walks you through it step by step, once per cloud environment, then shows what changes when you run the loop from there.

Before you start

• You are a member of the workspace on the Omni page: you signed in there once with GitHub (Install, step 3, or Join a team).
• The repository runs the loop: it has a .omni-loop/ folder at its root.
• Claude Code reaches it on GitHub: in Claude Code on the web or the app, your GitHub account is connected and the repository shows in the list when you start a session.
• A laptop with omni installed helps, for step 1. Without one, make the token on your profile page instead.

1. Make a token

Two ways, one token. Either one makes it, shows it once, and lists it on your profile page.

From a terminal on your laptop, at the root of a repository that runs the loop:

omni setup-token

It opens your browser: sign in with your GitHub account, as for omni signin. The terminal then prints:

Make the token in your browser: <link>
omk_…
It expires on <yyyy-mm-dd>.
Paste it as OMNI_TOKEN=<token> in your cloud environment's variables.

Copy the line that starts with omk_: it is the token, and nothing shows it again. No browser opened? Open the link of the first line by hand: the terminal waits for it all the same. The token is named terminal <yyyy-mm-dd> and expires in 90 days; --name and --days change that, and --days takes 30, 90 or 365:

omni setup-token --name "claude cloud" --days 365

From the Omni page, with no terminal at hand: open the app, go to your own profile page (/app/people/<your login>), and find Terminal tokens, under Alerts. Give the token a Name, pick Expires in 30, 90 or 365 days, and press Make a token. You sign in with GitHub, and come back to the same page with the token marked shown once, beside Copy and the line Paste as OMNI_TOKEN= in your environment. A reload never shows it again.

Terminal tokens lists every live token you made, newest first: its name, ·· and its last four characters, when it was made, when it was last used (or Never used) and when it expires. Revoke stops one at once, after you confirm; do it as soon as a token leaks or you stop using it. You hold at most 20 live tokens: the section says so when you reach the limit, and you revoke one to make another. An owner of the workspace sees and revokes every member's tokens where the workspace's links are listed, and a member who leaves the workspace loses every token they made.

Keep the token like a password: it acts as you until it expires or you revoke it. Paste it nowhere but your cloud environment.

2. Set up the cloud environment

A cloud environment is the settings every session started in it gets: its network, its variables and a setup script. Make one for the loop, or edit the one you use.

1. Open the environment's settings. In Claude Code on the web or the app, start a new session and open the cloud environment menu in the session's title bar: New cloud environment makes one, Edit changes the one selected.

2. Name it, so you pick it again: omni loop, for example.

3. Network access: a session must reach the Omni page. Allow the host of the repository's ask.url (read it with omni config ask.url; for the Omni Loop's own repository it is www.omni-loop.xyz), and openrouter.ai too when you set OPENROUTER_API_KEY below:

   • Limited, with those hosts added under Allowed domains, and Allow package managers left ticked, so the setup script can install. An app that has not updated shows the same thing as Custom, with a box to include the default list of package managers: tick it.
   • Or Full, which allows every host.

   The default, Trusted network access, does not allow the Omni page: a session then stops on OMNI_TOKEN: cannot reach <host>.

4. Environment variables: one line per variable, in .env format: OMNI_TOKEN=omk_…, with the token you made in step 1. Add any optional variable the repository's README lists under its environment variables, such as OPENROUTER_API_KEY, when you want what it turns on in the cloud too. Nothing for GitHub: see What needs no setting up.

5. Setup script, only for the Omni Loop's own repository: its omni runs the kit's source, which needs the repository's dependencies, so the session must install them before it starts. The script is one line: pnpm install --frozen-lockfile. Without it, omni and the briefing the session prints when it starts both stop on Cannot find package 'yaml'. A repository the kit was set up in carries a bundled omni in .omni-loop/bin/ that needs nothing installed: leave its setup script as it is.

6. Create environment (or Save).

Each session started in that environment reads its settings when it starts. A session already open keeps what it started with: start a new one.

3. Check it

Start a session on the repository, and ask Claude to run:

omni whoami

A cloud session has no omni installed globally: Claude runs the repository's own copy, node .omni-loop/bin/omni.mjs whoami, which is the same command. It prints your login and the last four characters of the token:

<your login> (OMNI_TOKEN ··<last four>)

That is it. Ask mode, dossiers, approvals, omni signin and the status line now work as you: the status line shows token ··<last four> where your laptop shows your sign-in, and omni signin prints signed in by OMNI_TOKEN as <login> — <owner/repo> goes to <workspace> and opens no browser.

4. Run the loop from the session

Start a session on the repository in that environment, and work as on your laptop: type the loop's commands, such as /omni:status, /omni:brainstorm '<your idea>' or /omni:yolo <n>, and answer Claude's questions there. Ask mode, PRD pages and approvals go through the token.

When a /omni: command is not found. A cloud session may start without the omni plugin's commands: Claude then says no command has that name. The skills are still there to follow. In the Omni Loop's own repository, ask Claude to follow the skill file itself, which is the same skill:

Follow kit/plugin/skills/brainstorm/SKILL.md for this idea: <your idea>

What is slower in the cloud. A cloud session reaches GitHub through Claude's GitHub connection, which allows GitHub's REST API but not its GraphQL API. The omni commands that list pull requests through gh pr stop on HTTP 403: GitHub GraphQL is not available: omni board, and the merge gate /omni:wave asks (omni flow check merge). /omni:yolo still builds a PRD there: Claude reads the waves from the plan, opens and merges each sub-PR through the GitHub connection, and checks by hand what the board and the gate check (the base, the slice's ground, its checks). Say so when you start, so Claude does not stop on the first 403.

What needs no setting up

• GitHub. The session reaches your repositories, branches and pull requests through Claude's GitHub connection, not through the token: nothing to paste for it.
• Your laptop. A token never touches your laptop's sign-in: omni signin there works as it did. When OMNI_TOKEN is set, it wins over the sign-in omni signin keeps.
• Several sessions at once. Any number of sessions share one token, for as long as they run.

When OMNI_TOKEN fails

Each failure stops the command with one line, naming the variable and never its value.

Other troubles with the sign-in are in When something goes wrong.

Next → How the loop works