opencode-introspect

Read and search OpenCode session logs in the SQLite database.

27|10|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/intersystems-community/iris-dev --skill opencode-introspect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode-introspect
Source: https://github.com/intersystems-community/iris-dev/tree/main/light-skills/skills/opencode-introspect
Command: npx skills add https://github.com/intersystems-community/iris-dev --skill opencode-introspect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read and search opencode session logs from the SQLite DB at ~/.local/share/opencode/opencode.db. Use when you need to review what a session did, assess whether AI work was safe/correct, diagnose a "session wipe", find a specific tool call or output from a past session, or recover the DB after a migration reset.

Core Features & Use Cases

  • Inspect session activity by reading the OpenCode SQLite DB and its stored JSON payloads to verify actions and tool usage.
  • Trace specific tool calls, user and assistant text, and outputs within a session to diagnose safety, correctness, or debugging scenarios.
  • Diagnose and recover from migration-induced issues by correlating DB records with ground-truth storage files and understanding session lineage.

Quick Start

Query and inspect the OpenCode SQLite logs to review a session's actions, trace tool calls, and diagnose a session wipe or recovery steps.

Frequently Asked Questions about opencode-introspect

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

FAQPage Schema
How do I read OpenCode session logs stored in SQLite to review past activity?

You can review OpenCode session activity by querying the SQLite database at ~/.local/share/opencode/opencode.db to parse stored JSON payloads and extract human-readable actions, tool calls, and outputs without modifying the underlying storage.

What is the best way to trace specific tool calls and outputs from a past OpenCode session?

The best way to trace tool calls is querying the OpenCode SQLite DB to parse session, message, and part data structures, allowing you to locate specific sessions and verify tool usage for safety and correctness assessments.

Can I diagnose a session wipe and recover database state after an OpenCode migration reset?

Yes, you can diagnose session wipes by correlating database records with ground-truth storage files, understanding session lineage, and tracing recovery steps to restore state after migration-induced resets across projects.

Does auditing OpenCode sessions via SQLite logs require modifying the underlying database storage?

No, auditing OpenCode sessions through SQLite logs strictly parses the stored JSON payloads to surface human-readable activity, ensuring the underlying database storage remains unmodified during review and debugging.

How do I locate a specific OpenCode session across multiple projects using stored logs?

Locate specific sessions by querying the SQLite database to filter and parse the session, message, and part data structures, effectively correlating database records across different projects to trace lineage.