You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat[pi]: plan mode - todos interoperatibilty with pi-todos #484
Hey do you mean like embed the todos in the plan review ui?
Yes that is one improvement. But the second one is post submission todos should be created using pi todos extension of mitsuhiko if available as during progress upon looking at diffs and some thoughts dev might want to just update todos. The todos should be editable as shown here https://youtu.be/uPR7aAneg2U?si=OSXbKfYXCFjpd2I7. There might be technical constraints in making this work outside of pi for other coding agents but doing this for pi might be game changer.
integrating todos that can be modified just like "mitsuiko does in todo extension" - directly in plannotator might be very useful i also fear this kind of customisation can only happen in pi and not outside of pi but just for pi this might be game changes . :) curious to know your thoughts
Bumping this from the omp (oh-my-pi) side — running plannotator over a remote/Tailscale setup, I hit the same wall, and two things reinforce the ask:
omp ships a native collapsible todo panel (ctx.setTodos / a tool's details.phases → toggleTodoExpansion, auto-clear, strikethrough completion). But plannotator's execution tracker uses the basic ctx.ui.setWidget string-array (capped ~10 lines, not collapsible, not editable). So on omp the plan progress can't be minimized or edited even though the harness has a first-class todo UI sitting right there.
On the pi side, mitsuhiko's pi-todos (extensions/todos.ts) is file-backed — .pi/todos/<id>.md with JSON front-matter plus a todos tool (list/create/update/append/claim/release). That's a stable, documented surface, so integration doesn't need a new cross-extension protocol.
A feature-detected path looks tractable:
On plan approval, if a todos provider is present (pi-todos .pi/todos / todos tool, or omp's native panel), translate the plan checklist into editable todos instead of the markdown/setWidget tracker.
Reflect plannotator's existing [DONE:n] markers onto todo status (one-way sync — plannotator already parses these).
Fall back to the current markdown widget on harnesses without a provider.
The one-way direction (plannotator → provider + done-sync) seems like a focused change. Full bidirectional editing (user edits in /todos flowing back into plan execution) is the harder follow-up. It's inherently pi/omp-specific, so it'd be a conditional path — agreed it won't generalize to every harness, but pi+omp is where most of the steering value is.
Happy to open a PR if you're open to the feature-detected approach.
Closing to keep the tracker current, but this design is still good and both upstream APIs are confirmed current as of today: pi-todos still backs todos with .pi/todos markdown files, and oh-my-pi still exposes setTodos with phases. The one-way sync sketched in this thread (feature-detect a provider on plan approval, push the checklist, reflect DONE markers, fall back to the current widget) is exactly the right shape. We would gladly take a PR implementing it, and will reopen alongside one. Thanks for the detailed design work here.
Activity
backnotprop commentedon Apr 5, 2026
Hey do you mean like embed the todos in the plan review ui?
JayGhiya commentedon Apr 6, 2026
Yes that is one improvement. But the second one is post submission todos should be created using pi todos extension of mitsuhiko if available as during progress upon looking at diffs and some thoughts dev might want to just update todos. The todos should be editable as shown here https://youtu.be/uPR7aAneg2U?si=OSXbKfYXCFjpd2I7. There might be technical constraints in making this work outside of pi for other coding agents but doing this for pi might be game changer.
JayGhiya commentedon Apr 7, 2026
integrating todos that can be modified just like "mitsuiko does in todo extension" - directly in plannotator might be very useful i also fear this kind of customisation can only happen in pi and not outside of pi but just for pi this might be game changes . :) curious to know your thoughts
jms830 commentedon Jun 14, 2026
Bumping this from the omp (oh-my-pi) side — running plannotator over a remote/Tailscale setup, I hit the same wall, and two things reinforce the ask:
omp ships a native collapsible todo panel (
ctx.setTodos/ a tool'sdetails.phases→toggleTodoExpansion, auto-clear, strikethrough completion). But plannotator's execution tracker uses the basicctx.ui.setWidgetstring-array (capped ~10 lines, not collapsible, not editable). So on omp the plan progress can't be minimized or edited even though the harness has a first-class todo UI sitting right there.On the pi side, mitsuhiko's
pi-todos(extensions/todos.ts) is file-backed —.pi/todos/<id>.mdwith JSON front-matter plus atodostool (list/create/update/append/claim/release). That's a stable, documented surface, so integration doesn't need a new cross-extension protocol.A feature-detected path looks tractable:
.pi/todos/todostool, or omp's native panel), translate the plan checklist into editable todos instead of the markdown/setWidgettracker.[DONE:n]markers onto todo status (one-way sync — plannotator already parses these).The one-way direction (plannotator → provider + done-sync) seems like a focused change. Full bidirectional editing (user edits in
/todosflowing back into plan execution) is the harder follow-up. It's inherently pi/omp-specific, so it'd be a conditional path — agreed it won't generalize to every harness, but pi+omp is where most of the steering value is.Happy to open a PR if you're open to the feature-detected approach.
backnotprop commentedon Jul 27, 2026
Closing to keep the tracker current, but this design is still good and both upstream APIs are confirmed current as of today: pi-todos still backs todos with .pi/todos markdown files, and oh-my-pi still exposes setTodos with phases. The one-way sync sketched in this thread (feature-detect a provider on plan approval, push the checklist, reflect DONE markers, fall back to the current widget) is exactly the right shape. We would gladly take a PR implementing it, and will reopen alongside one. Thanks for the detailed design work here.
feat(pi): mirror plan checklist to pi-todos (#1139)