alphaswarm-ide
Browser-tier IDE for AlphaSwarm. White-labeled Theia 1.72 with six
compile-time extensions (alphaswarm, alphaswarm-shell,
alphaswarm-mcp-bridge, alphaswarm-research-copilot,
alphaswarm-notebook-quant, alphaswarm-quant), an MCP-driven
research copilot, and a Perspective + Arrow notebook renderer.
The canonical operator entrypoint is alphaswarm-cli ide — see
alphaswarm-ide.md for the full IDE concept doc.
Identity
| Field | Value |
|---|---|
| Service id | alphaswarm-ide |
| Role | ide |
| Package | alphaswarm_ide/ |
| Image (key) | ide |
| Built from | alphaswarm_ide/Dockerfile (node:24-bookworm; extension-build env) |
Wire
| Field | Value |
|---|---|
| Protocol | HTTP/1.1 + WebSocket (Theia front channel) |
| Port | 3000 (browser-tier) |
| Health | GET / |
| Public URL | per-user (operator's own laptop or per-cell ingress) |
Deployment surfaces
| Surface | Where |
|---|---|
| Local | alphaswarm-cli ide start — runs the IDE as a docker container against the local cluster |
| Kustomize | deployments/kubernetes/alphaswarm-ide/ — Deployment + Service + Ingress + NetworkPolicy |
| AQP CR | AQPIDE — for per-user pod lifecycle |
Dependencies
Upstream:
alphaswarm-core/mcp/*— every research copilot LLM call goes throughrouter_complete(rule 2) on the API pod.alphaswarm-cp/auth/*— OIDC-bound IDE sessions.postgres,redis,iceberg/polaris— read paths for the notebook renderer.
Downstream:
- Operator browsers (one IDE pod per active operator session).
Boundaries
- AlphaSwarm code MUST live inside
theia-extensions/alphaswarm*/. - Theia extension code MUST NOT import
alphaswarmsource — cross-process via MCP only. - Copilot LLM calls go through
router_complete(AGENTS rule 2). - MCP registrations carry per-MCP
audclaims (rule 49).
Operations
- Per-user pods: the operator pattern is one Deployment per active session. Idle sessions scale to zero via KEDA after 30 min.
- NetworkPolicy: the IDE pod only reaches
alphaswarm-core,alphaswarm-cp, and the data plane through thealphaswarm-data-mcpsidecar. - Bundle sourcing: the AlphaSwarm extensions are built into the image at compile time; no runtime extension marketplace fetch.
See also
alphaswarm-ide.md— full IDE concept doc.alphaswarm-ide-roadmap.md— phase plan.alphaswarm_ide/AGENTS.md— boundary rules.