Who it is forA developer running Codex or Claude Code on a local project who wants to see which tasks the agent has reported and what is still in progress.
The problemAgent activity is spread across terminal windows and logs, so it is hard to tell what is being worked on and what is finished.
The outcomeA browser view at localhost:4780 that shows chefs, order tickets and completed deliveries based on local agent activity and native todos.
What you need first
- Node.js 20 or newer
- A browser with WebGL
- A local project folder (a git repo and PLAN.md are optional)
Steps
- Open a terminal in the repo you want to watch.
- Run
npx agenttrail-kitchen . - Wait for the browser to open at localhost:4780 (or the next free port) and keep this terminal open.
- Keep working in Codex or Claude Code and watch tickets and chefs update in Live mode.
- Click a chef or ticket to inspect its evidence.
Prompt for your agent
In the repo <repo-path>, run `npx agenttrail-kitchen .` and confirm the browser opens at localhost:4780 or the next free port. Report the URL that is shown. Verify that the terminal stays running and that the view is in Live mode, not Example mode.
Caveat. Kitchen is an experimental public preview, and if no activity is available the chefs simply wait, so a quiet view does not always mean an error.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page