Explore: GitHub.com-based Squad experience

[bradygaster]

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

• GitHub App auth (Support GitHub App authentication for Squad-authored commits #256) — prerequisite for app-based approach
• CLI-First (RFC: CLI-First Architecture — Migrate Squad Automation from GitHub Actions to CLI Commands #252) — CLI commands that could be triggered remotely

[bradygaster]

@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?