Local-First Access
Operate the laptop you trust from anywhere.
Conductor keeps repositories, terminals, and agent credentials on the paired machine while the dashboard handles launch, review, and session control.
Production auth with paired-device execution
Sign in
Connect to your paired runtime
Use Google or any other provider you enable in Clerk. Email stays available if you keep it enabled. After sign-in, Clerk returns you to the dashboard or active bridge claim flow inside the same local workflow.
What stays local
- Repositories remain on the paired laptop.
- Agent credentials remain on the paired laptop.
- Terminal output streams from the local ttyd runtime.
How it works
- Sign in to the dashboard.
- Pick the paired machine you trust.
- Launch and review work without moving the runtime.
What Conductor does not do
No cloud repo clone. No hosted shell. No credential proxy. Conductor orchestrates the machine you pair and leaves the runtime where it already lives.