Bridge is right for you if
- you already use Claude Code, Codex CLI or Claude Desktop;
- Node.js is available in your environment;
- you want to keep your tool’s interface and working habits.
SEALARCA BRIDGE
Connect Claude Code, Codex CLI or Claude Desktop to Sealarca from your local environment.
Downloading Desk and using Bridge add no separate cost. Only use of the Sealarca service debits credits according to the model and processed volume.
Your compatible tools
Sealarca Bridge
on your device
Sealarca
Sealarca service
Claude Code, Codex CLI and Claude Desktop use Sealarca Bridge on your device, then access the Sealarca service.
The role of Bridge
Bridge is a local adapter. It configures the compatible tool you already use to start a session with Sealarca, without becoming a new work interface or replacing the Sealarca API.
Sealarca Desk
Desk provides a document workspace to organize, find and work with your documents.
Sealarca API
The API is for software that integrates the service directly. Bridge is for your existing AI tool.
Compatible tools
Bridge starts Claude Code with the Sealarca parameters required for the session.
Configuration is injected into the child process environment and does not permanently overwrite your configuration.
Bridge starts Codex CLI with the parameters needed to use Sealarca through the Responses API.
Parameters are applied at runtime through -c options; your ~/.codex/config.toml file is not replaced.
Bridge configures a managed local profile and starts a loopback proxy for Claude Desktop.
The proxy stays local, on 127.0.0.1:15721 by default, and must run while Claude Desktop is in use.
Install & use
The Node package distributed on npm can be installed globally for regular use, or run once with npx. A Sealarca access key and a compatible tool are required.
Requirement
Bridge commands
This panel only shows commands and options available in the current CLI.
$ npm install --global sealarca-bridge
$ sealarca-bridge account login
$ sealarca-bridge models
$ sealarca-bridge claude-code --model <model-id>
$ sealarca-bridge codex --model <model-id>
$ sealarca-bridge claude-desktop configure
$ sealarca-bridge claude-desktop start
$ sealarca-bridge claude-desktop restoreSealarca access key
Bridge uses a Sealarca access key to access the service. Bridge does not provide a separate Sealarca access key.
SEALARCA_API_KEY can provide a key for one session. It is temporary and does not replace secure storage.
SEALARCA_API_KEYDynamic catalog
Bridge discovers the catalog authorized for the current key. No model is hardcoded on this page: the choice is made when you use the tool.
View the public catalogThe authoritative list is retrieved from the Sealarca service.
GET https://api.sealarca.ch/v1/modelsMetadata can enrich identifiers already returned by the catalog, without adding an unauthorized model.
GET https://api.sealarca.ch/v1/model/infoLocal environment
Bridge handles the integration between the compatible tool and Sealarca locally. AI operations then use the Sealarca service according to the documented mechanisms.
The boundary to know
Bridge does not necessarily control logs, histories, files or other data kept by the user tool or operating system. Those elements remain outside Bridge’s boundary.
A note about Claude Desktop
Bridge’s loopback proxy is neither a public API nor the Sealarca service. The token generated for this proxy is local and is not your Sealarca access key.
claude-desktop restore removes the managed profile. Ctrl+C stops the local proxy.
You need a Sealarca account and a Sealarca access key.