@gfgghgftgffg/rpiv-todo-lean
Lean Pi todo extension: the full @juicesharp/rpiv-todo runtime with a compact flat schema and per-session RPC overlay handling preserved.
Package details
Install @gfgghgftgffg/rpiv-todo-lean from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@gfgghgftgffg/rpiv-todo-lean- Package
@gfgghgftgffg/rpiv-todo-lean- Version
0.1.13- Published
- Oct 30, 2026
- Downloads
- 1,545/mo · 933/wk
- Author
- gfgghgftgffg
- License
- MIT
- Types
- extension
- Size
- 43.9 KB
- Dependencies
- 2 dependencies · 4 peers
Pi manifest JSON
{
"extensions": [
"./index.ts"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
@gfgghgftgffg/rpiv-todo-lean
Part of the amox-pi-extensions-lean monorepo. A lightweight Pi facade for
@juicesharp/rpiv-todo: the
complete task-management engine behind one compact todo tool. Runtime updates follow upstream.
Original lean facade by kunkun9527; upstream extension
by juicesharp. Both are MIT-licensed; the original LICENSE
is preserved in this package.
Core features
- Keeps upstream task lifecycle, dependencies, batch creation and the
/todosinterface. - Compact descriptions and schema retain native fields, validation, persistence and session isolation.
Installation
This is a public npm package. Install without a version pin:
pi install npm:@gfgghgftgffg/rpiv-todo-lean
pi update --extensions
For a Git fallback, run from the repository checkout:
node scripts/install-extension.mjs rpiv-todo-lean
Update a local Git installation by pulling the checkout and rerunning its installer; pi update does not update local contents. Keep one installation source. To migrate, back up settings, remove only the exact old source shown by pi list, then install the npm source. Do not load another rpiv-todo wrapper alongside it.
Usage
The model sees one tool, todo, with actions create, update, list, get, delete, clear.
action is normally required; when it is omitted the facade infers create from subject or
update from id plus a mutable field, and otherwise lets upstream report the error.
Create a task with subject; batch creation uses action: "create" and tasks, for example
{"action":"create","tasks":[{"subject":"Inspect"},{"subject":"Test"}]}.
Use id to update or retrieve a task and blockedBy for dependencies.
New tasks default to pending. For multi-step work, keep one task in_progress and mark it
completed promptly when finished. list excludes deleted tasks by default; clear empties the list
and resets IDs. See the upstream documentation
for all fields, batch rules and /todos usage.
Context footprint (character proxy)
| Package | Registered character proxy |
|---|---|
| @gfgghgftgffg/rpiv-todo-lean | 277 |
| @juicesharp/rpiv-todo | 1222 |
Fixed ceil(characters / 4), not provider billing tokens.
Development
See the development and maintenance guide and MAINTENANCE.md for adaptation details.