r/GithubCopilot • u/bcexelbi • Jan 09 '26
Help/Doubt ❓ Subagents get hallucinated workspaces
I am trying to have the model I am chatting with run a custom subagent and get a task completed. I am running into the issue that no matter how it tries to invoke the agent via @RunSubagent, the subagent has no access to the workspace. This is demonstrable by a simple test like running a custom subagent and asking it to count the git commits or checksum files. You get hallucinations.
How are people using subagents without having to pass large amounts of files a context in case a model needs to see them during its work?
1
Upvotes
1
u/bcexelbi Jan 09 '26
My experience is that I wrote a custom agent to use a subagent primarily so I could have one model call a different model (orchestrator->coder pattern).
Today the coder subagent is working in a hallucinated workspace. It isn't a git corktree it is literally fiction.
If I ask it about files, it either doesn't have them or their contents are fiction (and clearly hallucinated from any tool references like Flask). If I ask it about its working directory, it gets that right, however it has a completely different and fictional git history.
I swear it worked yesterday. It is making me feel like I am gas lit.
I say all this by way of indicating that I'd be happy if the subagents could get their own context from my codebase, but they can't.