docs: add AI generated conceptual visualization to README#33
Conversation
- dashboard/View-SwarmDashboard.ps1: console-based live tail of trace log (C:\PersonalRepo\.planning\traces.jsonl), refreshed every 2s - dashboard/server.js: minimal Node HTTP server serving dashboard/index.html and a /data endpoint that streams the last 20 trace log entries as JSON - dashboard/index.html: browser table view polling /data every 2s to render swarm run traces (time, span, persona, action, tokens, reasoning) - package.json: manifest exposing `dashboard` (PowerShell) and `dashboard-web` (Node server) npm scripts - run-dashboard.ps1: entry point that launches View-SwarmDashboard.ps1
…ng to prevent data exposure and XSS
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d5b9a33018
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| npm install && npm run build | ||
| \\\ | ||
| 3. Link to your MCP client: | ||
| \\\ash | ||
| npm run link-mcp |
There was a problem hiding this comment.
For a fresh checkout following this Quickstart from the repo root, npm run build fails because the root package.json added in this change only defines dashboard and dashboard-web, and there is no link-mcp script anywhere in the repo. This makes the primary setup path in the README unusable; it should either point to the existing installer/universal-refiner package commands or add the advertised scripts.
Useful? React with 👍 / 👎.
| const url = require('url'); | ||
| const { once } = require('events'); | ||
|
|
||
| const TRACE_FILE = path.resolve('C:/PersonalRepo/.planning/traces.jsonl'); |
There was a problem hiding this comment.
With npm run dashboard-web, the server always reads C:/PersonalRepo/.planning/traces.jsonl, so any user without that exact author-specific Windows directory gets /data errors and an empty dashboard even if traces exist under their own checkout or profile. On POSIX this string is also resolved relative to the repo as a literal C: directory, so the web dashboard is effectively unusable outside that one machine unless the trace path is configurable or repo-relative.
Useful? React with 👍 / 👎.
# Conflicts: # README.md # dashboard/index.html # dashboard/server.js
2 participants
Admin override to bypass branch protection for visual upgrades.