From adk
Explains the ADK Dev Console UI — tabs, Agent Steps, traces, component registry, and how to read execution data at localhost:3001 during adk dev.
How this skill is triggered — by the user, by Claude, or both
Slash command
/adk:adk-dev-consoleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The Dev Console is a local app served at port `3001` (by default, but can be customized) during `adk dev`. It gives developers real-time visibility into their agent's behavior — conversations, execution traces, data, integrations, and configuration.
The Dev Console is a local app served at port 3001 (by default, but can be customized) during adk dev. It gives developers real-time visibility into their agent's behavior — conversations, execution traces, data, integrations, and configuration.
Activate when users ask about:
localhost:3001, "dev console", "Dev Console", "component registry", or specific tab names (Chat, Build, Components, Data, Test, Observe, Config)| File | Contents |
|---|---|
references/agent-steps.md | Agent Steps visualization — turns, iterations, tools, messages, state mutations, cost tracking, status indicators |
references/pages.md | Every page/tab in the Dev Console — what it shows, key features, layout |
references/component-registry.md | Component Registry — installed vs registry tabs, component lifecycle, runtime registry internals, UI features |
Match depth to the question:
| Group | Pages | Purpose |
|---|---|---|
| Chat | Chat | Test the agent via webchat + see Agent Steps |
| Build | Story | Visual agent flow graph (feature-flagged) |
| Components | Webchat Components, Actions, Workflows, Triggers | Browse component registry, test bot primitives |
| Test | RAG Search, Evals | Test knowledge search and run automated evals |
| Data | Knowledge, Tables, Files | Manage knowledge bases, tables, and files |
| Observe | Conversations, Traces, Logs | View conversation history, execution traces, runtime logs |
| Config | Settings, Integrations | Agent config, secrets, LLM settings, integration management |
The right panel of the Chat page shows Agent Steps — a real-time visualization of what the agent did to process each message.
Hierarchy: Turn → Iterations → Tools / Messages / State Mutations
Status indicators: ✓ green = ok, ✗ red = error, ⟳ blue spinning = running
AI metrics per iteration: model name, input/output tokens, cost (USD)
| Path | Page |
|---|---|
/chat | Chat + Agent Steps |
/components | Component registry + installed components |
/actions | Actions browser |
/workflows | Workflows + run history |
/search | RAG search testing |
/evals | Eval definitions + runs |
/knowledge | Knowledge base management |
/tables | Table data management |
/traces | Full trace viewer |
/conversations | Conversation history |
/logs | Runtime logs |
/settings | Agent configuration |
/integrations | Integration management |
npx claudepluginhub botpress/skills --plugin adkSystematic debugging for ADK agents — trace reading, log analysis, common failure diagnosis, and the debug loop.
Provides the full ADK agent development lifecycle: scaffold, build, evaluate, deploy, publish, and observe. Entrypoint for building agents with google-agents-cli.
Guides Claude Agent SDK development in TypeScript/Python: auth, sessions, custom tools, permissions, prompts, tracking via docs-management delegation.