Docs/Reference

Architecture

How the Gray crates fit together — the agent loop, provider streaming, the bash tool surface, plugins and package management.

Source: Cargo.toml

CrateResponsibility
grayREPL, TUI, onboarding, config, CLI, sessions, memory, cron, gateway
gray-corethe agent loop, typed events, message model, compaction
gray-providerOpenAI-compatible SSE streaming, retries, prompt caching
gray-toolsbash plus profile-selectable read, write, edit, grep, find, ls
gray-pluginplugin trait, sidecar transport, gray.yml profiles, capabilities, scanning
gray-pkgplugin package management
gray-markdownstreaming markdown renderer for the TUI

Everything is streaming-first: text deltas, tool calls and usage arrive as typed events, which is what lets the TUI render a turn as it happens rather than after it finishes, and what --json serializes for harnesses.

Join the Discord

Chat with the people building and running Gray. Show what you made with it.

Join Discord →

Need help?

Open an issue on GitHub, run /feedback from the REPL, or ask in Discord.

Open an issue →