[FEATURE] have ultraplan run locally or be able to get local context
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
I liked ultraplan, the issue is that it doesn't have the same context as my local claude code instance in the terminal. It was doing planning without the full context and had no way when questions were asked to get that context loaded into. A key example was that it was looking for files on my local workspace to refine its plan. It couldn't access them as so the plan.
Proposed Solution
I would like to kick off ultraplan but when it wanted to ask questions be able to ask those questions and get persmissions to read something locally. I typically only use one claude session at a time with agents being spawned off, it would be good to have ultraplan somehow either talk/connect with my local instance or be able to ask me/it for access to the required materials it needs to improve its plan.
Alternative Solutions
The workaround I am currently using is to only use ultraplan for items that wouldn't need the context for the way i work, or local information. This practically means I won't be using ultraplan very often as sometimes i won't know that it may need this and that would be a wasted call.
Priority
Medium - Would be very helpful
Feature Category
Interactive mode (TUI)
Use Case Example
- I was working on a rework of a 2nd brain system i had been playing with. i was in rust, svelte and mentioned pg
- I had plan mode , spawned an agent to do research and then had claude build a plan
- As we exited plan mode i launched ultraplan
- Ultraplan had questions (i think, when i clicked the answer the questions link i didn't see questions just assumptions in the Ultraplan)
- The questions were around context and content that I had locally that were in the plan, so day to day unless ultraplan can talk to my local setup or be able to get the context it isn't as useful as i had hoped. to me at least for my usecase.
Additional Context
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗