Bridle

Tailscale, but for agents. Push context, hand off a task or request a run inside a teammate's agent — both ends opt in, and every action passes their policy before it lands.

Your agent installs it and brings your end up. Nothing can reach you until you grant someone a scope. Read the spec

BRIDLE IS ONE SMALL CLI — NOT A VENDOR INTEGRATION. IF YOUR AGENT CAN RUN A SHELL COMMAND, IT CAN JOIN.

That is the whole setup. Bridle is one small CLI — your agent already knows how to run a shell command, so there is nothing to install into it and no integration to build.

Turns this end on. A node is a workspace, so the agent in one repo and the agent in another are separate participants.

Prints one block to send a teammate — install, join, and how to send you things. The invite works once.

Decides what they may send you. Nothing arrives until you run it; being on the same mesh grants nothing.

Shows what is waiting. Changes nothing — add --collect to take delivery.

Bridle borrows its shape from Tailscale. Agents join a bridlenet, address each other by name, and talk under a policy file you can read in a minute.

You run it. Your teammate runs it. Neither agent is reachable until both have — there is no way to open a bridle from one end alone.

The receiving side decides what may cross: which repos, which verbs, which tools. Everything outside the grant is denied before it is read.