@plannotator/pi-extension
Interactive plan review with annotations — mark up agent plans and messages before execution.
Install
pi install npm:@plannotator/pi-extension
Installs from npm into ~/.pi/agent/.
Add -l for project-local (.pi/). Manage with pi list / pi update / pi remove.
What this package can reach
Detected automatically from the source at
version 0.25.1.
This describes access, not safety — you decide whether it's appropriate for what
the package claims to do.
- Behavior — Changes how the agent thinks Modifies the system prompt, injects messages, or rewrites conversation context.
- Extension bus — Talks to other extensions Uses pi.events to emit or listen on a shared channel, so it can coordinate with — or be driven by — other installed extensions.
- Commands — Runs shell commands Spawns processes on your machine.
- Credentials — Handles your API keys Reads or passes provider credentials. Highest-trust capability there is.
- Files — Reads files outside your project Touches paths beyond the working directory, such as your home folder.
- Intercepts tools — Can block or rewrite tool calls Subscribes to tool_call/tool_result/input. Can change a command after you approved the one displayed.
- Network — Talks to the internet Makes outbound network requests. Check the destinations are ones you expect.
- Subagents — Spawns agents or sessions Runs additional agents. Ask whether it caps iterations and spend.
- Tool control — Can switch pi's tools on and off Calls setActiveTools, so it can disable built-ins — including safety-relevant ones.
- New tools — Adds model-callable tools Gives the agent new abilities. Additive and visible, unlike an override.
- UI — Draws its own interface Renders widgets, footers, dialogs or full-screen views.
Network destinations found in the source (1)
r.jina.ai
Static analysis only — addresses built at runtime won't appear here.
What it actually did when run
observedLoaded in a sandbox with no network, a read-only filesystem and a recording stand-in for pi's API. This is what it called — not what the source suggests it might.
Tools registered plannotator_submit_plan
Events subscribed agent_endbefore_agent_startcontextplannotator:requestsession_shutdownsession_starttool_callturn_end
APIs called events.ongetActiveToolsgetActiveTools.filtergetThinkingLevelregisterCommandregisterFlagregisterShortcutregisterToolsessionManager.getBranchsessionManager.getSessionFilesessionManager.getSessionIdsessionManager.getSessionNameui.notifyui.setStatus
2 calls the source scan did not predict
events.on · getActiveTools.filter
Reached through a value the scan could not follow — passed as an argument, stored on another object, or returned by a helper.
Run against version 0.25.1 on 2026-08-01.
Registration-time behaviour under default settings; other configurations may differ.
Reviews
0 publishedSign in with GitHub to write a review, reply, or vote.
No reviews yet — be the first.
More in
- @dietrichgebert/ponytail — Lazy senior dev mode for AI agents — the best code is the code you never wrote. Bias towar…
- @juicesharp/rpiv-ask-user-question — A structured questionnaire the model can put to you when it would otherwise guess — answer…
- @juicesharp/rpiv-todo — A todo list for the model, rendered as a live TUI overlay that survives /reload.
- pi-prompt-template-model — Prompt template model selector for pi — route specific prompt templates to specific models…