session-history

Search OpenCode session history and plans using grep and jq.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/dheerkt/dotfiles --skill session-history
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-history
Source: https://github.com/dheerkt/dotfiles/tree/main/opencode/skills/session-history
Command: npx skills add https://github.com/dheerkt/dotfiles --skill session-history

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

Search across OpenCode session history to maintain context, recall decisions, and understand project evolution across conversations and plans.

Core Features & Use Cases

  • Per-project session recall and global plan search to locate relevant discussions and decisions.
  • Quick commands to list sessions and plans, and to extract summaries via structured storage metadata.
  • Data structures and storage locations used by OpenCode session history (storage/session, storage/message, storage/part, storage/todo, plans).

Quick Start

Search your OpenCode history for a term to retrieve relevant conversations and decisions.

Frequently Asked Questions about session-history

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search past OpenCode sessions to recall project decisions?

Search past OpenCode sessions by applying a local search script that leverages grep and jq across local storage schemas at ~/.local/share/opencode/storage to retrieve relevant conversation histories and project decisions.

Can I retrieve conversation context globally across all my current projects?

You can retrieve conversation context globally by searching the local storage and plans directories to locate relevant discussions and decisions across all current projects.

How do I extract summaries from OpenCode session histories using structured metadata?

Extract summaries from OpenCode session histories by running quick commands that query structured storage metadata located in the storage/session, storage/message, and storage/part directories.

Do I need jq installed to search OpenCode plans and session data?

Yes, jq is required as a dependency, because the search script relies on it alongside standard UNIX tools to parse structured storage metadata and surface relevant session results.

What's the best way to locate past plans and todos within OpenCode storage?

Locate past plans and todos by searching the ~/.local/share/opencode/plans directory and the storage/todo schema, which preserves project evolution and task context across conversations.

Why does my session history search return no results from local storage?

Session history search returns no results if the target term does not exist within the local storage schemas at ~/.local/share/opencode/storage, or if the required jq dependency is missing from the environment.