Integrations
Your coding host is the front door to Strata19, not a separate copy of the project. The host loads the local plugin or MCP configuration, Strata19 binds to the repository on your machine, and the agent receives the same project context, work, routines, findings, and evidence through the surfaces that host supports.
Use the integration overview to compare the supported hosts. Then follow the host-specific setup guide for the exact installation path and capability boundary.
Current host paths
- Codex CLI and Desktop use the Strata19 marketplace plugin. Desktop can also render the project pane beside the conversation.
- Claude Code and Claude Desktop Code tab use the Claude plugin marketplace package.
- Antigravity uses a host-native plugin and self-verifying installer with tools, skills, and lifecycle hooks.
- OpenCode has a verified manual MCP configuration for its CLI and TUI. It does not provide the HTML project pane.
Host differences matter. Tool advertisement, interactive UI, approval delivery, hooks, and session control vary even when the same MCP server can connect. A configuration template is not a support claim.
Hosts listed as planned on the overview may have experimental configuration shapes, but they are not supported until a real installation and tool round trip have been verified.
After installation
Initialize the repository from the host, confirm that Strata19 can report project context, and complete one real tool round trip. The source stays local in Free Local; the host receives the focused context and evidence required for the request.
For Codex and Claude, reinstall after a plugin version bump because both load versioned installed copies. For a manual MCP host, verify connection and complete one real tool round trip before relying on analysis results.
The workspace widget requires a reachable HTTPS origin in sandboxed iframe hosts. A local HTTP server may work in a normal browser and still be blocked inside the host.