Integrations

Claude Code

One install command connects Terminal and Desktop to your organization's workspace. Keep your normal Claude login.

Sovereign links your Claude requests to your organization's workspace. Your admin can see member activity, models, routing status, tokens, and timing. Your Claude plan and usage limits still apply. No provider API key is needed.

Set up your organization

Open sov.solibra.ai/app. Create a workspace or sign in with your email and password. Your dashboard email can differ from the account you use for Claude.

Open Connect, choose Claude Code Terminal or Claude Code Desktop, then choose My Claude login. Press Copy command and share it with your members. It contains your workspace address and an enrollment code. Members do not need dashboard access or an admin password.

To add another admin, enter their email on the same page and create an admin link. You can remove an outgoing admin after their replacement joins. Member setup stays the same.

Connect Terminal and Desktop

Run the command your admin shared once in Terminal. It installs the local connection and links both clients to the correct workspace. On macOS, it does not need an administrator password.

Quit and reopen Claude Desktop. Open the Code tab and start a local session. Open a new Terminal and run:

claude

Use your normal Claude login in each client. Do not copy a Claude token or set ANTHROPIC_AUTH_TOKEN or ANTHROPIC_API_KEY for this subscription connection. The installer keeps your login and adds the workspace connection.

Desktop manages its own API address, so a base URL alone does not connect Desktop. The installer uses Claude Code's supported proxy settings for local Code sessions. Remote cloud sessions, Chat, and Cowork are outside this integration.

See your requests

Your first request joins the workspace with the enrollment code and your verified Claude identity. Your admin sees you under Workspace. Requests appear under Sessions in that workspace's dashboard.

Open a session to see:

  • The model requested and the model that served the request.
  • Routed, Unchanged, Fallback, or Pass-through status, including HTTP errors.
  • Input and output tokens, request time, and elapsed time.
  • Subscription billing. API price estimates are not a subscription bill or cash savings.

Each workspace has a separate database, gateway process, and admin sign-in. An admin in one workspace cannot use that login to open another. A valid Claude login alone cannot join a workspace: the member must have its install command.

Sovereign forwards the Claude login credential to Anthropic over TLS without storing it. It records usage and redacted request context and replies. Login and account-management traffic stays with Anthropic.

Routing and access

Sovereign only selects Claude models for this connection. Context, workspace policy, cache state, and learned quality scores guide each decision. Tools, hooks, permissions, and MCP servers continue to run in Claude Code.

If the routing classifier fails, Sovereign sends the original request to the original model and records a fallback. It tries the classifier again on the next request, so routing resumes when the classifier recovers. Unknown models pass through unchanged. Subscription requests are not replayed for model comparisons.

An admin can remove a member on Workspace. That member cannot reconnect with the same Claude account, even with the install command, until an admin restores their access. Replacing the install command stops new enrollments with the old code; existing members stay connected.

Check or disconnect

Check the local connection:

curl -fsSL https://sov.solibra.ai/claude/install.sh | bash -s -- --status

Disconnect the installed clients and restore the settings changed by the installer:

curl -fsSL https://sov.solibra.ai/claude/install.sh | bash -s -- --uninstall

Restart Claude Desktop and open a new Terminal after a settings change. If requests do not appear, confirm that you used your workspace's command and a local Code session. Old shell exports or organization settings can override the connection. If your company already requires another proxy, keep it and ask your administrator to connect Sovereign through that proxy.

Company API accounts

In Connect, choose your Claude Code client and select Company API account. Connect Anthropic, OpenRouter, or a supported cloud account. Choose a model and create a setup for each user. Terminal users receive a command and settings JSON. Desktop users receive their gateway URL and credential for Developer, Configure Third-Party Inference. Usage is billed to the connected provider account.