Fix a production bug
Open the app workspace, inspect logs, patch the repo, run checks, deploy, and leave a receipt.
Codex workspace
Run Codex where the app can ship.
Bitter gives Codex a prepared app workspace: the repo, terminal, deploy target, credential selectors, logs, receipts, and product signal all in one place.
Boundary
Codex writes code. Bitter keeps the app operable.
The useful outcome is not a patch sitting in a chat. It is a change that was tested, deployed, checked, and remembered with the app context intact.
Bitter supplies the hosted workspace, repo context, deploy path, credential selectors, logs, and receipts.
Codex remains the provider agent surface. Use your provider's official auth flow and account policy.
The workspace keeps app operations visible so a code change can be tested, shipped, verified, and remembered.
Use cases
Work that needs more than a code diff.
Improve a launch page
Edit the site, generate the static output, submit the sitemap, and verify live metadata.
Connect credentials
Use BitterPass selectors and deploy manifests instead of handing an agent raw secret material in chat.
FAQ
Can I use Codex in a Bitter workspace?
Yes. Bitter workspaces are designed to run provider CLIs such as Codex alongside the repo, deploy tools, logs, credential selectors, and account context the app needs.
Does Bitter manage my Codex account?
No. Bitter keeps the app workspace ready and scoped. Provider account sign-in and policy stay with the provider and your account.
Why use Bitter around Codex?
The surrounding environment is the hard part after code generation: app context, deploys, verification, credentials, receipts, customer signals, and memory for the next pass.