Skip to content

Explore: GitHub.com-based Squad experience #260

New issue
New issue
Closed as not planned
Closed as not planned
Explore: GitHub.com-based Squad experience#260
Labels
go:needs-researchNeeds investigationpriority:p2Next sprintsquadSquad triage inbox — Lead will assign to a memberstatus:backlogBacklog itemtype:featureNew capability

Description

@bradygaster
bradygaster
opened on Mar 7, 2026

Summary

Explore feasibility of running Squad from GitHub.com — either through the agents panel, GitHub Actions, or a GitHub App integration.

Origin: Discussion #173 by @diberry

Current State

Squad is CLI-based and requires local file system access + shell execution. This is fundamentally different from browser-based environments.

Potential Approaches

  1. GitHub App — Squad as a GitHub App that responds to issue comments, PR events
  2. Codespaces integration — Squad in a Codespace (already works, just needs documentation)
  3. GitHub Actions trigger — Squad as an Actions workflow (partially exists via heartbeat)
  4. Agent panel integration — Requires GitHub platform changes, longer-term

Notes

Codespaces is the most immediately viable path — Squad already works there. We should document this better. The GitHub App approach is the most powerful long-term option.

Related

Activity

  1. bradygaster
    added
    type:featureNew capability
    status:backlogBacklog item
    on Mar 7, 2026

  2. bradygaster commented on Mar 7, 2026

    @bradygaster
    bradygaster
    on Mar 7, 2026
    CollaboratorAuthor

    @diberry - could you sort of describe your workflow idea here? Let's say a user has a prompt box on github and they can - somehow - direct the prompt to "use a squad" - would you imagine it fires up something like a codespace and runs a squad in it? or... something else?

  3. bradygaster
    added a commit that references this issue on Mar 7, 2026

    docs(ai-team): Merge decisions from inbox and log discussions-to-issu…

    4a06bea
  4. jongio
    added a commit that references this issue on Mar 9, 2026

    feat: OTel Phase 2-3 — session traces, tool enhancements, metric wiri…

    d59bbee

  5. diberry commented on Mar 9, 2026

    @diberry
    diberry
    on Mar 9, 2026
    Contributor

    @bradygaster I don't know every GitHub feature and it seems more are rolling out so my thinking may not quite be accurate however....

    Squad on GH may need its own app eventually but this is what I'm thinking now.

    I would like to interact with Squad via the repo/GitHub/Browser. At the business management level, I want to box in the process so give the repo functionality and squad $500 month.

    Features I can see at the org and/or repo level:

    • discuss proposals before issues are created - squad should be able to do the research and present several solutions
    • move a discussion to a solution issue
    • move a solution issue to 1 or more PRs
    • move the PR through full team review
    • move PR into temporary environment such as CODESPACE to interact with it - human in loop testing/feedback/steering
    • merge in for next release
    • update CHANGELOG
    • deploy to test/staging environment
    • retrospective feedback to squad - update to discussion for community awareness
    • meta level GH repo config/updates based on retrospective - this might be permissions or changes to contributors list - or branch rules, or action secrets
    • ask questions of the squad - these are my own understanding of the state of the squad or repo and don't need to be tracked in history but should be able to be targeted to branch and default to main. Squad - do you have a feature in the repo to do XYZ.

    squad --init --github --full-enchilada

    For your approaches above in the initial description - yes to all.

  6. WayneAtMicrosoft commented on Mar 9, 2026

    @WayneAtMicrosoft
    WayneAtMicrosoft
    on Mar 9, 2026

    My process:

    Have Squad in a sibling directory (git init) to all my repos (ADO mostly)

    1. Have Squad read from Sharepoint a proposal that has be pitched to my boss. (can do this via MCP)
    2. Have Squad create a Task in ADO Task Board ( can do this via MCP).
    3. Have squad create a new branch in ADO in a repo it doesn't live in (--yolo)
    4. Have Squad fix the Issue (in the Task)
    5. Have Squad commit, push, make PR in ADO
    6. Have Squad move ADO task to status: "In Code Review"
    7. Contact my boss to do another PR review.
  7. bradygaster
    added
    squadSquad triage inbox — Lead will assign to a member
    squad:keaton
    priority:p2Next sprint
    go:needs-researchNeeds investigation
    on Mar 13, 2026
  8. github-actions
    added
    squad:dsky
    on Mar 13, 2026

  9. github-actions commented on Mar 13, 2026

    @github-actions
    github-actionsBot
    on Mar 13, 2026 – with GitHub Actions
    Contributor

    🏗️ Squad Triage — Flight (Lead)

    Issue: #260 — Explore: GitHub.com-based Squad experience
    Assigned to: DSKY (TUI Engineer)
    Reason: Issue relates to frontend/UI 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.

  10. bradygaster
    added
    squad:flight
    and removed
    squad:dsky
    squad:keaton
    on Mar 13, 2026

  11. github-actions commented on Mar 13, 2026

    @github-actions
    github-actionsBot
    on Mar 13, 2026 – with GitHub Actions
    Contributor

    📋 Assigned to Flight (Lead)

    Issue: #260 — Explore: GitHub.com-based Squad experience

    Flight 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:
    Flight, work on issue #260

  12. github
    deleted a comment from github-actions on Mar 18, 2026

  13. diberry commented on Mar 31, 2026

    @diberry
    diberry
    on Mar 31, 2026
    Contributor

    🔄 Ralph status: Explore — GitHub.com-based Squad experience. No PR. Long-term backlog.

  14. bradygaster commented on Apr 12, 2026

    @bradygaster
    bradygaster
    on Apr 12, 2026
    CollaboratorAuthor

    Closing this research item — we've been focused on core CLI maturity and it's paid off. If a GitHub.com-based experience becomes relevant again, we'll open a fresh issue with updated scope.

  15. bradygaster
    closed this as not plannedon Apr 12, 2026
  16. bradygaster
    removed
    squad:flight
    on Sep 11, 2026
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 memberstatus:backlogBacklog itemtype:featureNew capability

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions