DamianEdwards / DamianEdwards/copilotd
Define behavior when multiple rules match an issue
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 60
- Forks
- 9
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
If multiple dispatch rules match an issue then it's possible to get conflicting configuration for the session, e.g. which model to use, what tools to allow, etc. We should properly define the behavior when multiple rules match and figure out what the experience should be, e.g. rule precedence, tie-breaker process, dispatch failure, etc.
Contributor guide
No contributing guide indexed for this repository
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 by locating the dispatch-rule matching flow and the session configuration decisions for the model and allowed tools. Done means the behavior for multiple matching rules is explicitly decided, including precedence, tie-breaking, or dispatch failure and the resulting user experience.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100