show

Display full messages and metadata for a single AI coding session.

1|Updated Feb 24, 2026

Search Tags:#cli #session #inspect #ai-session #session-id #omnisess

Ready to run

npx skills add https://github.com/psacc/omnisess --skill show

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: show
Source: https://github.com/psacc/omnisess/tree/main/skills/omnisess-show
Command: npx skills add https://github.com/psacc/omnisess --skill show

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly surface the complete message history and metadata for a single AI coding session so you don't have to switch tools or hunt through fragmented logs.

Core Features & Use Cases

Full session inspection: Retrieve the entire conversation and metadata for a session to understand context and decisions.
Tool-agnostic session identifiers: Accepts identifiers in the format tool:session-id (for example, claude:5c3f2742 or cursor:a1b2c3d4).
Debugging and review: Ideal for tracing edits, reviewing past advice, or exporting session contents for analysis.
Use Case: A developer reviewing why an automated suggestion was made can open the session to read all messages and timestamps.

Quick Start

Run omnisess show claude:5c3f2742 to display the full session messages and metadata.

Frequently Asked Questions about show

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

FAQPage Schema

How do I inspect a complete AI coding session history by its ID?▼

To inspect a complete AI coding session, you need to retrieve the full message history and metadata using a tool-agnostic session identifier. This surfaces the entire conversation so you don't have to hunt through fragmented logs.

What format is required for session identifiers when inspecting AI session details?▼

Session identifiers must follow the tool:session-id format to inspect AI session details successfully. For example, you would use claude:5c3f2742 or cursor:a1b2c3d4 to retrieve the corresponding session messages and metadata.

Can I review past AI coding sessions from tools like Claude Code, Cursor, Codex, and Gemini?▼

Yes, you can review past AI coding sessions from Claude Code, Cursor, Codex, and Gemini. The inspection process accepts tool-agnostic identifiers for these platforms to retrieve and trace their complete message histories.

Do I need to install any CLI tools to show full details of an AI session?▼

Yes, you need the omnisess CLI installed to show full details of an AI session. Once installed, you can run a command like omnisess show claude:5c3f2742 to display the complete session messages and metadata.

Why would I need to retrieve the complete message history of a past AI coding session?▼

Retrieving the complete message history of an AI coding session is ideal for debugging and reviewing past advice. It helps developers understand the context and decisions behind automated suggestions by tracing edits and reading all messages with timestamps.

What is the best way to trace edits made during an automated AI coding session?▼

The best way to trace edits made during an automated AI coding session is to open the session using its specific identifier. This allows you to review the entire conversation and metadata to understand exactly why edits were made.