@aetheros/control-room
v0.2.0
Published
Read-only Control Room for any AetherOS project: agents by department, guards, skills, features, specs, owner items, live agent activity and the last flow run, as a local page or a VS Code panel.
Readme
@aetheros/control-room
A read-only Control Room for any project. Each project can brand it with its own name and theme.
aether room # local page at http://127.0.0.1:4848/ (refreshes every 30 s)
aether room snapshot # the same data as JSON
aether room html room.html # a static page
aether room install-vscode # VS Code panel: run "AetherOS: Open Control Room"It shows:
- what's waiting on the owner and what's up next (from
HANDOVER.md) - agents running now
- agents grouped into departments: Plan, Build, Check, Ship (override in
.aether/departments.json) - guards (hooks), skills, features, spec approval states
- the last flow run (
aether run), recent activity, and the git branch and commits - Agent team: recent hand-offs between workspace agents (who asked whom, running, done or failed), by name only
- with
GITHUB_TOKEN: Building now on GitHub (open pull requests with check state, issues labelledin-progress) and the current sprint. Cached for 60 s;--no-githubturns it off
Agent activity comes from the Claude Code status-event.mjs hook. It stores only event kinds, agent types and times in .aether/local/events.jsonl, never prompts or answers, and that folder is git-ignored by its own .gitignore.
Safety:
- Read-only: it reads project files and runs
git log. - The server only listens on localhost and rejects foreign
Hostheaders. - Pages escape all project text and load nothing external; scripts are off in VS Code.
Limitations:
- One project per server or window.
- No owner actions from the page yet (slice 6).
- No voice screen.
- The VS Code extension is installed by copying it, not from the Marketplace, and hasn't been tested inside VS Code by CI.
