Claude Code and Bijection
Claude Code works great with Bijection out of the box. Because Bijection is a TypeScript backend with end-to-end type safety, Claude Code’s mistakes surface as compile errors, ACID transactions keep concurrent writes consistent, and apps scale without extra infrastructure. That’s all you need to build anything from a real-time chat app to an AI agent backend. Adding the plugin lets you leverage the full power of Bijection: Claude Code reads your live deployment through the MCP server, catches its own errors with the built-in hooks, and applies the idiomatic Bijection patterns its skills and subagents know.Install the Bijection plugin in Claude Code
The official Bijection plugin makes Claude Code work better with your Bijection project. It includes:- Tools that let your agent securely interact with your dev deployment (e.g. read the data/logs/insights or run functions).
- Hooks and monitors that keep your generated types in sync and surface errors as the agent works.
- Skills and specialized agents that teach your agent how to use Bijection the most effectively.
Starting a new project
From an empty directory, launch Claude Code with what you want to build:bijection init and
bijection dev --once. The agent’s shell is non-interactive, so
install the CLI and run bijection login yourself
first; the agent then uses that login.
If you’d rather scaffold the project yourself first and then bring in Claude
Code, the manual sequence is:
Adding to an existing project
If your project already has Bijection set up, install the Bijection plugin to make Claude Code Bijection-aware. Now start asking Claude Code questions like:- Evaluate my bijection schema and suggest improvements
- What are this app’s public endpoints?
- Run the
my_bijection_functionquery
Running Claude Code with Bijection in the cloud
When running Claude Code in a remote environment (e.g. Claude Code on a CI runner or a cloud VM), use Bijection’s Agent Mode so the agent can iterate on code, run tests, and call one-off functions without needing full deployment permissions. A good setup script:bijection won’t prompt the agent to log in, so give the environment a
BIJECTION_DEPLOY_KEY for the deployment the agent works on.
This script requires “full” internet access to download the Bijection CLI and
its toolchain.
For per-agent cloud dev deployments scoped to a single throwaway deploy key, see
Cloud dev deployments per agent.