How-to guides

"How do I do X?" A how-to guide is a recipe for a goal you already have: what you need, the steps, the result. It assumes the basics and points at the reference rather than repeating it; new here, start with a tutorial.

Set it up

• Set up accounts: the Slack app, a model key, the GitHub App, Cloudflare, E2B, Brave.
• Turn features on and off: the capability matrix and what each costs.
• Restrict who can do what: grants and restrict, from open to locked down.

Use it

• Configure your defaults: agent, model and effort, per you or per channel.
• Connect an MCP server: external tools without a token in chat.
• Onboard a repo: an always-warm environment for one repository.
• Watch a run: live runs, stopping one, reading history.
• Check spend: cost per day and group, and the JSON twin.

Extend it

• Add a model provider: a config block, or an adapter.
• Add an agent: a prompt, a toolset and budgets, on every surface.
• Put a preset on OpenCode: one config line, the rollback, what changes on the run page.

Run it in production

• Deploy: the profile, the secrets, deploy all, the optional Workers, CI.
• Operate production: a deploy or config change outside a release; the span log.
• Rotate a secret: a put and a restart.
• Ship a release: read the release PR's plan, merge, confirm it is live.
• Configure the repository: the GitHub settings a fork reproduces.
• Store run artifacts: the R2 bucket runs move files through — the token, the secrets, the config, retention, the privacy check.
• Run a load test: a number for many runs at once.