$ bitter grid
deploys and hosted workspaces
Ship apps, check runtime state, and recover releases from the same command surface.
Bitter CLI
One command surface for agent-built software.
Bitter CLI connects an agent workspace to the product systems a real app needs after the prototype: deploys, credentials, logs, payments, support, analytics, inboxes, and memory.
Namespaces
A CLI that matches the operating shape of a product.
$ bitter pass
scoped credentials
Give agents access through explicit selectors instead of loose production secrets.
$ bitter log
receipts and memory
Keep the evidence of what changed, what shipped, and what should happen next.
$ bitter checkout
payments
Add checkout and subscription flows when the product is ready to sell.
$ bitter desk
support
Turn customer questions and incidents into work your agent can pick up.
$ bitter analytics
demand signals
See usage, search, support, and checkout signals next to the work that caused them.
$ bitter workspace
hosted AI agent workspace
Open the repo, terminal, provider CLIs, deploy state, logs, and receipts in one account-scoped environment.
$ codex in bitter
provider CLI inside app operations
Use Codex where the app can be tested, shipped, verified, and remembered after the code changes.
Workflow
Local when you want it. Hosted when the work needs a home.
The CLI is useful on your machine, but it is also the same command language a hosted Bitter workspace uses. That keeps local experiments and production operations in one loop.
- 01
Install the Bitter CLI locally or open a hosted workspace.
- 02
Register the app, repo, service, and domain that the agent will operate.
- 03
Run build, deploy, credential, log, checkout, and support commands through scoped namespaces.
- 04
Let every release leave receipts that improve the next pass.
Next