Close a session and bring it back by name
Can I close it and pick it up later?
End a session when you are done. Bring it back by name, with its history, when you need it again.
What you get: a session you can close without losing it. quox sessions attach <name> brings the same conversation back, in the folder it started in, and the bar at the bottom always shows the way back out.
Everything below is from one real run of the released [email protected] on our dev box, with a throwaway session called orchid-review.
Say it in plain words
Section titled “Say it in plain words”In Quoxon (type quox), ask about a session by its name. Quoxon answers these on your machine and asks before it does anything:
› what is orchid-review doing?⚠ This terminal asks: Run /sessions peek orchid-review?do /sessions peek orchid-reviewwhy orchid-review is a session here: this shows its screen, read only, and changes nothing▶ Run /sessions peek orchid-review? y yes · n no · c chat✔ Run /sessions peek orchid-review? yes (00:24)Ⓠ QUOX │ peek orchid-review │ idle · up 3m · dev-box❯ Draft three short review notes for the orchid greenhouse sensor dashboard. Keep it to a list.✻ Worked for 26s · done Friday 3:34 PM› take me into orchid-review⚠ This terminal asks: Run /sessions attach orchid-review?do /sessions attach orchid-reviewwhy orchid-review is a session here: going in hands this terminal over to it▶ Run /sessions attach orchid-review? y yes · n no · c chat✔ Run /sessions attach orchid-review? yes (00:24)⚠ This terminal asks: Go into orchid-review?do go into orchid-reviewwhy Ctrl-b d or /session exit to come back to Quoxon▶ Go into orchid-review? y go in · n stay✔ Go into orchid-review? yes (00:25)Ⓠ QUOX │ attach orchid-review │ Ctrl-b d or /session exit to come back to QuoxonBack in Quoxon from orchid-review. “What is orchid-review doing?” shows its screen and changes nothing. “Take me into orchid-review” asks twice (run it, then go in) before it hands your terminal over. Pressing Ctrl-b d inside brought us straight back to Quoxon.
Do it yourself
Section titled “Do it yourself”1. See what is closed
Section titled “1. See what is closed”quox sessions lists what is working, waiting and idle, then an Off group: closed conversations you can bring back. Rows you can act on are numbered, so quox sessions attach 4 works too.
quox sessionsOff (24) · quox sessions attach <name> resumes it4 ○ off orchid-review 1d ago+16 older · quox sessions all 2. Bring it back by name
Section titled “2. Bring it back by name”quox sessions attach <name> on a closed session asks first, then resumes the same conversation:
quox sessions attach orchid-revieworchid-review is off. Resume its conversation (last active 1d ago)? [y/N] y❯ Draft three short review notes for the orchid greenhouse sensor dashboard. Keep it to a list.- Alert thresholds need units and context.- Stale sensor data should be obvious.- Trends matter more than snapshots.✻ Worked for 26s · done Friday 3:34 PM──────────────────────────────────────────────────────── orchid-review ─❯[quox-orch0:claude* Ctrl-b d or /session exit · back to Quoxon The history is back: the request and the answer from before it was closed. The bar at the bottom shows the way back out.
3. Step out without stopping it
Section titled “3. Step out without stopping it”Press Ctrl-b then d. The session keeps running, and you are back at your prompt:
Ⓠ QUOX │ attach orchid-review │ Ctrl-b d or /session exit to come back[detached (from session quox-orchid-review)] quox sessions now lists it as idle on this host, with the command to go back in:
quox sessions20 ○ idle orchid-review tmux·claude this host 1m quox sessions attach orchid-review 4. Look without going in
Section titled “4. Look without going in”quox sessions peek <name> shows the end of its screen. It is read only and types nothing:
quox sessions peek orchid-reviewⓆ QUOX │ peek orchid-review │ idle · up 53s · dev-box❯ Draft three short review notes for the orchid greenhouse sensor dashboard. Keep it to a list.✻ Worked for 26s · done Friday 3:34 PM Peek works on a running session. On a closed one it says there is nothing called that running; bring it back first.
5. Close it, keep the conversation
Section titled “5. Close it, keep the conversation”quox sessions kill <name> ends it after a y/N. The conversation stays, and it goes back under Off:
quox sessions kill orchid-reviewStop orchid-review? Its conversation and address are kept. [y/N] yⓆ QUOX │ stop orchid-review │ stopped ✔Conversation kept: quox claude --resume orchid-reviewStart it again: quox sessions attach orchid-reviewquox sessionsOff (24) · quox sessions attach <name> resumes it1 ○ off orchid-review 12s ago What just happened
Section titled “What just happened”A closed session is a saved Claude conversation on this machine. quox sessions attach starts it again inside a tmux session named after it, resuming the same conversation in the folder it started in. kill ends that tmux session and nothing else, so the conversation can come back as often as you like.
Each of these acts left a witnessed record, stamped by the server with the person who did it: the resume (00MWH39YDT04HCRLB6EYY7R5AX), the attach from Quoxon (00MWH3F4ZYH76ALYZKFGPW0BUF) and the stop (00MWH3G816S9L8H64TEQX9NMU7). Find your own with quox aee query --intent quox.session.stop.
Check it yourself
Section titled “Check it yourself”quox sessions shows it under Off. quox sessions all lists every closed conversation, not just the latest.
Limits
Section titled “Limits”- This machine’s Claude sessions only. Server chat cannot see a machine’s sessions, by design: ask Quoxon in your terminal, not the web chat.
- Codex sessions are not covered yet.
- This machine’s sessions are listed only for a login in the organisation this machine reports to. With a login in another organisation,
quox sessionsshows that organisation’s conversations and the Off group, but not the live sessions here. - Proven on one host in one organisation.
Nothing to undo: kill keeps the conversation. Bring it back with quox sessions attach <name>.