goalpulse
Site: https://raysca.github.io/goalpulse/
Visual progress reporting for agent-driven goals. Your coordinating agent reports tasks, assumptions, questions and status; you watch a live dashboard instead of a stream of text or a bloated progress.md.
Install
In Claude Code:
/plugin marketplace add raysca/goalpulse
/plugin install goalpulse@raysca-tools
Use
Tell your agent:
Use goalpulse to report progress on this.
That is all. The agent creates a goal, logs tasks and assumptions as it works, and replies with URLs for the dashboard on this computer and on the local network. The startup output prints QR codes for LAN links, and the dashboard has a Share to phone popup with scannable codes. The live dashboard is reachable from a phone or tablet on the same network by default. To pick work back up in a new session: "Resume the goalpulse goal."
The dashboard is read-only and has no authentication. By default, it listens on all network interfaces so your other devices can follow progress. Use it on a trusted network. If a local-only dashboard from an older version is running, the next goalpulse dashboard command restarts it with LAN access enabled.
Requires Node.js 18+. GoalPulse generates QR codes locally for LAN sharing; no external QR service is used. Logs live in .goalpulse/ in your project and are git-ignored by default (delete .goalpulse/.gitignore to commit them).
What you get
- Overview of every goal in the project, goals needing you first.
- Per goal: the coordinator's report, progress, what needs your attention (open questions, low-confidence assumptions, blocked work), task list and board, assumptions and best guesses, and an activity feed.
- Task dependency graph: follow prerequisite arrows, see what work can proceed in parallel, and select a task to inspect its details. Missing dependencies and possible cycles are called out.
- Mobile view: responsive task lists, wrapped summaries, reflowing board columns, and touch-sized controls make live progress easier to follow on phones and tablets.
- Share to phone: open the live dashboard on the same Wi-Fi with a QR code or direct LAN link from the dashboard popup.
- Resume: a fresh agent gets the goal and plan, current report, completed and in-flight work, stale tasks, risks, assumptions and your new answers, then continues from the workspace state.
- Parallel work: the skill identifies independent tasks and encourages explicit agent ownership and file boundaries so work can be split and integrated safely.
- Snapshots:
goalpulse render writes a single shareable HTML file.
Sub-agents report to the coordinator as usual; only the coordinator writes to the log, which keeps one voice.
Codex, Antigravity and other agents
The skill is a single SKILL.md (Agent Skills format), and the only other thing an agent needs is the goalpulse command.
npm install -g github:raysca/goalpulse # puts `goalpulse` on PATH (Node 18+)
cd your-project
goalpulse install-skill # -> .agents/skills/goalpulse (Codex, Antigravity)
goalpulse install-skill --global # -> ~/.agents/skills (Codex, every project)
goalpulse install-skill --agent claude # -> .claude/skills, if you skip the plugin
Then tell the agent: "Use goalpulse to report progress on this." If goalpulse is not on PATH the skill falls back to npx -y github:raysca/goalpulse.
For agents without skills support (Cursor, Copilot, Aider, ...), paste skills/goalpulse/SKILL.md into AGENTS.md or the goal prompt. The contract is just the CLI.
goalpulse dashboard --open # background dashboard (LAN accessible by default)
npm run demo # simulated run, three goals
Multiple goals in one project
Each goal has its own log, .goalpulse/goals/<slug>/events.jsonl, and its own tiny command. goalpulse goal "Title" creates both and prints how to call it (--id chooses the slug):
goalpulse goal "Fix flaky CI tests"
# .goalpulse/goals/fix-flaky-ci-tests/gp <- this goal's own command
.goalpulse/goals/fix-flaky-ci-tests/gp add "Reproduce locally" # the goal is built in: no --goal
.goalpulse/goals/fix-flaky-ci-tests/gp start T1 --by debugger-1
goalpulse goals # list all goals: health, progress, items needing you
The per-goal command (gp, plus gp.cmd on Windows) is a few lines that set the goal and the .goalpulse location, then call goalpulse. Hand it to a coordinator and it cannot log to the wrong goal, which matters because agent shells do not keep environment variables between calls. It finds .goalpulse relative to itself, so it works from any directory and survives moving the project, and goalpulse resume re-creates it if it is missing.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
