Workspace crates

When to read this: You need a one-glance map of the 13 workspace crates and where to dive deeper. This page opens the Reference section.

The Reference section is lookup material, most of it generated or synced from the repository: the crate index below (one README per crate), the tools catalog, the provider matrix, the slash commands, the CLI flags, the environment variables, the settings schema, the GPUI event catalog, the singleton inventory, the WIT interface, the curated MCP catalog, build disk usage, make targets & CI workflows, the doc frontmatter schema and the glossary. The reference/* pages are regenerated by make docs-gen from scripts/gen-docs-reference.sh; edit the script, not the page.

Each crate has a README synced into this site on make docs-sync. Edit the source at crates/<name>/README.md, not the built copy under dev/crates/.

None of the workspace crates are published to crates.io / docs.rs today. Research crates set publish = false. Until a crate is published, use the README on this site and cargo doc -p <crate> --open locally — do not add docs.rs badge URLs (they 404 and fail the link checker).

Crate	crates.io / docs.rs	Local rustdoc
Application + WASM + Hive crates	Unpublished	`cargo doc -p <crate> --open`
`chatty-trace`, `chatty-playbook`, `chatty-flow`, `chatty-optimize`	`publish = false`	`cargo doc -p <crate> --open`

When a crate is published, add a docs.rs badge here and on its README, and keep the crate-level //! docs complete enough for docs.rs.

Application crates

Crate	Purpose	README
chatty-core	UI-agnostic agent core: models, services, tools, settings, sandbox	`crates/chatty-core/`
chatty-gpui	GPUI desktop app — ships the `chatty` binary	`crates/chatty-gpui/`
chatty-tui	Ratatui terminal app — interactive, headless, and pipe modes	`crates/chatty-tui/`

WASM modules & protocols

Crate	Purpose	README
chatty-wasm-runtime	Wasmtime embedding and host-side WIT interfaces	`crates/chatty-wasm-runtime/`
chatty-module-registry	Module discovery, manifest, and lifecycle	`crates/chatty-module-registry/`
chatty-protocol-gateway	HTTP gateway: OpenAI / MCP / A2A protocol surfaces	`crates/chatty-protocol-gateway/`
chatty-module-sdk	SDK for authoring `wasm32-wasip2` agent modules	`crates/chatty-module-sdk/`

Research crates (Self-improving chatty2)

Reserved symbols and human-only entry points are listed in RESERVED.md. Linear project: Self-improving chatty2.

Crate	Purpose	README
chatty-trace	Trace capture, ATIF export, feedback hooks (M0)	`crates/chatty-trace/`
chatty-playbook	ACE-style playbook memory for evolving instructions (M4)	`crates/chatty-playbook/`
chatty-flow	AFlow workflow representation and IR (M2)	`crates/chatty-flow/`
chatty-optimize	GEPA/AFlow optimizers, paired stats, QA loaders (M3)	`crates/chatty-optimize/`

Hive integration

Crate	Purpose	README
hive-client	Open-source client for the Hive module registry	`crates/hive-client/`
hive-billing-sdk	Publisher SDK for Hive billing in WASM modules (separate `Cargo.lock`)	`crates/hive-billing-sdk/`

Dependency direction

flowchart TB
  gpui[chatty-gpui] --> core[chatty-core]
  tui[chatty-tui] --> core
  gateway[chatty-protocol-gateway] --> core
  registry[chatty-module-registry] --> runtime[chatty-wasm-runtime]
  runtime --> core
  trace[chatty-trace] -.-> core
  playbook[chatty-playbook] -.-> core
  flow[chatty-flow] -.-> core
  optimize[chatty-optimize] -.-> trace
  optimize -.-> playbook
  optimize -.-> flow

chatty-core never depends on a UI crate. Research crates integrate with production code but optimizer runs must not block the interactive chat path.

Workspace crate split — why the split exists
Component map — diagrams of how crates connect
Research pipeline — paper → experiment → product flow

Keyboard shortcuts