Frequently asked questions
Clear answers, inside the current scope.
DotBridge Beta is in active development. These answers describe the supplied public direction only; they are not a release announcement, a product guarantee, or an invitation to download software.
What is DotBridge?
DotBridge is a small, Rust-based MCP bridge. It lets chat agents that can add a remote MCP connector work safely on a user’s own computer and repositories: read, search, write with custody, run approved tests, and land changes through a gate.
Why does DotBridge use intent?
The agent declares what it is trying to do; DotBridge answers with the next lawful step as a ready-made typed request. This helps the agent re-orient cheaply rather than loop.
What is a door?
On-device clients use a local door. Cloud agents use an owner-approved remote door, with owner windows and Touch ID in the route. The door makes locality and custody explicit. Plainly: a door is a controlled way into your computer.
What does “evidence” mean here?
Every effect is journaled, every completion needs a receipt, and nothing is accepted without evidence. If a request cannot proceed, a refusal says what is needed next.
What systems are planned?
Linux, Windows through WSL, and macOS are planned. This is future-facing positioning, not a statement of current availability.
Can I install or download DotBridge now?
No public download is described here. DotBridge Beta is in active development. Beta access is by request.