A clear boundary between execution and collaboration
The local companion is the execution and evidence authority. Cloud services are optional and should carry shared contract metadata—not your local secrets or captured payload bodies.
What stays local
- Repository source and Git working tree.
- Request credentials and OS-vault secrets.
- Captured request and response payloads.
- Private network access, logs, and the authoritative project timeline.
- MCP execution over local stdio.
Local access
The daemon binds only to 127.0.0.1. The same-origin dashboard uses an HTTP-only, SameSite session cookie; MCP and CLI clients use the protected local daemon descriptor.
Optional cloud collaboration
Team cloud capabilities are intended for shared contract records, consumer locations, environments, CI proof metadata, and governance. Hosted access uses an opt-in outbound pairing bridge rather than opening an inbound port to the developer machine.
Redaction
The observer removes authorization, cookies, API keys, passwords, tokens, and common secret fields before evidence is stored. Redacted evidence is still sensitive development data and should not be committed.