@gent
DocsOptional dashboard
Sessions

Optional dashboard

The dashboard lists sessions on your paired computers. You can find a session from your phone and email yourself its thread. Dashboard access is optional.

Dashboard login is optional. Your CLI and email workflow keep working without it. Pairing a computer adds a list that you can open in a browser.

Note

Use @gent 0.5.0 or later.

Session commands are available in the published package. Upgrade with uv tool upgrade atgent, then run atgent start so the runner uses the new version. Check it with atgent status --human --wait-ready 30.

Pair a computer

Run this on the computer where @gent runs:

$ atgent login

The command prints a pairing code and a link for the email address in your config. Open the link and request a sign-in link. The dashboard emails a magic link to that address. Connecting your mailbox to @gent does not sign a browser in.

After you sign in, check the computer name, the email and the code. Then choose Approve this computer. A different signed-in email cannot approve it. The code expires after 10 minutes.

  1. 1Start pairing. atgent login prints a code and a link for the email in your config.
  2. 2Check and approve. Sign in with the magic link, then compare the computer and code before you approve.
  3. 3Choose a session. Email me this thread queues an email on that computer.
  4. 4The thread arrives. The computer sends it when it is awake and online.
Note

Opening the email on another device?

Run atgent login --no-browser to print the link and code. If the sign-in link opens in another tab or on your phone, enter the code in the dashboard's pairing field.

Email yourself a session

Choose a session and select Email me this thread. The request waits until the computer syncs, then the computer queues the email. The dashboard marks the request complete when the computer's local outbox accepts it. That is not proof that Gmail delivered it.

The request does not release a session that your terminal holds. Close the local session and run atgent handoff TASK_ID before replies can run. The dashboard has no chat, terminal, stop or continue control.

What the dashboard stores

A paired computer sends a session list every 30 seconds while the runner is active. The list contains session titles, project aliases, agent and model, task IDs, status and timestamps.

The paired computer never sends transcripts, prompts, results, attachments, file paths, native session IDs, passwords or mailbox credentials. Titles can contain private text, so keep sensitive details out of them. Task text and results still travel through Gmail and your agent provider.

Pairing uses outbound HTTPS from your computer. It opens no inbound port.

When the computer is offline

The computer must stay awake and online with the runner active. The dashboard shows the computer as offline after 90 seconds without a heartbeat. Requests wait for the computer and expire after one hour.

Remove a computer

$ atgent logout

Logout revokes this computer and removes its local token. You can also revoke a computer in the dashboard. Your local task history and email stay as they are. If you change the email in your config, run atgent logout and then atgent login.

  • atgent dashboard shows the local pairing state.
  • atgent dashboard sync sends the session list now and runs waiting requests.

The device token is stored in state/dashboard.json beside your config. Never attach that file to a bug report.

Checked against @gent 0.5.0.