Global assistant: Planner pro-actively edits workflows too often
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 5
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 17
Description
When attaching logs in particular, the planner insists on fixing broken workflows even if the user just asks a question, or sends a greeting. The subagents are more likely to diagnose the problem and ask if the user would like a solution.
This is unexpectedly difficult to fix, and none of my dozen prompts adding/moving/tweaking prompts worked. The branch pushy-planner contains a test for the scenario. It might be easier to fix this when we add dedicated skills.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the scenario test on the pushy-planner branch, focusing on requests with attached logs, questions, and greetings. Trace the planner behavior exercised by that test and compare it with the subagents' diagnostic-and-confirm approach. Done means the planner no longer edits broken workflows without the user asking for a solution, and the scenario test passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- ai
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100