Skip to content

Coordinator should auto-detect repo owner for GitHub MCP calls #437

Closed

Description

@uvirk

Problem

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:

  1. Run gh repo view --json owner,name at session start and cache the result
  2. Parse the git remote URL (git remote get-url origin)
  3. 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.

Activity

  1. github-actions commented on Mar 18, 2026

    @github-actions
    Contributor

    🏗️ 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:

    • Flight (Lead) → label: squad:flight
    • Procedures (Prompt Engineer) → label: squad:procedures
    • EECOM (Core Dev) → label: squad:eecom
    • FIDO (Quality Owner) → label: squad:fido
    • PAO (DevRel) → label: squad:pao
    • CAPCOM (SDK Expert) → label: squad:capcom
    • CONTROL (TypeScript Engineer) → label: squad:control
    • Surgeon (Release Manager) → label: squad:surgeon
    • Booster (CI/CD Engineer) → label: squad:booster
    • GNC (Node.js Runtime) → label: squad:gnc
    • Network (Distribution) → label: squad:network
    • RETRO (Security) → label: squad:retro
    • INCO (CLI UX & Visual Design) → label: squad:inco
    • GUIDO (VS Code Extension) → label: squad:guido
    • Telemetry (Aspire & Observability) → label: squad:telemetry
    • VOX (REPL & Interactive Shell) → label: squad:vox
    • DSKY (TUI Engineer) → label: squad:dsky
    • Sims (E2E Test Engineer) → label: squad:sims
    • Handbook (SDK Usability) → label: squad:handbook
    • Ralph (Work Monitor) → label: squad:ralph
    • @copilot (Coding Agent) → label: squad:copilot

    To reassign, remove the current squad:* label and add the correct one.

  2. github-actions commented on Mar 18, 2026

    @github-actions
    Contributor

    📋 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.

    For Copilot coding agent: If enabled, this issue will be worked automatically.
    Otherwise, start a Copilot session and say:
    Procedures, work on issue #437

  3. bradygaster commented on Mar 20, 2026

    @bradygaster
    Collaborator

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    go:needs-researchNeeds investigationpriority:p2Next sprintsquadSquad triage inbox — Lead will assign to a membertype:bugSomething broken

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions