How diillson/chatcli works
ChatCLI is a multi-surface assistant and autonomous coding platform. A user submits a chat turn or task through the terminal, an editor, a chat integration, or a server interface; ChatCLI routes it through its chat or agent runtime, which can call models and tools, then returns a response or streamed run. Other documented capabilities include model orchestration, quality patterns, persistent context and memory, task graphs, integrations, dashboards, and Kubernetes operations. The README and selected excerpts support the main runtime links; unsampled subsystem wiring is not inferred.
Main entry points: chat_pipeline.go Chat turn pipeline · worker_react.go Coder and agents · pipeline.go Pipeline RPC · llm_manager.go Provider manager
Components 24
User surfaces
- Interactive CLI
cli/cli.go - Browser UI
cli/webui/server.go - ACP server
cli/rpcserve/acp.go - Chat gateway
cli/gateway/gateway.go - Pipeline RPC
server/pipeline.go
Chat and agent runtime
- Chat turn pipeline
cli/chat_pipeline.go - Coder and agents
cli/agent/workers/worker_react.go - Tool safety policy
cli/coder/policy_manager.go - Task graph engine
cli/taskgraph/engine.go
Models and quality
- Provider manager
llm/manager/llm_manager.go - Quality harness
cli/agent/quality/pipeline.go - Usage pricing
llm/pricing/engine.go
Context and state
- Context retrieval
cli/ctxmgr/manager.go - Workspace memory
cli/workspace/memory.go - Session and state storage
cli/storage.go
Integrations and operations
- MCP integration
cli/mcp/manager.go - Plugin system
cli/plugins/manager.go - Live dashboard
cli/pulsedash/server.go - Kubernetes operator
operator/main.go - Rollback controller
operator/controllers/rollback_engine.go
Other components
- Terminal user
- Editor clients
- Chat apps
- RPC clients
Connections 23
- Terminal user → Interactive CLI: submits turns
- Editor clients → ACP server: send requests
- Chat apps → Chat gateway: send messages
- RPC clients → Pipeline RPC: invoke pipeline
- Interactive CLI → Chat turn pipeline: runs turns
- Chat turn pipeline → Provider manager: requests completions
cli/chat_pipeline.go - Chat turn pipeline → Quality harness: uses harness
cli/chat_pipeline.go - Chat turn pipeline → Context retrieval: retrieves context
- Chat turn pipeline → Workspace memory: uses memory
- Chat turn pipeline → Session and state storage: persists sessions
- Coder and agents → Tool safety policy: checks tool access
- Coder and agents → Provider manager: requests completions
- Task graph engine → Coder and agents: dispatches workers
cli/taskgraph/engine.go - Task graph engine → Session and state storage: saves run state
cli/taskgraph/engine.go - Provider manager → Usage pricing: reports usage
- MCP integration → Coder and agents: provides tools
- Plugin system → Coder and agents: extends tools
- Pipeline RPC → Chat turn pipeline: hosts backend
- Pipeline RPC → Coder and agents: runs tasks
server/pipeline.go - Browser UI → Chat turn pipeline: serves assistant
- Chat gateway → Chat turn pipeline: shares sessions
- Live dashboard → Kubernetes operator: visualizes runtime
- Kubernetes operator → Rollback controller: uses controller
operator/main.go