-
Notifications
You must be signed in to change notification settings - Fork 125
Open
Description
Plannator is already quite nice tool, but following is somewhat problematic to use with multiple claude instances.
Issues I encounter currently are:
- I forget in which terminals claude is still processing and where plan was already created; solutions for this are tools like https://github.com/masx200/claudecodeui help with that so you don't waste time switching sessions, or worse, on idling until you discover something ended long time ago
- this is related to plannator, as plannator will pop-up a window asking about plan while I work on something else already - which is not terrible, but somewhat distracting
- same thing happens if I confirm plan in the terminal instead a browser (which happens often as I jump from window to window)
- this is further worsened by the fact I sometimes don't close that window after approval and when I revisit that browser tab I have to wonder is this a new plan? already executed plan? (related: Add the ability to auto close the tab on approval #128 )
Solution would be, to spawn a single plannator instance (from first plannator plan call, some lock would be nice there), and add each new planning session as within plannator interface (important: each new plan from same claude session should replace previous one).
Approving plan would also be to inform that single plannator instance that a particular session plan can be closed (archived?).
This will also solve #102 .
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels