A second pair of eyes, only when you want them.
Sometimes the fastest way through a problem is to bring in a sighted teammate. Accessible Claude lets you invite one into your live session — and decide, precisely, what they can do. You stay in control the whole time.
Grant exactly what you mean to. Take it back in a blink.
Watching, suggesting, and approving are separate powers. You hand over each one deliberately — never all at once, never by accident.
Watch
The peer sees your live session — the conversation, the tools running, the results — and nothing else. Read-only.
Suggest
The peer can propose prompts. You decide what runs; a suggestion is never sent to the agent on its own.
Approve
The peer can approve or deny the agent’s tool actions on your behalf — useful when a sighted helper is driving.
Host-sovereign, end to end.
The peer is an assistant, never an owner. Everything below is enforced, not just promised.
- You start the pairing. It’s one-time, expiring, and encrypted end-to-end, so the relay that connects you never sees your session.
- View, send, and approve are three separate permissions. You grant each one on purpose, and there’s no silent escalation from one to another.
- You’re always told — on screen and aloud — who is connected and every prompt or approval the peer makes.
- You can revoke any permission, or disconnect the peer entirely, in an instant.
- Every peer prompt and tool decision is audited.
- If the link drops or anything is ambiguous, the session fails safe: the risky action is denied and sole control returns to you.
Whoever’s helping whom.
Both your pairing controls and the peer’s own client work fully by keyboard and screen reader — so a partially-sighted host and a sighted helper, or two developers with sight loss, can pair either way round.
A sighted helper
A colleague joins to lend a second pair of eyes — reading a diff aloud, spotting a typo in a path, or approving a step while you keep typing.
Remote pair-assist
Two developers work a problem together from different machines, across any network — no port-forwarding or setup on your side.
Remote support
A helper drives your agent under your supervision, with you informed of every action and able to take back control at any moment.
Pairing, answered
Does the peer take over my machine?
No. The agent always runs on your machine and you remain in control. The peer is an assistant, never an owner — they can only do the specific things you have granted (view, send, or approve), and you can take any of it back instantly.
Can the relay read my code?
No. Pairing is end-to-end encrypted, so the relay that connects you and the peer cannot read the session content — only you and the person you admit can.
Is the peer’s side accessible too?
Yes. Both your pairing controls and the peer’s own client are fully operable by keyboard and screen reader, so a partially-sighted host and a sighted helper — or two developers with sight loss — can pair either way round.
Bring someone in — on your terms.
Download Accessible Claude for Windows, or join the waitlist to hear when new pairing features land.