This page describes Corbits Code, the app. It does not describe credentials or grants held by the control plane, and it does not speak for behavior inside MCP server processes or the shared agent runtime.
MCP servers
Connect Model Context Protocol servers over stdio (launched as a subprocess) or HTTP (a remote Streamable-HTTP endpoint, authorized via OAuth). Configure them per repo and inspect connected servers with
/mcp. The setup guide walks through adding Linear and Slack.Lifecycle hooks
Config-driven
postTurn and postRun hooks (shell or TypeScript) run automatically. postTurn receives aggregated turn context; postRun receives a run summary. Discovered per repo and globally, and toggled with /hooks.Plugins and skills
Opt-in capabilities: web search, additional tools, workflow recipes. Plugins are discovered per repo, from
.corbits/plugins/, and globally, from ~/.corbits/plugins/. Enabling one is a global choice rather than a per-repo one, because the enable flag travels with any credentials the plugin declares and those live only in the global settings file. Skills are Markdown capability packages the model loads on demand rather than commands you invoke, resolved from enabled plugins first and then from the repo you are working in.Slash commands
An extensible in-TUI command surface:
/model, /connect, /settings, /permissions, /plugins, /hooks, /mcp, /cost, /status, /clear, and more. Plugins can register their own.Support
Help Center
Join hundreds of developers building with Corbits and speak with the team directly.