You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Coordinator should auto-detect repo owner for GitHub MCP calls #437
When the coordinator uses the GitHub MCP server tools (e.g. github-mcp-server-issue_read), it must provide owner and repo parameters. Currently, the coordinator guesses the owner — and gets it wrong.
Repro:
Repo agent-framework-demo is owned by uvirk (fork/transfer)
Coordinator assumed bradygaster as owner (original creator or team.md context)
MCP call: GET https://api.github.com/repos/bradygaster/agent-framework-demo/issues/33 → 404 Not Found
Fallback to gh issue view 33 worked fine (uses local git remote)
MCP server 'github-mcp-server': McpError: MCP error 0: failed to get issue: GET https://api.github.com/repos/bradygaster/agent-framework-demo/issues/33: 404 Not Found []
Expected Behavior
The coordinator should resolve the correct owner/repo before making any GitHub MCP calls. Options:
Run gh repo view --json owner,name at session start and cache the result
Parse the git remote URL (git remote get-url origin)
Store the canonical owner/repo in team.md under Issue Source or Project Context
Current Workaround
The coordinator falls back to gh CLI (which reads from git remotes), so work isn't blocked — but it adds latency and a visible error in the session.
Suggested Fix
In the coordinator's session-start sequence (Team Mode), after resolving the team root, also resolve and cache the GitHub owner/repo:
gh repo view --json owner,name
Pass this as REPO_OWNER and REPO_NAME into spawn prompts and use it for all MCP tool calls. Add to team.md under Project Context for persistence.
Issue:#437 — Coordinator should auto-detect repo owner for GitHub MCP calls Assigned to: FIDO (Quality Owner) Reason: Issue relates to testing/quality work
@copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.
Issue:#437 — Coordinator should auto-detect repo owner for GitHub MCP calls
Procedures will pick this up in the next Copilot session.
For Copilot coding agent: If enabled, this issue will be worked automatically.
Otherwise, start a Copilot session and say: Procedures, work on issue #437
Fixed in dev. The coordinator now auto-detects repo owner/name from git remote at session start and passes REPO_OWNER/REPO_NAME to all spawn prompts. Falls back to gh repo view if parsing fails.
Activity
Fix github#420/github#425: Add SDK connection feedback (github#437)
docs(ai-team): Summarize history files to Core Context (under 12KB th…
github-actions commentedon Mar 18, 2026
🏗️ Squad Triage — Flight (Lead)
Issue: #437 — Coordinator should auto-detect repo owner for GitHub MCP calls
Assigned to: FIDO (Quality Owner)
Reason: Issue relates to testing/quality work
@copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.
Team roster:
squad:flightsquad:proceduressquad:eecomsquad:fidosquad:paosquad:capcomsquad:controlsquad:surgeonsquad:boostersquad:gncsquad:networksquad:retrosquad:incosquad:guidosquad:telemetrysquad:voxsquad:dskysquad:simssquad:handbooksquad:ralphsquad:copilotgithub-actions commentedon Mar 18, 2026
📋 Assigned to Procedures (Prompt Engineer)
Issue: #437 — Coordinator should auto-detect repo owner for GitHub MCP calls
Procedures will pick this up in the next Copilot session.
fix: auto-detect repo owner/name at session start (#437)
bradygaster commentedon Mar 20, 2026
Fixed in dev. The coordinator now auto-detects repo owner/name from git remote at session start and passes REPO_OWNER/REPO_NAME to all spawn prompts. Falls back to gh repo view if parsing fails.