EARLY ACCESS · CONNECTOR SETUP
Install once.
Route with less friction.
Choose the coding tool you already use. Embercrank stays in the background while routing policy remains on our service.
Choose your tool
The current Claude adapter runs through a separately authenticated local Claude Code CLI. A desktop-app session is not copied into the adapter; use the provider login available to that CLI when it asks.
Recommended: ask your coding tool to install it
Install Embercrank from the public Embercrank marketplace. Run the documented marketplace install commands for this host. Do not modify project files. After installation, show me the Embercrank activation link and device code, then wait for my approval.The host may ask for permission before running the commands.
Prefer the terminal?
Copy these commands into your terminal
codex plugin marketplace add jaydenreu/embercrank-marketplace --ref v0.1.0-beta.13codex plugin add embercrank@embercrank --jsonConnect your account
Start the connector from the same local CLI you plan to use, then run its activation command. It will show a short-lived device code.
Open activation ↗Enter your email code in the browser. Then approve only the device code shown by your own connector. This connects Embercrank; it does not transfer or reuse a desktop-app provider session.
Need a fallback?
Use a verified archive if your host cannot add a Git marketplace. The archive contains the connector only; it does not contain routing policy, credentials or server code.
Verify the published SHA-256 manifest before extracting. Keep your provider login with Codex or Claude Code.
What stays private
- Provider credentials stay with your official coding tool.
- Routing policy and model selection remain server-side.
- Prompts and provider responses are not stored in Embercrank’s application records.
Embercrank only manages jobs explicitly sent through its connector. It cannot intercept unrelated host actions.