session-debug

Diagnose BotNexus session state issues across logs, traces, and session DB.

2|3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/sytone/botnexus --skill session-debug-sytone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-debug
Source: https://github.com/sytone/botnexus/tree/main/.squad/skills/session-debug
Command: npx skills add https://github.com/sytone/botnexus --skill session-debug-sytone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BotNexus users need to diagnose and resolve session issues across agents, channels, and gateway logs. This Skill provides quick, structured methods for inspecting session state, routing messages, resuming interrupted sessions, and correlating traces across logs.

Core Features & Use Cases

Probe-based correlation and diagnostics across logs, sessions, and traces. Python helper scripts for direct DB access and file-store inspection. Guided investigations for common issues like resuming sessions and verifying visibility.

Quick Start

Run BotNexus Probe to correlate a session across logs and traces, then use the Python helpers for direct DB lookups if needed.

Frequently Asked Questions about session-debug

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

FAQPage Schema
How do I debug session state issues across gateway logs and traces?

Debug session state issues by correlating events across gateway logs and traces using Probe, while optionally leveraging Python helpers for direct SQLite or JSONL DB lookups to diagnose routing and resumption failures.

Can I trace message routing and correlate events across multiple data sources?

Trace message routing by correlating events across logs, traces, and session databases. Probe-based diagnostics identify routing paths, while Python helpers enable direct DB inspection for structured session metadata access.

What is the best way to resume interrupted BotNexus agent sessions?

Resume interrupted BotNexus agent sessions by inspecting session state across logs and the session DB. Guided investigations help verify visibility and safely restore sessions using auditable query flows via SQLite or JSONL stores.

Do I need Python to inspect session databases directly?

Python is optional for inspecting session databases. Probe handles correlation and diagnostics across logs and traces natively, while Python helper scripts provide direct DB access and file-store inspection for deeper structured metadata queries.

Does this session debugging approach work with SQLite and JSONL stores?

Yes, session debugging supports both SQLite and JSONL stores. It provides safe, auditable query flows for inspecting session state and correlating traces, ensuring robust local tooling across these data formats.

Why are my session traces not correlating across gateway logs?

Traces fail to correlate across gateway logs when session state is inconsistent across data sources. Probe-based diagnostics identify event mismatches, and Python helpers can perform direct DB lookups to isolate the routing discrepancy.