condensate

Start here

Find your way around

Where the runtime, apps and shared packages live in the repository.

On this page

This page maps the Condensate repository: the runtime, the applications that run on it, and the shared packages they use. Use it to find the package or app you want to use or change.

The runtime runs three engines: Claude Code, Codex, and Condensate's own agent. The spawn request and model routing decide which one runs a task. Models and other harnesses explains that choice.

The system at a glance
YOUR INTERFACE
Dex · Dojo · Your application
HTTP / TypeScript SDK
CONDENSATE RUNTIME
Threads · Events · Approvals · Coordination
Engine sessions
Claude CodeThrough the Claude Agent SDK
CodexThrough the Codex CLI app-server
Condensate's own agentRuns its model loop in the runtime
Your interface talks to the runtime over HTTP. The runtime records every thread, and the engine you pick runs the model conversation on one of your accounts. Middleware connects agent tools you did not build.

Build an application

Use packages/agents-sdk to call the runtime from your own code. The SDK is early access: it lives inside this repository as a private workspace package and is not published to npm.

The SDK guide starts with a read-only client that lists threads. It then follows recorded events and sends work.

For a chat interface, packages/chat-sdk supplies shared state and React components that connect to runtime threads. packages/thread-ui turns runtime events into view models for the conversation, tool activity, and stream state, and also supplies theme tokens. Its core has no DOM, so server code can use it too. Your interface can then follow the thread the same way the Condensate apps do.

Understand the runtime

PackageWhat it does
packages/agents-hostKeeps durable threads, serves the HTTP routes, tracks which process owns each session, and runs work in execution runners
packages/engineRuns the agent loop for Condensate's own agent, the Claude and Codex adapters, context windows, model routing, and failover between accounts
packages/agents-sdkTyped client and event schemas for applications (early access)
packages/brokerStores provider credentials, refreshes tokens, and gives accounts to sessions

The runtime listens on port 4741 by default. The Runtime HTTP API describes its routes.

For how the running processes are arranged on real machines, read the notes in docs/architecture/ in the repository.

Explore the applications

ApplicationWhat it providesDefault port (developer setup)
DexOne installable page that drives your runtime threads from a phone, a tablet, or a desktop5189
gt-reviewThe review hub: registered checkouts, review rooms, and the API that Dex reads for review work4700
DojoLessons with an AI tutor, a terminal or notebook for the work, and a tutor that reviews what you submit4800
MiddlewareTools exposed over MCP, and hook policy for other agents such as Claude Code and Codex4787

Other apps in apps/:

DirectoryWhat it is
apps/canvasBoards that agents draw on and people open
apps/browser-extA browser side panel that answers questions about the page you have open
apps/condensate-liveThe iPhone app, which embeds the Dex page and shows a Live Activity
apps/headThe workspace head page: a conversation with the head agent next to the state of your estate
apps/siteThe public condensate.dev site: the landing page, forkit, and where the docs are mounted
apps/docsThis documentation website, built from apps/docs/content
apps/dexThe Dex design system assets (web/ds): component styles, scripts, and icons

Shared packages

PackageWhat it does
packages/orbkitAnimated marks and status indicators for agent state. Its root API does not need React
packages/proseWriting checks, the document profile, and the proof passes that a document thread's merge gate counts
packages/canvas-vocabularyThe drawing vocabulary an agent may use on a canvas board
packages/head-toolsThe tools the workspace head uses, provided as an Effect service
packages/condensate-pluginOne plugin for Claude Code and Codex that bundles governance hooks, the code-mode MCP server, and skills
packages/estateSnapshots a machine's setup, plans changes against a desired manifest, and redacts secrets before a manifest is shared
packages/workos-authChecks WorkOS access tokens and returns the signed-in principal or a failure reason

Reference pages

Each package and app that has a package.json gets a reference page, generated from that manifest. The pages list its commands, its exports, and the workspace packages it depends on. Find them under /reference/packages/ and /reference/apps/, for example agents-host.

When a guide and a reference page disagree, the reference page reflects the current manifest.