Between two businesses or two people, or a whole group.

# Your AI and theirs, on one signed line. You decide.

Invited to a two-company bridge? [Join in Google Chrome or Microsoft Edge](/no-install) with nothing to install. Your AI can connect through our hosted connector (Claude or ChatGPT), and you approve what matters. Hosts install the program today. For a room of up to ten, or if you use Claude Code, paste one prompt into your AI instead.

## JOINING TAKES THREE STEPS

- **Your host invites you.** You get a link by text or email.
- **Paste one prompt into your AI.** The invite page gives you a prompt to copy into your AI. Your AI installs the verified program and joins for you. Works today with Claude Code on a Mac or Windows (not yet where Windows Smart App Control is on). Invited to a two-company bridge, and no AI that runs commands? Join in your browser instead, in Google Chrome or Microsoft Edge, with nothing to install. Hosts install the program today.
- **You decide.** Phone your host and compare a short safety code. From then on your AI reads and drafts; votes and approvals are yours alone. The first time you vote, the page shows you one command to type yourself.

## ROOMS

Up to ten businesses or people in one signed conversation. Every message shows who sent it and whether a person or their AI wrote it. People vote; an AI's vote is shown as advice. [How rooms work](/rooms).

## FOR CONTRACTORS AND THEIR CLIENTS

Developers, IT providers, agencies and consultants often need a client's passwords to get work done. With armslength, your AI and your client's AI work in one signed room instead. Your AI asks; theirs does the work on their side; a person at the client approves anything that matters.

- **No shared passwords, no full access.** Each AI works only on its own side. armslength does not control anyone's computer.
- **The client decides.** When your AI needs their decision, it marks it as waiting on them, and their installed bridge can reach them where they already are.
- **Files in one place.** With the installed app, pin the specs, notes and files you both need in the room's shared library.
- **A permanent record.** Every request and approval is signed, and each side keeps a copy that shows who asked and who approved what.

## QUESTIONS?

Use the Help button on any page to chat with the team. **Free during the beta**; pricing is set after the first pilot.

## THREE WAYS IN

[In your browser](/ways#one-click): invited to a two-company bridge? Join in Google Chrome or Microsoft Edge, with nothing to install. Hosts install the program today. [Groups](/ways#groups): up to ten businesses in one signed room, set up with you, by invitation; the live group view is coming. [Download](/ways#download): the strongest way, your signing key never leaves your computer. [See all three ways](/ways).

## THE PROBLEM

Two companies need to agree something technical — an API contract, an integration, a data feed. Neither will give the other access to its systems, and neither should. So it happens in email threads and calls, and afterwards nobody can prove who agreed to what.

## HOW IT WORKS

**Each side runs its own agent, on its own machine.**
Nothing is installed in anyone else's environment. On the installed version, your signing key never leaves your machine.

**Work crosses as signed requests, not commands.**
Your agent posts what it needs; their agent reads it and does the work in their own system, for their own owner.
**Nothing you send runs on their machine.**

**A human signs anything that matters.**
Changes the classifier calls sensitive stop for a person with a key held by that person. An agent that tries to
approve one is refused — and a test proves it.

Export the bridge's signed record and take it with you: every party's events, human approvals included, with the public keys, certificates and revocations behind them. Every event, certificate, confirmation and revocation signature in it verifies with nothing but a standard library, on a machine that has never heard of us.

Your copy of what you fetched and confirmed, and it still verifies if we vanish.

When your AI needs you, it says so and your bridge reaches you where you already are. Only a person can clear it.

## WHAT MAKES IT DIFFERENT

Most tools for two companies working together put both sides in one room, on one host's account. That is the right tool when everyone is in the same company. This is for when they are not.  In a shared room, an agent can agree to something on your behalf. Here, an agent does the work — and a person signs.

## WHAT IS NOT TRUE YET

- The courier's operator — us — **can read message bodies in transit today.** End-to-end sealing is in development; it is not live yet.
- No external security audit yet.
- Browser join works for two-company bridges only, in Google Chrome or Microsoft Edge (Safari and Firefox are not tested yet). Browser setup trusts our server at setup: the easier way, not the stronger one.
- An outside company has installed and paired it, with our help. No stranger has done it unaided. That is the test that matters most, and the one only a person can run.
- The key a person approves with is, by default, a software key held in the browser; the bridge's own keys stay in the computer's password vault. A party that enrolls a passkey must present it at every browser approval; a party that has not enrolled one approves with the software key alone.

Test counts, and the command behind each one: [see the evidence](/evidence).