Managed workspace + Bitter CLI

A real workspace for coding agents.

Bitter gives you and your agents one prepared place to build, deploy, sell, and support a real product.

Open the hosted terminal or use the same CLI locally. Your repo, deploys, credentials, logs, payments, support, and analytics are connected from the start.

$bitter# Keeps project history and decisions
disk
80GB
ram
8GB
cpu
2 vCPU
Request early access
What is includedExplore the CLISee the workspace
$curl -fsSL https://install.bitter.sh | sh

from prompt to operating base

A prompt is only the bottom rung.

Agents can draft the app from a prompt. Bitter hands them the rest: a prepared box, project instructions, and CLI hooks into source, deploys, secrets, logs, and customer channels.

Agent-built software ladder. Work moves from one-off prompts through project context and operating loops toward Bitter. Earlier levels become context beneath the ladder.
  1. Prompts: type one-off instructions by hand.
  2. Project context: give agents durable objectives and enough context to act.
  3. Operating loops: deploy, observe, capture feedback, and improve.
  4. Bitter: the operating base above the climb.

vertically integrated

Agents get one operating surface.

Instead of handing agents a pile of SaaS accounts, Bitter exposes the pieces of a real product through one CLI: deploys, secrets, memory, inbox, payments, support, clips, leads, and analytics. Ship through them and they report back: what people paid for, replied to, asked about, and watched.

agent attachedlive

An agent enters through the CLI.

$ bitter

Keeps project history and decisions

loggridgitpasscheckoutscreenclipanalyticsleadsinboxdesk

the discovery loop

Every release teaches the next.

No prompt can tell you what customers will do. Ship, watch what happens, and use that evidence in the next release.

  • you set the direction
  • agents build and ship
  • customers respond: payments, replies, tickets, usage
  • bitter keeps the lessons for the next release

what a Bitter Box includes

A prepared machine agents know how to use.

Dedicated VM

80GB disk, 8GB RAM, 2 vCPU, hosted in the region of your choice: US, EU, or Singapore.

AGENTS.md

Project instructions that teach agents how to use the Bitter CLI and this box.

Hosted terminal

Work from the browser or connect directly through remote sessions.

Bitter CLI

Connects source, deploys, logs, credentials, checkout, support, inbox, clips, analytics, leads, and project history. See the CLI surface.

AI agent workspace

A hosted workspace with your repo, coding tools, deployment access, logs, and project history. See the workspace.

Codex-ready

Use Codex or another coding tool in an environment that can test, deploy, and remember the work. Use Codex with Bitter.

The machine arrives ready to work, with project instructions that show agents how the pieces fit together.

Request early access
$curl -fsSL https://install.bitter.sh | sh

AI agent workspace FAQ

The workspace behind the CLI.

Bitter is built for the handoff after a prototype exists: a place where agents can keep building while the product starts collecting deployment, support, search, usage, and revenue signals.

What is Bitter?

Bitter is a workspace and CLI for AI-built software. It gives coding agents a prepared machine with your repo, coding tools, deployment access, logs, support, checkout, analytics, and project history.

How does the Bitter CLI work with hosted workspaces?

The Bitter CLI keeps the local and hosted loop consistent. A builder can install the CLI locally or open a hosted workspace, then use the same account, app, deploy, credential, and log concepts.

What can agents do after a Bitter workspace is prepared?

Agents can inspect the repo, run and test code, deploy, check logs, use approved credentials, and leave a clear project history for the next session.