the integrations

Warp · Oz CLI

null

{"id":"warp","name":"Warp · Oz CLI","class":"C","status":"wired","install":"already covered by interop: Warp reads ~/.claude.json, the project .mcp.json and ~/.codex/config.toml — nika wire claude or codex opens this door today","wire":null,"components":{"mcp":"mcp-config","scaffold":"init"},"gaps":[],"class_gap":"the door is INTEROP by their design (docs.warp.dev capabilities/mcp) · native ~/.warp/.mcp.json exists (a wire target lands only on real demand) · AGENTS.md read natively (WARP.md compat) · project-scoped servers never auto-spawn · house doctrine: operator surface, interop yes, no fork no dependency"}

Wired: the connection is written and lands, and no end-to-end run is recorded yet. Class C: it speaks MCP and nothing else, so the oracle is the whole surface.

wiredthe stateat v0.107.0
Cthe classhow much lands
2pieces landnamed below
0gapsnothing missing

get set up

already covered by interop: Warp reads ~/.claude.json, the project .mcp.json and ~/.codex/config.toml — nika wire claude or codex opens this door today

what lands, and how

mcpmcp-config
scaffoldinit

what does not

the door is INTEROP by their design (docs.warp.dev capabilities/mcp) · native ~/.warp/.mcp.json exists (a wire target lands only on real demand) · AGENTS.md read natively (WARP.md compat) · project-scoped servers never auto-spawn · house doctrine: operator surface, interop yes, no fork no dependency

cross-references

the rooms it touches

where this comes from

v0.107.0
warp