Agent Office
github.com/alminisl/agent-office- Category
- Developer Tools
- Rank
- No. 1869Tools index
Previous survey · No. 1787 ·
- Type
- TOOL
- Use case
- Agent Building
- Interfaces
- Web
- GitHub
- 9 stars
- Date
About
Agent Office is a zero-dependency Node.js server with a canvas front end that reads the session data Claude Code already stores locally and renders each active session as a pixel-art coworker at a desk in an office. Sessions are grouped by project and shown with a status, personality, and career, so a developer running multiple Claude Code sessions at once can see at a glance which ones need attention and jump back into any session with one click.
At a glance
Agent Office gives each Claude Code session a pixel-art coworker, with a desk and a status showing whether it is working or needs you. A local Node server reads the transcripts and live session files already on your machine. The office also offers optional AI summaries, conversations and background workers.
Good fit
Consider it when several Claude Code sessions make it hard to spot the one waiting for input. The useful part of the playful office is its Needs you view and session details. The public demo separates working, waiting and finished sessions; its employees and spending figures are simulated, so it demonstrates the interface rather than proving live monitoring works.
Consider something else when
You want a dashboard for every coding agent, audited measures of code quality, or a clearly licensed component to redistribute. The implementation targets Claude Code’s local files. XP, motivation and character relationships are game mechanics, not evidence that an agent did good work.
Start here
Open the public demo and its Office dashboard, then inspect Needs you before exploring the leaderboard. For your own sessions, the documented local entry point is npm start in the repository, followed by http://localhost:4747. Start with status viewing; connecting office tools or hiring a Fixer adds capabilities beyond watching sessions.
Cost and requirements
The manifest requires Node.js 18 or newer and has no package dependencies. Real session viewing needs an existing Claude Code installation and transcripts. AI features use your Claude account and consume its usage. Terminal launching is documented for macOS and Linux. The README still lists the licence as TBD.
Limits to know
The server binds to the local machine, but Ask, the PM and standups can send session content or briefings through the Claude CLI. Fixers can edit and commit in separate worktrees. Personalities can also add instructions to sessions started from the office. Treat those features as changes to how agents work, rather than decorative dashboard controls. Defaults show fourteen days of recent sessions and twenty cubicles, with running sessions always included.
Related work
Still unclear
- Which licence will govern reuse and redistribution? The README currently says TBD.
Sources checked 2026-10-30. Source-based assessment.
Why it made the leaderboard
It turns invisible parallel Claude Code sessions into an at-a-glance pixel-art office, so you can see which sessions are waiting on you without tabbing through terminals.
Intel on Agent Office
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.