Skip to content

docs: add observe-and-operate capability to overview #367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
codeaholicguy merged 2 commits into from
Oct 10, 2026
Merged

docs: add observe-and-operate capability to overview #367

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ebaa684
docs: add status, capacity, and daemon to the overview
codeaholicguy Oct 10, 2026
7113018
docs: point overview links at the split capacity/runtime pages
codeaholicguy Oct 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 11 additions & 1 deletion web/content/docs/0-what-is-ai-devkit.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,16 @@ The [Memory](/docs/6-memory) service gives your coding agents persistent, local

AI DevKit isn't tied to a single tool. It supports [many AI coding environments](/docs/2-supported-agents) and sets up the right configuration files, skills, and instructions for each one. Switch between agents or use multiple at the same time. Your workflows, memory, skills, and operating model carry across supported environments.

### Observe And Operate

AI DevKit ships with a local coordination daemon (`devkitd`) that runs agent detection and session routing, plus operational commands for day-to-day checks:

- `ai-devkit status` reports readiness for your whole setup — CLI version, per-agent health, tmux, registries, channels, and memory MCP wiring
- `ai-devkit capacity` shows remaining quota across your logged-in providers (Codex, z.ai, OpenAI, Anthropic, Claude, Devin) so you can pick the agent with the most headroom
- `ai-devkit daemon` manages the background daemon; it auto-starts on first use, so no manual step is needed

See [Status & Capacity](/docs/15-capacity) and [Runtime (devkitd)](/docs/16-runtime) for details.

## A Typical Workflow

Here's what working with AI DevKit looks like in practice:
Expand All @@ -98,7 +108,7 @@ Project initialization and lifecycle work produce documentation in `docs/ai/`, g

1. **Connect** - Run `npx ai-devkit@latest setup` once per machine to connect detected agents and install their global workflow skills.
2. **Initialize** - Run `npx ai-devkit@latest init` once per project to create workflow docs and environment-specific project configuration.
3. **Operate** - Use `agent list`, `agent console`, and `agent send` to supervise and route work across running local agents.
3. **Operate** - Use `agent list`, `agent console`, and `agent send` to supervise and route work across running local agents; use `status` and `capacity` to check readiness and provider quota.
4. **Develop** - Ask the agent to use installed workflow skills such as `dev-lifecycle`, `tdd`, and `verify` so it follows the workflow instead of improvising in chat.
5. **Remember** - Store important decisions and patterns in memory so they persist across sessions.
6. **Extend** - Install skills to give your AI specialized knowledge for your stack and domain.
Expand Down
Loading