Being able to do cross repo work in a single session.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Being able to do cross repo work in a single session. For example: A new task spanning across frontend and backend. I have a custom agent orchestrator in backend that delegates to implementor, test agents, reviewer and so on. The implementor agent only lives in the backend repo, but should be able to make changes in both repos (like it can in the Copilot CLI, by adding the frontend repo directory). Currently it seems not possible to do that?
---
| Field | Value |
| --- | --- |
| App version | 1.1.9 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 2 |
Contributor guide
Research direction
Start at the /chat entry point and trace how a session selects and accesses repository directories. Verify how the backend agent orchestrator currently scopes work, then define completion as one session allowing the implementor agent to make changes in both the frontend and backend repositories.
Written by the indexing model from the issue text.
Assessment
- Domain
- ai-infra-agents, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100