claude-sessions plugin

claude-sessions creates persistent Claude Code workspaces: session notes, conversation resume and local git history.

  • 54 ★ on the repository
  • Last commit
Plugin

Broad access

Why this level

  • The installer writes hooks and skills into Claude Code settings and downloads a script from the network.
  • The task queue runs confirmed tasks by itself at turn boundaries.
All reasons and checks

hex/claude-sessions

Install

Works in

Manual install

curl -fsSL https://github.com/hex/claude-sessions/releases/latest/download/install.sh | bash

The command from the Install section. The authors ask you to read `install.sh` first. From a clone, `./install.sh` works.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • The installer writes hooks and skills into Claude Code settings and downloads a script from the network.
  • The task queue runs confirmed tasks by itself at turn boundaries.

This is third-party code. Review the repository files before installing.

What it does

claude-sessions installs the `cs` command: `cs name` creates a session the first time and resumes it afterward. A workspace keeps the objective, per-actor narratives, memory, plans, checkpoints and a timeline in a `.cs/` folder. Edits are saved to shadow git refs with no extra branch commits. The `cs` command handles conversation rotation through `/rotate` and `/clear`, parallel worktrees, a task queue at turn boundaries, local mail between sessions, a secrets store and a status line with limits. The installer registers hooks, skills and mods, and `cs -adopt` attaches an existing project.

Who it is for. People who run long projects in Claude Code on macOS or Linux and want to return to a session with notes and history instead of an empty window.

Good fit when

  • A Claude Code session crashed and recent edits must come back from shadow git refs.
  • A task spans several days and the goal and plan must survive a conversation change.
  • A feature needs its own checkout and its own session record.
  • One session must pass a message to another and wake it.

Not a fit when

  • You need only one short chat with no history.
  • You work on Windows without WSL.
  • Hooks cannot be installed and `~/.claude/settings.json` cannot be changed.

Example request

Create a debug-api session through cs and continue it tomorrow with the recorded objective and notes.

Limitations

macOS or Linux, Bash 3.2 or newer, git, jq, perl and Claude Code are required, plus a UTF-8 locale: in eucJP, eucKR and eucCN locales the scripts hit syntax errors. The installer writes hooks and tips into Claude Code settings. The install command runs a script from the network, so read `install.sh` first. Updates verify a signed manifest through `ssh-keygen -Y verify`.

How to disable. Remove the commands from `~/.local/bin/`, drop the hooks from Claude Code settings and uninstall the mods. Workspaces with `.cs/` folders stay on disk and are deleted separately.

FAQ

How do I start a session?

Run `cs debug-api`. The first call creates a workspace and opens Claude Code, and later calls offer to resume the recorded conversation.

Is a git project needed first?

No. A session is created with no project or repository. `cs -adopt name` attaches an existing folder.

How do I recover edits after a crash?

Autosave writes edits to shadow git refs without adding normal branch commits. They are restored from the session timeline.

How do I work on features in parallel?

`cs base@feature` gives each feature its own checkout and session record.

Can a session be controlled remotely?

`cs name --remote` serves a session for the Claude app or web. Claude Code 2.1.299 or newer is required.

Discussion

No questions or reviews yet.

Plugins

A Claude Code plugin: share a session link and a teammate sees the same prompts, replies and tool results in their own Claude Code

PluginBroad access997Repository stars

Streams Claude Code hidden thinking, tool calls and subagents to a separate terminal with a live session tree

CLIMinimal access158Repository stars
Russian stack

A Claude Code environment installer: CLAUDE.md, rules, skills, agents, hooks and two-layer project memory in one script

WorkflowExtended access196Repository stars

claudefiles deploys a personal Claude Code setup onto a new machine: skills, commands, hooks and settings from a single manifest.

PluginBroad access120Repository stars

An installer giving Claude Code rules for phases, decision logs, debugging and tests in Go, Rust, Python and six more languages.

CLIExtended access116Repository stars

A Claude Code plugin stores conversations and decisions in Markdown, updates CLAUDE.md and helps resume work in a new session.

PluginExtended access525Repository stars

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialRepository starsMain difference
claude-sessions (this card)no54
Claude Session Dashboardno77displays session state; claude-sessions itself creates and resumes workspaces with notes and recovery
session-migrateno176moves sessions between machines; claude-sessions maintains persistent workspaces that record objective and plan

README in short

The manager keeps a full work trail in `.cs/` and adds safeguards: session encryption on macOS, secrets in the keychain and signed releases.

README badge

Report a problem