Run any Skill in Manus with one click

session-history

Stars6

Forks0

UpdatedMay 15, 2026 at 15:04

Find, inspect, summarize, or search prior pi sessions/conversations. Use when the user asks to refer to previous sessions, inspect session history for a working directory, search across all conversations, recover prior tool output, or audit what was stored.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

kiahjh

kiahjh/dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

File ClerksOffice and Administrative Support Occupations·SOC 43-4071

SKILL.md

readonly

name	session-history
description	Find, inspect, summarize, or search prior pi sessions/conversations. Use when the user asks to refer to previous sessions, inspect session history for a working directory, search across all conversations, recover prior tool output, or audit what was stored.

Session History

Pi stores local session transcripts as JSONL files. Treat them as sensitive: they can contain user messages, assistant messages, tool calls, tool arguments, tool output, bash output, images as base64, cwd/session metadata, branching, compaction summaries, labels, model changes, token usage, and extension messages/state.

Location

Default root:

session_root="${PI_CODING_AGENT_SESSION_DIR:-${PI_CODING_AGENT_DIR:-$HOME/.pi/agent}/sessions}"

Sessions are usually under:

~/.pi/agent/sessions/--<cwd with / replaced by ->--/*.jsonl

Example for /Users/miciah/.dotfiles:

~/.pi/agent/sessions/--Users-miciah-.dotfiles--/*.jsonl

Quick commands

List recent sessions across all working dirs:

find "$session_root" -type f -name '*.jsonl' -print0 | xargs -0 ls -lt | head -50

List sessions for the current working directory:

encoded_cwd="$(pwd | sed 's#/#-#g')"
find "$session_root/--$encoded_cwd--" -type f -name '*.jsonl' -print 2>/dev/null

Search all sessions for text:

rg -n "SEARCH_TEXT" "$session_root"

Show basic metadata for every session:

find "$session_root" -type f -name '*.jsonl' -print0 |
while IFS= read -r -d '' file; do
  python3 -c 'import json,sys; h=json.loads(open(sys.argv[1]).readline()); print(f"{h.get(\"timestamp\",\"\")}\t{h.get(\"cwd\",\"\")}\t{h.get(\"id\",\"\")}\t{sys.argv[1]}")' "$file"
done | sort

File format reminders

First line: {"type":"session", ...} with id, timestamp, cwd, version, and sometimes parentSession.
Most transcript entries are {"type":"message", "message": ...}.
message.role may be user, assistant, toolResult, bashExecution, custom, branchSummary, or compactionSummary.
Assistant content blocks can include text, thinking, and toolCall blocks. Tool calls include name and full arguments.
Tool result content stores returned text/images plus isError, toolName, and optional details.
Entries form a tree via id / parentId; do not assume simple linear history if branches exist.
Compaction is lossy for model context, but original earlier entries remain in the JSONL file.

When answering from session history, summarize relevant findings and cite session file paths/timestamps. Do not dump large transcripts or secrets unless the user explicitly asks.

More from this repository

same repository

multi-character-code-council

kiahjh/dotfiles

Run a Multi-Character Code Council with four GPT-5.6 Sol reviewer characters and an xhigh skeptical chair. Use only when the user explicitly requests an MCC review, names the Multi-Character Code Council, or directly invokes this skill. Never use for a generic review, second opinion, adversarial review, cross-review, pre-implementation review, or request for multiple perspectives unless the user explicitly asks for MCC.

2026-07-246

context-capture

kiahjh/dotfiles

Capture durable resume context into a project-local agent state file. Use when the user asks to capture the current session, prepare a handoff before starting a new session, preserve resume context, or update saved agent state.

2026-07-216

context-preflight

kiahjh/dotfiles

Read project-local saved agent state and orient before work. Use when the user asks to preflight, resume from a handoff, load saved agent context, compare saved state with the repository, or understand where prior work left off.

2026-07-216

image-generation

kiahjh/dotfiles

Generate new images and edit, restyle, or combine existing images with OpenAI GPT Image 2 through Codex's native subscription-backed image tool. Use when the user asks to create an image, illustration, poster, logo, icon, mockup, diagram, product shot, visual asset, or to modify one or more image files.

2026-07-216

gt-workspaces

kiahjh/dotfiles

Use the local Gertrude `gt` task helper to list, spawn, review, fork, and clean Gertrude task workspaces. Load when working on Gertrude, creating, reviewing, or forking GT tasks, choosing an isolated agent workspace, or explaining how to use `gt`.

2026-07-096

visual-spec

kiahjh/dotfiles

Create compact, dark-mode, browser-viewable HTML artifacts for specs, plans, PRDs, RFCs, roadmaps, implementation plans, architecture proposals, decision docs, and strategy briefs. Use when the user asks to spec something out, make a plan, draft a proposal, compare options, or produce substantial planning content; save a scannable artifact and return its path instead of dumping a long Markdown answer in chat. Prefer simple disposable docs with visual sketches or UI examples when helpful.

2026-07-076

name	session-history
description	Find, inspect, summarize, or search prior pi sessions/conversations. Use when the user asks to refer to previous sessions, inspect session history for a working directory, search across all conversations, recover prior tool output, or audit what was stored.

Session History

Location

Default root:

session_root="${PI_CODING_AGENT_SESSION_DIR:-${PI_CODING_AGENT_DIR:-$HOME/.pi/agent}/sessions}"

Sessions are usually under:

~/.pi/agent/sessions/--<cwd with / replaced by ->--/*.jsonl

Example for /Users/miciah/.dotfiles:

~/.pi/agent/sessions/--Users-miciah-.dotfiles--/*.jsonl

Quick commands

List recent sessions across all working dirs:

find "$session_root" -type f -name '*.jsonl' -print0 | xargs -0 ls -lt | head -50

List sessions for the current working directory:

encoded_cwd="$(pwd | sed 's#/#-#g')"
find "$session_root/--$encoded_cwd--" -type f -name '*.jsonl' -print 2>/dev/null

Search all sessions for text:

rg -n "SEARCH_TEXT" "$session_root"

Show basic metadata for every session:

find "$session_root" -type f -name '*.jsonl' -print0 |
while IFS= read -r -d '' file; do
  python3 -c 'import json,sys; h=json.loads(open(sys.argv[1]).readline()); print(f"{h.get(\"timestamp\",\"\")}\t{h.get(\"cwd\",\"\")}\t{h.get(\"id\",\"\")}\t{sys.argv[1]}")' "$file"
done | sort

File format reminders

First line: {"type":"session", ...} with id, timestamp, cwd, version, and sometimes parentSession.
Most transcript entries are {"type":"message", "message": ...}.
message.role may be user, assistant, toolResult, bashExecution, custom, branchSummary, or compactionSummary.
Assistant content blocks can include text, thinking, and toolCall blocks. Tool calls include name and full arguments.
Tool result content stores returned text/images plus isError, toolName, and optional details.
Entries form a tree via id / parentId; do not assume simple linear history if branches exist.
Compaction is lossy for model context, but original earlier entries remain in the JSONL file.

When answering from session history, summarize relevant findings and cite session file paths/timestamps. Do not dump large transcripts or secrets unless the user explicitly asks.