@supierior/experimental-workflows
Experimental Workflower playground package for impractical workflows that demonstrate engine patterns.
Install
pi install npm:@supierior/experimental-workflows
Installs from npm into ~/.pi/agent/.
Add -l for project-local (.pi/). Manage with pi list / pi update / pi remove.
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 workflower_handoffworkflower_state_setworkflower_state_getworkflower_state_list
Events subscribed agent_endcontextinputsession_shutdownsession_start
APIs called registerCommandregisterMessageRendererregisterToolsessionManager.getSessionIdui.notifyui.setStatus
11 calls the source scan did not predict
on("agent_end") · on("context") · on("input") · on("session_shutdown") · on("session_start") · registerCommand · registerMessageRenderer · registerTool · sessionManager.getSessionId · ui.notify · ui.setStatus
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.1.0-beta.0 on 2026-08-02.
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 Modes & workflows
- pi-executor — Pi extension to run executor
- pi-gsd — Get Shit Done - Unofficial port of the renowned AI-native project-planning spec-driven too…
- @gonrocca/zero-pi-todo — zero-pi-todo — TODOs persistentes para pi, con tool, slash command y overlay aboveEditor.
- @siddr/pi-review — Interactive review mode extension for pi