File-based plans

[DanielusG]

In my experience, this plugin could become even more powerful if plans were first written in a markdown file and the model edit the plan file based on subsequent feedback, rather than rewriting the plan from scratch in a tool call.

I noticed that models tend not to rewrite the plan exactly as it was before, so there is a risk that a nice feature described prior to the feedback disappears immediately afterwards to include the new feedback provided.

Additionally, for long and detailed plans, the context window gets cluttered with continuous rewrites of entire plans when a simple call to the edit tool would suffice; it is faster and more efficient.

Is there a particular reason why a tool is simply used where the model has to write the entire plan?

[backnotprop]

@DanielusG this is for opencode right?

I agree. I think the OpenCode team is starting to write plans to files or it is in the works. I will make sure Plannotator taps into those.

[DanielusG]

@DanielusG this is for opencode right?

I agree. I think the OpenCode team is starting to write plans to files or it is in the works. I will make sure Plannotator taps into those.

Yes OpenCode, sorry I didn't check if Claude Code had the same problem, I assumed so.

[backnotprop]

Claude Code already does the plan writing to files. I saw dax tweet something about it last week. I will check progress

[backnotprop]

They just announced today

https://x.com/thdxr/status/2011204789607284974?s=20

[DanielusG]

So basically, now you'll modify the opencode implementation to add a hook when it enters plan_exit to launch your tool and provide feedback like in Claude Code, right?

[backnotprop]

That is the basic idea, yes. I need to look deeper at the implementation. It sounds like you have?