Menu

Beta · invitation only

Give agents the next lawful step.

DotBridge Beta is a small, Rust-based MCP bridge for chat agents that need to work safely on your computer and repositories—without losing the thread, the custody, or the evidence.

Request beta access →Read the docs
  • 01Rust-based
  • 02MCP bridge
  • 03CNP wire + state
DotBridge Beta lawful-step loopAn agent declares an intent. DotBridge returns the next lawful step. A door routes the request to the owner’s computer, where a receipt returns evidence.01 / AGENTIntentdeclares the job02 / DOTBRIDGENext steptyped + ready03 / ROUTEDoorlocal / remote04 / CLOSEReceiptevidence returns
Intent → route → evidenceOwner custody stays visible
01Every effect is journaledThe route remains visible after an action.
02Completion needs a receiptNothing closes without evidence.
03Refusals name the next stepAgents can re-orient instead of loop.
04Remote access is owner-approvedThe owner stays in the route.

Designed for MCP connector chat agents

Let chat agents work where the work is.

DotBridge is designed for chat agents that support MCP connectors, including ChatGPT and Claude, to work on your own computer and repositories while you approve what matters.

Repository work

Read, search, write with custody.

Give an agent a bounded path to inspect files, prepare changes, run approved tests, and take a change through the gate.

A qualified fit

Designed for, not certified.

Connector support is the design target. This is not a certification claim or a public compatibility guarantee.

Problem → response

Agent work needs an answer that can move forward.

ORIENTATION

Agents lose the thread and loop.

When an agent cannot tell what changed, what is allowed, or what must happen next, it re-orients by trying again. The loop grows; the task does not close.

intent→next lawful step→action
CUSTODY

A chat window is not a machine route.

An agent may explain a change, but it cannot safely touch your computer or repository just because it has a plan. Effects need a lawful route and a clear gate.

local door↔owner-approved remote door
CLOSURE

A completion without evidence is still an open loop.

DotBridge journals the effect and requires a receipt to close the result. A refusal names what is required next so work can re-orient instead of churn.

journal→receipt→closure

How it works

Each action moves through a small, typed path.

01 / INTENT

State the job

The agent declares what it is trying to do. Intent is a starting point, not permission.

02 / DOOR

Take the lawful route

DotBridge returns a ready-made typed request for the next step—local where local, owner-approved when remote.

03 / RECEIPT

Close with evidence

Effects enter the journal. Completion needs a receipt. A refusal says what is needed next.

Operating choices

Designed to assist, not substitute.

01 / Role

Assistive never substitutive

DotBridge supports an agent’s work while keeping the owner, their machine, and their gate in view.

02 / Standard

Evidence over claims

Every effect is journaled. Completion is not accepted without evidence in a receipt. Plainly: a receipt is proof a task really finished.

03 / Direction

Closure over churn

A next step and a refusal both move work forward; neither asks an agent to guess in a loop.

A plain-language pass

The three words that carry the route.

Door
The explicit route through which work reaches your computer and repositories.
Plainly: a door is a controlled way into your computer.
Receipt
The evidence returned when work closes.
Plainly: a receipt is proof a task really finished.
Lawful step
The typed request DotBridge returns when the agent needs to move forward.
Plainly: a lawful step is the next action the rules allow.

Frequently asked questions

What the Beta does—and does not describe.

What is DotBridge Beta?

DotBridge Beta 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.

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.

Can I install or download it now?

Beta access is by request. No public download is described here.

Read the full FAQ →

Beta · invitation only

Request beta access.

Email the Beta team to request access.

Request beta access →