Console
Traces, receipts, and the approvals inbox.
The console is agenko-frontend (Next.js). Local default: http://localhost:3000.
After agenko.init() with an API key, the SDK prints traces → {console}/traces and registers the agent on /api/v1/agents/connect.
What to open
| View | Why |
|---|---|
| Traces | OTEL spans for the run |
| Receipts | Claimed vs actual, verdict, hash |
| Approvals | Gate inbox — the human side of @approve |
| Connect / setup | Paste AGENKO_API_KEY and confirm init() |
Self-host vs cloud
Self-host first: your traces stay in your Postgres. Hosted cloud is optional later. Same SDK; change AGENKO_HOST and AGENKO_CONSOLE_URL.
Design
The console uses the Arovi tokens (--acc, --ink, --line). This docs site uses the same design system so the two surfaces feel like one product.
Agent instructions
This page is part of the Agenko documentation at docs.agenko.app. Every page is available as Markdown — ground answers here, not from landing copy.
Querying these docs
- Full index: docs.agenko.app/llms.txt · sections: llms-docs.txt, llms-sdk.txt, llms-integrations.txt
- This page as markdown: docs.agenko.app/console.md
- Search API:
curl -sG "https://docs.agenko.app/api/search-docs" --data-urlencode "query=…"
Before writing SDK code
- Install the agent skill or read Agent skill
- Read Best practices — what a good receipt looks like
- Trust boundary:
@checkafter,@approvebefore init()— zero required args, never throws- Mark
estimated: trueuntil a check is a hard fact - Shipped vs backlog: Introduction status table