Skip to main content
Version: 1.2.0

Providers & Login

ClaudusBridge ships one embedded coding agent that can drive three different AI providers using your own accounts:

  • Claude (Anthropic)
  • ChatGPT / Codex (OpenAI)
  • Gemini (Google)

There are no API keys to paste and no per-token billing from the plugin. You sign in with the same account you'd use in each provider's own app, and only that provider's normal login and model calls leave your machine. Everything else is local.

One agent, three providers​

The embedded agent is ClaudeCodeAntigravity (CCAG) — a Claude Code build that also speaks to ChatGPT (Codex) and Gemini in the same session. It ships inside the plugin as a single, self-contained Node bundle at Resources/Agent/:

  • cli.js — the bundled agent (Node target, vendor-free, ~30 MB).
  • cli-node.js — a tiny ESM entry that imports cli.js.

Because the bundle is vendor-free, the plugin needs no external agent install. The only host requirement is a system Node.js install, which the plugin uses to run the bundle.

The agent is reachable two ways, both local:

  • In-editor terminal. The ClaudusCode module hosts a Slate terminal (SClaudusCode) backed by a real PTY (ConPTY on Windows, forkpty on Mac/Linux) and a VT parser. This is the interactive, type-to-the-agent experience.
  • Programmatic ACP. FClaudusAcpClient spawns the bundle headless via node "cli-node.js" --acp and drives it over the Agent Client Protocol (JSON-RPC over stdio) — no PTY required. Console commands: ClaudusCode.Acp.Start, ClaudusCode.Acp.Stop, ClaudusCode.Acp.Prompt.

How sign-in flows​

Sign-in happens through the agent, using each provider's normal OAuth login — the same browser-based "Sign in with…" flow you already know:

  1. Start the agent (open the in-editor terminal, or start an ACP session).
  2. Trigger the provider's login from the agent (its standard login command/flow).
  3. The provider's OAuth page opens in your browser. Approve it with your own Claude, ChatGPT/Codex, or Gemini account.
  4. The session token is stored by the agent locally on your machine. From then on the agent uses your account's normal entitlements.

Because this is OAuth against the provider, the plugin never sees or stores an API key. There is no ClaudusBridge billing layer in the path — your usage is just your account's usage.

Switching models and providers​

Once signed in, you switch between providers and models the same way you would in the underlying Claude Code-style agent — through its model/provider selection inside the terminal or via the agent's own commands. The single agent process can target Claude, ChatGPT/Codex, or Gemini; pick whichever account you're signed into and whichever model that account exposes.

Over ACP, the same agent applies a permission mode to each session, which governs how much the agent may do on its own:

ModeBehavior
defaultAsks for permission on sensitive actions.
acceptEditsAuto-accepts edits, still prompts for riskier actions.
bypassPermissionsRuns without permission prompts.
planPlans without making changes.

100% local​

Apart from each provider's own login and model API calls — which go directly to Anthropic, OpenAI, or Google under your account — nothing leaves the machine:

  • The agent bundle runs locally under your system Node.
  • The MCP server binds to 127.0.0.1 only.
  • Multi-User, the editor tools, and the terminal are all local.

In short: you bring your own AI account, the plugin brings the agent and the 900+ editor tools, and the only traffic off your machine is the provider login plus the model calls you'd be making anyway.

Requirements​

  • Unreal Engine 5.8 (Windows / Mac / Linux).
  • A system Node.js install on PATH (used to run the embedded agent bundle).
  • An account with at least one of the providers — Claude (Anthropic), ChatGPT/Codex (OpenAI), or Gemini (Google).

Tip: verify the bundle runs against your Node install with node cli-node.js --version from Resources/Agent/ — it should print the agent version (e.g. Claude Code).