DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to reopen an AI conversation after closing its session with Session Kit

Close a session from the picker and later restore the exact conversation it held.

Who it is forA developer who closes finished or paused AI sessions to tidy up and later needs to pick up one of those conversations.

The problemClosing a session loses track of the conversation, so resuming the work means finding the right thread again by hand.

The outcomeClosing a session records the exact conversation, so you can read its history or restore it from the picker.

What you need first

  • Linux with systemd, or macOS 14 or newer
  • shpool 0.11.0, the stock build
  • Claude Code, Codex, or both
  • One trusted Unix account with per-user service access
  • Python 3.10+ on Linux or Python 3.11+ on macOS, plus Bash 4+

Steps

  1. Run kit to open the picker.
  2. Press k and enter the number of the session to close.
  3. Run kit again later and press h to read the settled history.
  4. Open the restored conversation from the picker by its number.

Prompt for your agent

Using Session Kit from https://github.com/dob323/session-kit, close the session numbered <n> from the picker, then reopen the conversation after running `kit`. Verify that the restored conversation matches the closed one and report which session number it appears under.

Caveat. The README describes closed-session restore in the picker navigation documentation, so confirm the exact restore keys in that guide before relying on them.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page