Skip to content

feat[pi]: plan mode - todos interoperatibilty with pi-todos #484

Closed as not planned

Description

@JayGhiya

Todos in pi-todos are editable and great for steering - https://github.com/mitsuhiko/agent-stuff/blob/main/pi-extensions/todos.ts so instead of markdown todos when pi-todos are available can we use that?

Activity

  1. backnotprop commented on Apr 5, 2026

    @backnotprop
    Owner

    Hey do you mean like embed the todos in the plan review ui?

  2. JayGhiya commented on Apr 6, 2026

    @JayGhiya
    Author

    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.

  3. JayGhiya commented on Apr 7, 2026

    @JayGhiya
    Author

    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

  4. jms830 commented on Jun 14, 2026

    @jms830
    Contributor

    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:

    1. 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.

    2. 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.

  5. backnotprop commented on Jul 27, 2026

    @backnotprop
    Owner

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions