# AI use cases for Session Kit (dob323/session-kit)

Repo: [dob323/session-kit](https://github.com/dob323/session-kit) | Use cases: 4 | Page: https://dedupedai.com/use-cases/dob323-session-kit/

Session Kit is a local terminal picker that lists, names, numbers, and reopens Claude Code and Codex sessions that keep running on the host.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Find the one AI coding session that needs you: https://dedupedai.com/use-cases/dob323-session-kit/see-which-ai-session-needs-you/
- Keep AI coding sessions running through SSH drops: https://dedupedai.com/use-cases/dob323-session-kit/keep-ai-sessions-alive-over-ssh/
- Run each Claude Code session on its own account: https://dedupedai.com/use-cases/dob323-session-kit/run-claude-sessions-on-separate-accounts/
- Reopen an AI conversation after closing its session: https://dedupedai.com/use-cases/dob323-session-kit/reopen-a-closed-ai-conversation/

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

Repo: [dob323/session-kit](https://github.com/dob323/session-kit) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

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

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

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

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

### 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 to paste into your agent

```text
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.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/dob323-session-kit/see-which-ai-session-needs-you/

## How to keep AI coding sessions running through SSH drops with Session Kit

Repo: [dob323/session-kit](https://github.com/dob323/session-kit) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Start Claude Code or Codex on a remote host and reconnect later without losing the session.

**Who it is for:** A developer who runs AI coding agents on a remote Linux host and works from a laptop over SSH that sometimes drops.

**The problem:** When the SSH connection or terminal closes, the agent session in that window is lost or hard to find again.

**The outcome:** Sessions keep running on the host. After reconnecting, you open the picker and type the number of the session you want.

### Steps

1. On the remote host, install Session Kit for your user following the README.
2. Run `sp new claude` or `sp new codex` to start a session on the host.
3. Close your terminal or let the SSH connection drop. The session keeps running on the host.
4. Reconnect over SSH and run `kit`.
5. Type the session number to return to the session.

### Prompt to paste into your agent

```text
On the remote host <host>, install Session Kit from https://github.com/dob323/session-kit using the latest release artifact, run `session-kit services enable`, then start a session with `sp new claude`. Verify with `kit` that the session is listed and still running after the SSH connection is closed and reopened.
```

### Caveat

Session Kit runs on a Linux or macOS host with systemd or launchd services, so a host without those will not work as described.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/dob323-session-kit/keep-ai-sessions-alive-over-ssh/

## How to run each Claude Code session on its own account with Session Kit

Repo: [dob323/session-kit](https://github.com/dob323/session-kit) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Enrol several Claude Code logins and pick the account for each session at launch.

**Who it is for:** A developer with a work and a personal Claude Code subscription who wants each session to use the right one.

**The problem:** A terminal normally inherits one login, so every window shares one subscription and it is easy to use the wrong one.

**The outcome:** Each session authenticates as the account it was started on, and the picker shows which account each session belongs to.

### Steps

1. Install Session Kit following the README.
2. Run `sp account enroll claude work you@example.com` for each account, using your own label and email.
3. Run `sp account list claude` to confirm the enrolled accounts.
4. Run `sp new claude` and choose the account when prompted.
5. Run `kit` and check the account column for each session.

### Prompt to paste into your agent

```text
Using Session Kit from https://github.com/dob323/session-kit, enrol the Claude Code account <label> with `sp account enroll claude <label> <email>`, then run `sp account list claude`. Verify that the list shows <label> and report the output.
```

### Caveat

Account separation is for choosing the right subscription per session, and Session Kit does not isolate sessions from other processes running as your own Unix user.

Risk, credentials: Each enrolled account keeps its own provider configuration directory, so treat those directories and the logins in them as sensitive credentials on this machine.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/dob323-session-kit/run-claude-sessions-on-separate-accounts/

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

Repo: [dob323/session-kit](https://github.com/dob323/session-kit) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

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

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

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

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

### 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 to paste into your agent

```text
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.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/dob323-session-kit/reopen-a-closed-ai-conversation/