AgentsKit Chat
Build one versioned chat application and render it natively across every supported AgentsKit client.
Experience layer (alpha) on the AgentsKit foundation. Primitives (controller, tools, memory, RAG, framework bindings) stay upstream; this product owns application composition and versioned boundaries.
Define routes, actions, components, sessions, and backend seams once. AgentsKit Chat composes those application concerns over AgentsKit, then each supported framework renders them natively.
Start with a working shell
pnpm dlx @agentskit/chat-cli@0.4.1 init my-chat --renderer react --yes
cd my-chat
pnpm install
pnpm testThe CLI creates a shared definition, Web-standard handler, native shell, test, and architecture note. Choose another supported renderer in the framework quick starts.
Choose the shortest path
Architecture
Understand ownership and upstream boundaries.
Routes and state
Define deterministic conversation paths.
Action policy
Register actions, policy, and confirmation.
Grounded backend
Connect hosted or self-hosted Ask.
API reference
Look up exported public contracts.
Compatibility
Verify supported package versions.
Missing framework-neutral primitives are fixed in AgentsKit first. Chat owns application composition and versioned boundaries; it does not copy the controller, lifecycle, tools, memory, RAG, or framework bindings.
Continue through the ecosystem
Every product is optional. Follow the next problem, not a prescribed suite.
AgentsKit
Build or extend the underlying agent.
Registry
Start from a ready-to-adapt agent.
Agents Playbook
Apply delivery and engineering standards.
Doc Bridge
Make repository documentation agent-ready.
Code Review
Review the implementation before merge.
AKOS
Add enterprise orchestration and controls.
For agent consumption, use llms.txt, the full corpus, canonical Markdown from each page, or the for-agents handoffs.
