Skip to content
Back to search

pi-goal

Persistent autonomous goals for pi

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/michaelliv--pi-goal/badge.svg)](/listings/michaelliv--pi-goal)

HTML

<a href="/listings/michaelliv--pi-goal"><img src="/api/listings/michaelliv--pi-goal/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

pi install npm:pi-goal

Or from git:

pi install git:github.com/Michaelliv/pi-goal

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 76 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # pi-goal
  2. ![pi-goal](docs/assets/pi-goal-poster.png)
  3. Persistent autonomous goals for [pi](https://github.com/badlogic/pi-mono).
  4. `pi-goal` adds a `/goal` command and goal tools so Pi can keep working toward a long-running, thread-scoped objective until the goal is complete, paused, cleared, or token-budget-limited.
  5. ## Install
  6. ```bash
  7. pi install npm:pi-goal
  8. ```
  9. Or from git:
  10. ```bash
  11. pi install git:github.com/Michaelliv/pi-goal
  12. ```
  13. ## Usage
  14. ```text
  15. /goal improve benchmark coverage until the suite has strong evidence
  16. /goal --tokens 50k finish the migration and verify tests
  17. /goal
  18. /goal status
  19. /goal pause
  20. /goal resume
  21. /goal clear
  22. /goal statusbar off
  23. ```
  24. When a goal is active, the extension shows compact visible lifecycle markers like `Goal active` and `Goal continuing`; expand them with `ctrl+o` to inspect the objective and usage. The full continuation instructions ride along as the content of that custom message, so the model always has the objective and audit guidance in the transcript while the renderer keeps the visible UI compact.
  25. The same Pi agent keeps running normal turns in the same session context until it calls `update_goal({ status: "complete" })`, the user pauses/clears it, or the token budget is reached. Reloading Pi pauses an active goal instead of silently resuming it; use `/goal resume` to continue.
  26. ## What it adds
  27. - `pi-goal-writer` skill: draft and review strong `/goal` objectives with evidence-based success criteria
  28. - `/goal [--tokens 50k] <objective>`: set or replace a goal
  29. - `/goal` or `/goal status`: show the current goal
  30. - `/goal pause`: stop autonomous continuation without deleting the goal
  31. - `/goal resume`: reactivate a paused goal
  32. - `/goal clear`: remove the goal
  33. - `/goal statusbar on|off`: show or hide the footer status line
  34. - `create_goal` tool: model can set or replace the current goal only when explicitly requested
  35. - `get_goal` tool: read current goal state
  36. - `update_goal` tool: model can only mark the goal `complete`
  37. - `get_goal` and `update_goal` are only exposed to the model while a goal is `active`; paused, cleared, complete, and budget-limited goals hide them so unrelated sessions are not tempted to call them
  38. - footer status: `Pursuing goal`, `Goal paused`, `Goal achieved`, or `Goal unmet`
  39. ## Flow
  40. ```text
  41. /goal <objective>
  42. -> persist goal in the current Pi session
  43. -> show compact Goal marker and footer status
  44. -> deliver continuation instructions as the marker's message content
  45. -> trigger an agent turn
  46. -> account time/tokens on turn_end
  47. -> queue another continuation on agent_end while active
  48. -> stop when update_goal marks complete, user pauses/clears, or budget is hit
  49. ```
  50. ## Completion behavior
  51. The model is instructed to audit completion against real evidence before calling `update_goal`. The `update_goal` tool deliberately accepts only `status: "complete"`; pausing, resuming, clearing, and budget limiting are controlled by the user or extension runtime. The final turn is still accounted even when the model completes the goal mid-turn.
  52. ## State
  53. Goal state is stored as Pi custom session entries with `customType: "pi-goal"`. It follows the active session branch, survives reloads, and does not require an external database.
  54. ## License
  55. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.