omc.session.search

Search JSONL session history for matching runtime events.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/jimmi2051/oh-my-copilot --skill omc-session-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc.session.search
Source: https://github.com/jimmi2051/oh-my-copilot/tree/main/plugins/omc-copilot/skills/omc-session-search
Command: npx skills add https://github.com/jimmi2051/oh-my-copilot --skill omc-session-search

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users need to quickly locate relevant entries in the persisted session history to diagnose issues and verify runtime behavior.

Core Features & Use Cases

  • Textual search over the JSONL session history to surface matching events.
  • Returns the matching lines for quick inspection during debugging.
  • Supports project-wide searches via the omc-copilot tooling.

Quick Start

Query the session history with a string to retrieve matching entries.

Frequently Asked Questions about omc.session.search

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

FAQPage Schema
How do I search session history to debug runtime events in omc-copilot projects?

Search session history by querying the JSONL file stored under .omc/state/omc-copilot-history.jsonl. The tool returns matching lines for direct inspection to help diagnose issues and verify runtime behavior.

What is the best way to trace runtime events across omc-copilot session history?

Trace runtime events by applying textual search over the persisted JSONL session history. This surfaces matching entries for quick inspection during debugging, auditing, and traceability tasks.

Do I need access to the local project root to search persisted session history?

Yes, searching persisted session history requires access to the local project root and relies on the omc-copilot tooling to query the JSONL history file stored under .omc/state/omc-copilot-history.jsonl.

Can I use text search to inspect JSONL session history for auditing purposes?

Yes, you can use text search over the JSONL session history for auditing. Query the history file with a string to retrieve matching entries and verify runtime behavior across omc-copilot projects.

What limitations exist when searching JSONL session history with omc-copilot tooling?

The search applies textual matching over the JSONL session history and returns matching lines for direct inspection. It depends on the omc-copilot tooling and access to the local project root to function.