Integration proposal: Warp 2.0 — missing integration guide (auto-drafted 2026-06-29)

[NativeTeachingAidsB]

Score: 12 — codetalker has no Warp integration guide; Warp went open-source April 28, 2026. Labels to add manually: integration-proposal, auto-generated, urgent.

Auto-generated by the weekly-landscape-scan routine. Draft spec in docs/superpowers/specs/2026-06-29-integrate-warp.md (on branch docs/landscape-report-2026-06-29). Do not promote to approved without human review.

What is it?

Warp — GPU-accelerated Rust terminal, open-sourced April 28, 2026 (AGPL-3.0 core + MIT UI crates). 30,000+ stars. Supports MCP natively via settings.json. Also ships "Oz" cloud agent orchestration for background agents.

Why it matters for codetalker

No docs/integrations/warp.md exists. Gap. Warp is MCP-native, and developers already run Claude Code + Codex in Warp split panes — codetalker would narrate all of them. Integration is the same config pattern as Cursor/Cline.

Scoring

Signal	Score
Active (open-sourced April 28)	+2
>500 stars	+1
>2000 stars	+2
MCP support (native)	+2
Agent Mode hooks (stretch)	+1
Free tier (open source)	+1
Mentioned in 2+ sources	+2
HN/PH at open-source launch	+1
Total	12

Open questions

1. Exact path for Warp's MCP config — needs verification against docs.warp.dev.
2. Do Warp "Oz" cloud agents support local MCP servers or only remote HTTP?
3. Warp plugin marketplace for discovery?

Effort

Small — 1–2 days. Config verification + integration guide authoring.

---

Routine run: 2026-06-29 | Landscape report: docs/landscape-reports/2026-06-29.md