Chroniton Bridge

Access ·

Browsers exchange a short-lived ticket for a credential, SSH clients fetch a certificate; both are signed by this machine's key and nothing is kept there. chronbridge rotate-key on the machine revokes everything at once.

Passkey

Browser credentials last 7 days. Save this machine to a passkey and one touch refreshes them, on any browser your password manager syncs to, without a ticket. The passkey's public key is certified by this machine; the certificates live inside the passkey (largeBlob). Nothing is stored here.

SSH access

One command enrolls an SSH client: run it there within 10 minutes. It fetches a certificate for the key you connect with, through the relay, and prints what to do next. Nothing is kept here to revoke; chronbridge rotate-key on the machine invalidates every client.

read-only

GitHub login

A session on needs GitHub credentials. The daemon keeps the token; sessions only ever see a proxy.

Open and enter this code:

The request that needed it continues on its own once you are done. Closing this only hides it; chronbox github status shows the code again.

A session wants to enter another session's sandbox

On , session asks to run a shell inside the sandbox of session .

If you allow this, whatever runs in the requesting session (an AI agent, most likely) gets the other session's files, processes and credentials-by-proxy, until that shell exits. Deny unless you asked for it.

Danger: an AI session wants to run code in this page

The AI session asks for permission to run arbitrary JavaScript inside this browser tab. Its reason:

If you allow this, that AI session can do anything this page can do, until you reload the page or revoke it:

read everything stored in this browser for Chroniton Bridge: your machine credentials and tickets, your ChatGPT tokens, every AI transcript, queued feedback;
type into any session on any connected machine, and create, rename or kill sessions, as you;
send anything it reads to any server on the internet;
change what you see on this page, including what other AI sessions appear to say.

This exists for debugging Chroniton Bridge itself. Deny unless you asked the AI to do this and you understand the risk. Every run will be shown in the transcript with its code.

I understand this gives the AI session full control of this browser tab

Feedback

Reports collect here: an AI session adds one when it runs into a problem or when you ask it to, and you can write one below. Nothing is sent until you approve the whole batch; open a report's context to see exactly what goes with it.

Your email Kept in this browser and sent with your reports.

Chroniton BridgeAdd a machine

Attach to terminal sessions on your machines, from anywhere. Nothing runs on a server: your browser talks to each daemon over an encrypted iroh connection.

Paste a ticket

On the machine: chronbox ticket (or chronbridge ticket) while its daemon runs. A ticket in a link (#t=…) never leaves your browser.

Restores every machine saved in your passkey.

Sign in with ChatGPT

Access ·

GitHub login

A session wants to enter another session's sandbox

Danger: an AI session wants to run code in this page

Feedback