AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Session Recall

skill-jesse-merhi-skills-session-recall · by jesse-merhi

Find prior local Codex or Claude agent sessions with the agent-session-find CLI. Use when context may exist in previous sessions, after compaction or handoff, before asking the user to remember prior work, when searching for old fixes, decisions, commands, errors, file paths, repo context, review outcomes, or "where did we handle this before?" Keep session contents local and use low-token search…

↗ Repository
— No reviews yet
0 installs
23 views
0.0% view→install

Install

$ agentstack add skill-jesse-merhi-skills-session-recall

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jesse-merhi-skills-session-recall)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 26d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Session Recall? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Session Recall

Use agent-session-find as the first recall step when previous agent work may answer the current question. The goal is to recover the right full session with minimal tokens, not to dump transcripts into context.

Keep session contents local. Do not upload session contents or paste whole session logs into external tools.

Workflow

  1. Confirm the command setup in [command-setup.md](references/command-setup.md).
  2. Start with a recent, bounded fuzzy query:

agent-session-find --index-since 14d --max-sources 80 "".

  1. Add repo or cwd context when the project is known:

agent-session-find --cwd "" --since 30d "".

  1. Search one source when the likely harness is known:

agent-session-find --source codex "" or agent-session-find --source claude "".

  1. If the user mentions a handoff, worker, subagent, delegated implementation,

reviewer pass, branch, commit, or PR opened by another agent, retry with --workers.

  1. If nothing matches, widen gradually: increase --index-since, remove

--cwd, try synonyms, then omit --max-sources for a fuller local refresh.

  1. If running several follow-up searches against the same index, add

--no-refresh after the first successful refresh.

  1. Use [query-strategy.md](references/query-strategy.md) for search terms.
  2. Inspect low-token result cards first, then use

[result-handling.md](references/result-handling.md) before opening logs.

Defaults

Use these defaults unless the task suggests otherwise:

agent-session-find --index-since 14d --max-sources 80 ""
agent-session-find --cwd "" --since 30d ""
agent-session-find --limit 5 ""

For stale or long-running projects, prefer --index-since 90d over an unbounded first pass. Run agent-session-find status when you need to see index size before widening.

Context Pointers

  • Use [command-setup.md](references/command-setup.md) for binary, wrapper,

privacy, database, and parallel-refresh rules.

  • Use [query-strategy.md](references/query-strategy.md) for query terms and

widening strategy.

  • Use [result-handling.md](references/result-handling.md) for interpreting

result cards and deciding when to open local JSONL.

Source & license

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

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

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Search