Practical overview
When it fits
Use Map for a project-level view of structure and file activity, or Kitchen when you want to follow available tasks and role contributions in a 3D scene.
Who it is for
- Developers monitoring AI coding work in a local project.
- Teams using supported Codex or Claude workflows who want a visual view of activity and tasks.
- Developers who want project structure and changing components in Map or a task-and-role scene in Kitchen.
Documented uses
- See which project components and files are changing.
- Inspect tasks reported through available native todos.
- View role contributions and activity from supported local agent sessions.
- Review evidence associated with a chef or ticket in Kitchen.
Requirements & limits
Kitchen setup requires Node.js 20 or later, a browser with WebGL and a local project folder. The README describes Kitchen as a public experimental preview.
- Map can show file activity without a plan, but its component map needs
PLAN.md. - Kitchen can use available native todos as tickets; without a plan, progress can remain unknown.
- Codex local sessions and Claude Code logs are supported; Cursor hook setup is described, but native Cursor live validation is pending.
- VS Code and Cursor use Agenttrail as a browser companion rather than a shipped editor extension.
- Activity coverage and history differ between Map and Kitchen.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start Agenttrail Kitchen in a project
Open Kitchen to observe available local coding-agent activity and tasks for a project.
Before you start
- Node.js 20 or later
- A browser with WebGL
- A local project folder
Steps
Run the command below in the repository you want to watch.
npx agenttrail-kitchen .Open the browser view at localhost:4780, or use the next free port shown.
Keep the terminal open and continue working in the coding agent.
Expected outcome
Kitchen displays available local activity and supported native todos in its task-and-role visualization.
Guide limitations
- This is a public experimental preview.
- Kitchen does not launch agents or edit the repository.
- Confirmed handoffs and explicit sharing of one todo across sessions require extra metadata.
- Missing plans remain progress unknown; an ended turn does not mean a deliverable shipped.
Compare options for AI coding assistance
These projects document a common task and share a project role. This is a source-based comparison, not an execution benchmark or a guarantee of interchangeability.
| Project | Documented purpose | Platform | Access and requirements |
|---|---|---|---|
| Agenttrail | See which project components and files are changing. | CLI, Desktop | Kitchen setup requires Node.js 20 or later, a browser with WebGL and a local project folder. The README describes Kitchen as a public experimental preview. |
| Harness Score | Measure the presence and structure of agent guidance, skills, hooks, feedback tools and safeguards. | CLI | The project is documented as a CLI and is MIT-licensed. The README shows invocation through `npx harness-score` and references a GitHub Action. |
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- sodiumsun/agenttrail · Official homepage title · retained in its source language