Skip to main content

Provider Authentication

Before Omnara can start a coding session, you need a working provider.

Claude Code

You can authenticate Claude Code in either of these ways:
  1. Claude Code CLI
    claude /login
    
  2. Environment variable
    export ANTHROPIC_API_KEY=sk-ant-...
    

Codex

Install the Codex CLI, then sign in:
codex login

Omnara Sign-In

When you run omnara for the first time:
  1. Omnara opens your browser
  2. You sign in to your Omnara account
  3. You return to the CLI or app
  4. Your sessions can now sync across devices

Sign-In Options

Email

Email and password

Google

Google account

GitHub

GitHub account

Apple

Apple account

Sign Out

omnara auth logout

Multi-Device

Once you are signed in, the same Omnara account works across:
  • CLI
  • web dashboard
  • desktop app
  • mobile app

Security

  • Encrypted local token storage under ~/.omnara/
  • Automatic token refresh
  • TLS for all connections
  • Session isolation

Account Deletion

You can delete your account from Omnara settings in supported clients. If you are having trouble accessing your account, contact contact@omnara.com.

Common Questions

“Do I need both Claude Code and Codex?”

No. You only need one provider to start using Omnara.

“Why does Omnara launch but not start coding?”

Usually this means Omnara sign-in is complete, but your provider is not installed or authenticated yet.

Troubleshooting

Make sure Claude Code is installed and authenticated.
claude /login
Or set:
export ANTHROPIC_API_KEY=sk-ant-...
Install Codex and complete its login flow.
codex login
Copy the sign-in URL from the CLI and open it manually in your browser.
You are probably signed in to Omnara but not to your provider. Check Claude Code or Codex authentication separately.
Some sandbox flows require workspace sync, checkpoints, or GitHub setup. See the sandbox guide.