live-session-debugger

Audit live Gormes session state for locks, duplicates, and gateway health.

9|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill live-session-debugger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: live-session-debugger
Source: https://github.com/TrebuchetDynamics/gormes-agent/tree/main/development-skills/live-session-debugger
Command: npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill live-session-debugger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Audit live ~/.gormes session state to surface locks, transcripts, gateway status, and profile data that can block sessions, duplicate turns, or obscure memory activity.

Core Features & Use Cases

  • Inspect sessions.db locks, memory.db transcripts, gateway state, and logs to surface inconsistencies and health issues.
  • Detect duplicate sessions, missing backups, and extractor backlog to guide repair planning.
  • Use case: operators run this tool during incident response to rapidly map operator state and surface actionable diagnostics.

Quick Start

Run the audit against your Gormes home to generate a read-only report of sessions.db, memory.db, gateway.pid, and related state.

Frequently Asked Questions about live-session-debugger

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

FAQPage Schema
How do I debug live Gormes sessions to find locks and duplicate turns?

To debug live Gormes sessions, run a read-only audit against the GORMES_HOME directory to inspect sessions.db, memory.db, and gateway.state. This surfaces session locks, duplicate turns, and gateway health issues without exposing secrets.

What causes duplicate sessions and missing backups in a Gormes runtime?

Duplicate sessions and missing backups in a Gormes runtime are caused by inconsistencies within sessions.db and gateway state. Auditing these local stores surfaces extractor backlogs and state conflicts to guide repair planning.

How do I audit SQLite and BoltDB-like stores during a Gormes incident response?

You audit SQLite and BoltDB-like stores during Gormes incident response by executing lightweight queries against sessions.db and memory.db. The audit generates a read-only diagnostic report of locks, transcripts, and gateway status.

Can I inspect gateway state and memory activity without exposing sensitive secrets?

Yes, you can inspect gateway state and memory activity safely because the Gormes audit applies safe reporting that excludes secrets. It requires only read-only access to map operator state and surface actionable diagnostics.

What is the best way to troubleshoot a blocked Gormes session locally?

The best way to troubleshoot a blocked Gormes session locally is running an audit against your Gormes home. It inspects sessions.db locks, memory.db transcripts, and gateway.pid to rapidly map operator state and identify blocking inconsistencies.