gemini-cli-extensions / gemini-cli-extensions/conductor
Memory Eraser Button - For when things get wonky
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.7k
- Forks
- 295
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
I've been putting conductor through its paces, but recently I've noticed the bot gets very chatty about what its reasoning, becomes inconsistent when asking questions (answering for itself and then speeding on), or just stopping...
e.g stopping:
✦ Gemini: I will run the tests now.
<log time, not status update or spinner>
> Did you run the tests?
✦ I apologize. I made a mistake by calling the test run and the implementation in the same turn. According to the TDD
workflow, I must first run the tests and confirm they fail (the "Red" phase) before proceeding to the implementation.
I will now run the unit tests for the new models to confirm their current status.
<long time, no spinner, doing nothing>
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
The issue does not identify a file, test, or entry point. First determine where the agent's conversation or state is managed, then define the reset behavior and tests needed to verify that the bot recovers from inconsistent or stalled interactions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100