# Ccthread

> Read, search, and summarize Claude Code conversation history. Use when the user asks to find things discussed in past sessions, review old threads, summarize recent work for teammates, extract learnings into a skill or CLAUDE.md, or answer "what was that value/port/command we used?" — ccthread reads ~/.claude/projects/ and emits clean markdown. Triggers on "past conversation", "old thread", "last…

- **Type:** Skill
- **Install:** `agentstack add skill-jakemarsh-ccthread-ccthread`
- **Verified:** Pending review
- **Seller:** [jakemarsh](https://agentstack.voostack.com/s/jakemarsh)
- **Installs:** 0
- **Category:** [Content & Media](https://agentstack.voostack.com/c/content-and-media)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [jakemarsh](https://github.com/jakemarsh)
- **Source:** https://github.com/jakemarsh/ccthread/tree/main/plugin/skills/ccthread

## Install

```sh
agentstack add skill-jakemarsh-ccthread-ccthread
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# ccthread — past-conversation archaeology

You have a CLI tool `ccthread` available. It reads Claude Code conversation logs from `~/.claude/projects/` and returns clean markdown. Use it whenever the user asks about past work.

## Common patterns

**Look up something from THIS conversation**
```
ccthread show current                                # read the current session
ccthread search "" --session current --window 3
ccthread show current --before-last-compact         # "before we compacted, what did you say?"
```
`current` resolves to whichever session invoked you — via the `CCTHREAD_SESSION_ID` env var, the parent `claude` process's argv, or the plugin's SessionStart hook if argv doesn't carry it. Use it whenever the user says "in our conversation", "before we compacted", "earlier in this session", "what did you just say".

**Find a conversation by topic**
```
ccthread find "" --limit 10
```

**Read a conversation**
```
ccthread show  --page 1 --per-page 50
```
Paginate with `--page 2` etc. Run `ccthread info ` first to see how long it is.

**Keyword search with context**
```
ccthread search "" --window 2 --limit 5
```
Good for "what did we decide about X?" — returns ±2 messages around each hit.

**Summarize recent work on a project**
```
ccthread list --project  --since 2026-04-01
ccthread show   # for each session you want to dig into
```

**Stats / overview**
```
ccthread stats --project  --since 
```

**Tool usage for a session**
```
ccthread tools 
```

## Tips

- Session ids can be short (8-char prefix) or full UUIDs. `last` / `latest` resolves to the most recent session.
- `--no-thinking` hides thinking blocks when they're noise.
- `--tool-details none` hides tool outputs entirely (cleanest for summaries); `full` shows them untruncated.
- `--include-sidechains` inlines subagent threads.
- `--json` emits structured output when you need to re-process it.
- Default page size is 50 messages.

## When to reach for this skill

- "what was that port/env/value we settled on in the X session?" → `ccthread search`
- "summarize last week on project Y for the team" → `ccthread list --since ...` then `ccthread show ` on each
- "make a skill from that process we worked out" → `ccthread show ` then distill into SKILL.md
- "update CLAUDE.md with lessons from recent work" → `ccthread list --project ... --since ...` → read → write
- "find where we hit that bug and what we tried" → `ccthread find ""`

## Running ccthread outside this skill

This skill is all you need when you're in Claude Code — the dispatcher keeps a cached binary under `~/.claude/plugins/data/ccthread/`. If you want `ccthread` on your shell PATH too, the project's install scripts drop it there:

```sh
curl -fsSL https://raw.githubusercontent.com/jakemarsh/ccthread/main/install.sh | sh          # macOS / Linux
irm https://raw.githubusercontent.com/jakemarsh/ccthread/main/install.ps1 | iex              # Windows PowerShell
```

Repo: https://github.com/jakemarsh/ccthread

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [jakemarsh](https://github.com/jakemarsh)
- **Source:** [jakemarsh/ccthread](https://github.com/jakemarsh/ccthread)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** yes
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: flagged — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-jakemarsh-ccthread-ccthread
- Seller: https://agentstack.voostack.com/s/jakemarsh
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.