API overview

Claxedo is a set of composable packages for building coding-agent products. The HTTP surfaces below are owned by different packages in the stack — each one is a distinct trust boundary. This page indexes the surfaces and points at the per-surface reference pages.

These tables are hand-written and checked against the source. Every route, tool, and field on the API Reference pages is meant to match the cited package source exactly. Found a mismatch between these tables and the code? Please open an issue.

HTTP surfaces

Surface	Owning package	Reference
/api/wr/* — per-workspace host routes (health, capabilities, config, events, files, diff/git, PTY, process, hooks, session-env)	@claxedo/workspace-runtime	Workspace runtime API
Relay tunnel edge + /metrics + /health	@claxedo/workspace-relay	Relay API
MCP runtime tools (stdio)	@claxedo/mcp	MCP tools
/api/claxedo/integrations/* — connections framework	@claxedo/connections (mounted by the host)	Connections API
/api/workgraph/* — personal WorkGraph commands, snapshots, opaque tenant-bound cursors, ordered changes, Work Sources, Source Views, and candidate admission	@claxedo/workgraph (mounted by claxedo-server)	WorkGraph package source
Channel ingress webhooks (github / slack / telegram / discord / whatsapp)	@claxedo/channels	Channels API

Package roles

Package	Use it for
@claxedo/workspace-runtime	Run or embed a per-workspace host next to the project directory the agent should work on.
@claxedo/agent-extensions	Discover, install, lock, materialize, and replay reusable Agent Extension packages for OpenCode, Claude, Codex, and Cursor.
@claxedo/agent-sdk-runtime	Embed one AgentRuntime facade over OpenCode, ACP harnesses, native SDK harnesses, or Pi.
@claxedo/agent-event-runtime	Normalize raw harness events into a canonical AgentRuntimeEvent stream and project them into compatibility formats.
@claxedo/workspace-relay-protocol	Use tunnel wire types and token verifier contracts without pulling in Hono or server code.
@claxedo/workspace-relay	Run the relay process that connects browsers/gateways to workspace-runtime hosts.
@claxedo/mcp	Expose Claxedo runtime tools to any MCP client.
@claxedo/sandbox-manager	Manage sandbox placement and epoch-based leases for running workspace runtimes inside provider sandboxes (Cloudflare, Daytona, Docker, Modal, Vercel).
@claxedo/channels	Route GitHub / Slack / Telegram / Discord / WhatsApp messages into Claxedo sessions with dedup, session resolution, and approval bridging.
@claxedo/connections	Link external accounts (Notion, Atlassian, GitHub, Google) once and consume them by capability.
@claxedo/workgraph	Embed the personal AI-work graph, runtime-neutral contracts, SQLite adapter, HTTP router, and core adapter conformance v5. The host supplies trusted organization and user scope; Claxedo Cloud supplies the Convex adapter through its control plane.
control-plane (claxedo-server)	Study the gateway/host composition Claxedo itself runs. Private and unpublished; a @claxedo/control-plane split is planned. See control-plane.

Code-supported vs product-owned

The runtime and relay packages ship code-supported surfaces. Some concerns are deliberately product / control-plane owned and are not part of any package API surface:

Product-owned surface	Status
Agent Extension catalog policy	Curated catalog data and marketplace UX live in the product/control plane, not in @claxedo/agent-extensions.
Agent Extension auth and org UX	Workspace/user/org authorization and team-wide activation UX live in the control plane. The package exposes desired state and policy primitives.
Agent Extension fan-out	Server/supervisor code decides which connected workspace runtimes receive snapshots. The package materializes the snapshot it is given.

@claxedo/workgraph is published at 0.1.0. It provides the personal AI-work domain, embedded service/router, runtime-neutral contracts, SQLite composition, public storage ports, and runner-neutral adapter conformance. claxedo-server derives the trusted (organization, user) tenant and exposes no tenant selector. Local embedded agent tools invoke the service directly; standalone stdio MCP tools use authenticated HTTP; hosted embedded tools require durable Session tenant provenance. Claxedo Cloud composes the same contract over Convex. The deployed staging proof remains a release gate.

Supported package entry points

Surface	Supported today	Source
Standalone workspace runtime	startServer(port, options)	packages/workspace-runtime/src/server.ts
Embedded runtime Hono app	createWorkspaceRuntimeApp(options)	packages/workspace-runtime/src/server.ts
Low-level Workspace Host	createWorkspaceHost(options)	packages/workspace-runtime/src/workspace/runtime.ts
Core route mounting	mountWorkspaceCore(app, upgradeWebSocket, { eventHub, exposure })	packages/workspace-runtime/src/workspace/core.ts
Relay-attached runtime options	workspaceRelayRuntimeOptionsFromEnv	packages/workspace-runtime/src/workspace-relay-env.ts
MCP runtime tools	@claxedo/mcp CLI package	packages/claxedo-mcp/package.json, packages/claxedo-mcp/src/server.ts

---

For per-package install instructions and architecture, start at the workspace-runtime package page and follow the sidebar; each API page above also links back to its owning package.