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

How to find the one AI coding session that needs you with Session Kit

See every Claude Code and Codex session in one picker and jump to the one waiting on you.

Who it is forA developer with many Claude Code or Codex sessions open who keeps opening windows to find the session that asked a question.

The problemWith several sessions running, it is hard to tell which one is blocked on a prompt, which has finished, and which is still working.

The outcomeOne picker shows every session with its state, and a single number takes you straight into the session that needs you.

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. Install Session Kit on the Linux or macOS machine where your AI sessions run, following the install steps in the README.
  2. Run session-kit doctor and fix any problem it reports.
  3. Run kit to open the picker.
  4. Press a to narrow the list to sessions that need you.
  5. Type the session number to open it.

Prompt for your agent

Install Session Kit from https://github.com/dob323/session-kit using the latest release artifact, then run `session-kit doctor`. Confirm that `kit` opens a picker listing the Claude Code and Codex sessions on <host>, and report the state shown for each session.

Caveat. Codex does not expose a blocking question yet, so a Codex session shows needs you when its turn ends rather than when it asks you something.

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