Find sessions by email
Email one word to receive a list of your sessions. Reply with a task ID, and that session's own thread arrives. You do not need a dashboard login.
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.
Ask for the directory
Send a new email to your +agents address. Use any subject. Write only this in the body:
sessions
list works too. @gent replies with each session's task ID, agent, project alias, status and title.
sessions
Your @gent sessions 7c41e2d0 | claude | website | local | Finish the settings page 3f9c2a7e | codex | main | completed | improve the signup form Reply open TASK_ID to receive that session's email thread. Reply sessions to refresh.
open 7c41e2d0
Session 7c41e2d0 queued for email delivery in its own thread.
- 1Ask for the directory. Send a new email whose body is sessions or list.
- 2Read the list. Each line has the task ID, agent, project, status and title.
- 3Pick a session. Reply open with one task ID.
- 4Get its thread. The session's own thread arrives. Reply there to continue.
Open a session
Reply to the directory email with one task ID:
open 7c41e2d0
@gent sends a message in that session's own thread. Reply there to continue the session. Reply sessions to get a fresh list.
The directory does not run tasks.
The directory thread never sends text to an agent. Every other reply receives a short note that lists the two commands. The system rejects a reply that matches no known thread, and the reply does not start a new task.
Which sessions appear
- Sessions you connected with Connect a session or
atgent attach. - Sessions that the optional automatic registration hook lists.
A connected session can still be held by your terminal. Replies in its thread wait until you close it and run atgent handoff TASK_ID.
From the terminal
The same sessions appear in atgent list. To send a session's thread to yourself from the terminal, run:
The email is queued on your computer and sent while the runner is active. @gent does not send a duplicate while one is pending or uncertain. A queued email is not proof of delivery; check atgent status --human.