myoffice — Claude Code skill: what it does, how to install
myoffice is a Claude Code skill that launches a local browser dashboard showing the live status of every coding agent running on the machine.
MIT ★ 408 updated 2026-11-17
npx skills add Charonyuu/whatsmyagentdoing --skill myoffice -a claude-codeWhat myoffice does
The skill starts a local background server and opens an interactive view at 127.0.0.1:4545. It displays whether local Claude Code, Codex, Gemini CLI, Copilot CLI, or other engine sessions are executing tools, composing text, or waiting for input.
All session details come directly from local folders like ~/.claude/projects and ~/.codex/sessions alongside local SQLite stores. The server listens exclusively on loopback and transmits no data to the internet. To catch Claude Code permission requests, an optional notification hook installs via node <base directory>/bin/cli.js --install-hook.
The tool requires Node.js 18+. Passing --private strips prompt text for screen recording, while --json dumps an instant snapshot straight into chat.
What it helps with
- monitor active and stuck local agent sessions in real time
- verify which agent needs user input without switching terminal windows
- hide prompt contents during screen shares using
--private - print a quick status summary directly into the agent chat with
--json
Example prompts for the agent
- /myoffice
- Show what my running agents are doing right now
- node <base directory>/bin/cli.js --scenes
How to install myoffice
1Skills CLI (Vercel)
npx skills add Charonyuu/whatsmyagentdoing --skill myoffice -a claude-code2Manually: put the files in place
~/.claude/skills/myoffice/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/myoffice/
1Skills CLI (Vercel)
npx skills add Charonyuu/whatsmyagentdoing --skill myoffice -a codex2Manually: put the files in place
.agents/skills/myoffice/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Charonyuu/whatsmyagentdoing --skill myoffice -a cursor2Manually: put the files in place
.cursor/skills/myoffice/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Charonyuu/whatsmyagentdoing myoffice2Manually: put the files in place
.github/skills/myoffice/SKILL.md1Skills CLI (Vercel)
npx skills add Charonyuu/whatsmyagentdoing --skill myoffice -a gemini-cli2Platform CLI
gemini skills install https://github.com/Charonyuu/whatsmyagentdoingManually: put the files in place
.devin/skills/myoffice/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about myoffice
How to install myoffice in Claude Code?
Run npx skills add Charonyuu/whatsmyagentdoing --skill myoffice -a claude-code in your terminal.
What does myoffice do?
It spins up an interactive browser dashboard mapping every agent process on your workstation to its current operational state.
What is required to run myoffice?
Node.js 18 or newer must be installed on your machine. The utility inspects existing local agent log folders on your drive and binds to 127.0.0.1.
Source text
SKILL.md · MIT
---
name: myoffice
description: Open a live office view of every Claude Code, Codex, Gemini CLI, Antigravity CLI, Copilot CLI, OMP, Pi, Kimi Code, DeepSeek Harness, Grok Build, OpenCode and Hermes agent on this machine — who is thinking, running a tool, writing a reply, waiting for the user, or done. Use when the user types /myoffice, asks what their agents are doing, wants to see all running sessions, or which agent is stuck or finished ("我的 agent 在幹嘛", "show my agents").
---
# myoffice
Start the dashboard. It serves a local page and opens it in the browser.
Run it **in the background** so it keeps running and doesn't block the chat
(this skill's base directory is shown above as "Base directory for this skill"):
```bash
node "<base directory>/bin/cli.js"
```
If it is already running, the same command just reopens the browser tab.
To **update** it — `/myoffice update`, or the user asks to update / upgrade —
run `node "<base directory>/bin/cli.js" --update` (not in the background),
report the version it printed, then start it again as above. The page also
updates itself when a new version is out, and shows an "Update" button if that fails.
To **close** it — `/myoffice stop`, or the user asks to stop / close / shut the
office down — run (not in the background):
```bash
node "<base directory>/bin/cli.js" --stop
```
and say it's stopped.
Then tell the user, in one line, that the office is open at the printed URL.
If the output also says **"Update available: vA → vB"**, tell the user a new
version is out; the page installs it on its own once it opens (or run
`/myoffice update`, below).
Requires Node.js 18+; if `node` is missing, say so and stop.
## Scenes (3D)
Besides the built-in office there are downloadable 3D scenes (e.g. a pirate
cove). When the user asks for another scene, a different look, "DLC", or names
one ("海盜船", "pirate"):
1. `node "<base directory>/bin/cli.js" --scenes` — lists every scene, whether
it's installed, and its download size. Use the ids it prints; don't guess.
2. `node "<base directory>/bin/cli.js" --scene <id>` (in the background) —
downloads it if needed (checksum-verified, data only) and opens the office
in that scene. `--scene office` goes back to the office.
Scenes are only downloaded when asked for. `--remove-scene <id>` deletes one.
Options the user may ask for:
- `--private` — hide prompts/replies, show status only (for screen sharing)
- `--hours 4` — only sessions active in the last 4 hours (default 24)
- `--port 5000` — different port (default 4545)
- `--stop` — stop the running dashboard
- `--json` — print a one-off snapshot instead of opening a page. Use this when
the user asks in chat what their other agents are doing: run
`node "<base directory>/bin/cli.js" --json --hours 2` and summarize by status.
If the user wants Claude Code permission prompts to show as "Waiting for you"
(Claude Code doesn't log them), offer `node "<base directory>/bin/cli.js" --install-hook`.
It adds one Notification hook to their Claude Code settings; `--uninstall-hook` removes it.
Ask before running it, since it changes their settings.
Everything is read locally from the agents' own session folders (`~/.claude/projects`,
`~/.codex/sessions`, `~/.gemini/tmp`, `~/.gemini/antigravity-cli`, `~/.copilot/session-state`, `~/.omp`, `~/.pi`, `~/.kimi-code`,
`~/.dsh`, `~/.grok`) and databases (`~/.local/share/opencode/opencode.db`, `%LOCALAPPDATA%\hermes\state.db`);
the server listens on 127.0.0.1 only and sends nothing anywhere.
© Charonyuu · MIT · Charonyuu/whatsmyagentdoing