Ccsessions banner
miskiewiczm miskiewiczm

Ccsessions

Design community

Description

Terminal UI for browsing, previewing, resuming and managing Claude Code sessions

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

ccsessions

A fast terminal UI for browsing, previewing, resuming and managing [Claude Code](https://claude.com/claude-code) terminal sessions.

![ccsessions in a fullscreen terminal — wide layout with a full-height conversation pane](assets/ccsessions_fullscreen.png)

Features

  • **Project & session browser** — every Claude Code project on your machine, newest first, with live-session indicators (●), message counts and token usage (input / output / cache read / cache write)

  • **Conversation preview** — the tail of any session rendered with roles, Markdown (for Claude's replies), tool calls (⚙) and slash commands (⌘), without opening Claude Code

  • **One-key resume** — `r` replaces the TUI with `claude --resume ` in the session's working directory; `c` copies a ready `cd && claude --resume ` command to the clipboard (OSC 52)

  • **Archive & delete** — move sessions out of `claude --resume` (reversibly) or delete them for good, per session or per project, with confirmation dialogs; sessions whose transcript lives on another synced machine are detected and marked (✕)

  • **Responsive layout** — wide terminals get a side-by-side layout with a full-height conversation pane; narrow (half-screen) terminals get a stacked layout with a full-width conversation pane:

    ccsessions in a half-screen terminal — stacked layout with a full-width conversation pane
  • **Export** — write a whole session to Markdown (YAML front matter with session metadata, then the conversation — ready for Quarto/Pandoc) or copy the raw JSONL transcript verbatim; existing files are never overwritten

  • **Live document** — `w` keeps `_session_.md` in the project directory in sync with a running session, so an external renderer (`quarto preview`, VS Code, Marked, Obsidian) can display the conversation **with LaTeX rendered** while you work in the terminal. Only appended bytes are read, so fo