git:20260603.b07d25b to git:20260607.0aa1402

---

name: recap

description: >-

---

> **For agents:** When the `kcap-sessions` MCP server is available, prefer its tools (`search_sessions`, `get_session_summary`, `get_session_transcript`) for retrieving past sessions. This CLI-wrapped skill remains a fallback for shell use and when MCP isn't installed.

# Session Recap

Retrieve session history recorded by Kurrent Capacitor. Supports single-session recap, continuation chains, and **repository-wide session summaries** for understanding recent work across multiple sessions.

## Usage

**IMPORTANT:** Always use the `kcap recap` CLI command. Do NOT call the HTTP API directly via `curl`, `WebFetch`, or `HttpClient` — the CLI handles formatting, error handling, and server URL resolution.

```bash

# Current session summary (default — concise AI-generated overview)

kcap recap

# Full transcript (all prompts, responses, file changes)

kcap recap --full

# Full continuation chain (all linked sessions, oldest first)

kcap recap --chain

# Both: full transcript across all chained sessions

kcap recap --chain --full

# Recent session summaries for the current repository

kcap recap --repo

# Explicit session ID (overrides env var)

kcap recap <sessionId>

kcap recap --full <sessionId>

kcap recap --chain <sessionId>

```

`kcap recap` resolves the current session id from the environment when the host agent CLI exposes one. If no session id is available, pass it explicitly: `kcap recap <sessionId>`.

## Repository Recap (`--repo`)

Returns AI-generated summaries from the most recent ended sessions in the current git repository. Each entry includes the session title, date, summary, and a command to get the full transcript.

**Use this when:**

- The user says "what have we been working on recently?"

- The user references prior work ("recently we implemented X")

- You need context about recent changes in this repo

- Starting a new session and want to understand recent activity

**Progressive disclosure:** Start with `--repo` for the overview. If a specific session's summary is relevant, drill into it with `kcap recap --full <sessionId>` to get the complete transcript. This avoids loading full transcripts for all sessions into context.

## Default Output (Summary)

Shows the plan (if any) and an AI-generated summary with:

- **Context** — why the work was done

- **Key decisions** — trade-offs and design choices that matter for future work

- **Unfinished/Risks** — anything deferred or left incomplete

If no summary is available (e.g., active session), a hint is shown to use `--full`.

## Full Output (`--full`)

The complete transcript with these section types:

- **`## User Prompt`** — what the user asked

- **`## Assistant`** — Agent text responses

- **`## Plan`** — plans that were created

- **`## Write <path>`** — files that were created (with syntax-highlighted content)

- **`## Edit <path>`** — files that were edited (with diff content)

When using `--chain`, sessions are separated by `# Session <id>` headers, and agent activity appears under `### Agent (<type>)` sub-headers.

## When to Use Each Flag

- **`--repo`** (`kcap recap --repo`) — recent session summaries across the repo (start here for "what did we do recently?")

- **No flags** (`kcap recap`) — quick context on the current session

- **`--full`** (`kcap recap --full`) — when you need exact prompts, responses, or file contents from a specific session

- **`--chain`** (`kcap recap --chain`) — understanding the full history of a task that spanned multiple sessions

- **`--chain --full`** — complete transcript across all continuations

## Environment

The `KCAP_URL` environment variable overrides the default server URL (`http://localhost:5108`).

## Tips

- **For "what have we been working on?"** — use `--repo` first, then drill into specific sessions.

- Start with the default summary. Only use `--full` when you need specific details.

- When continuing work from a previous session, use `--chain` to get summaries across continuations.

- Summarize key decisions and changes for the user rather than echoing the full recap output verbatim.

- The `kcap` CLI must be available on PATH (typically installed at `~/.local/bin/kcap`).

## Error Handling

- If the session is not found, the command prints "Session not found" and exits with code 1.

- If not in a git repository (for `--repo`), the command prints an error and exits with code 1.

- If the Kurrent Capacitor server is unreachable, the command prints an HTTP error. Ensure the server is running.