Verified:GitHub

Session Log Management

Manage agent session logging with structured turn lifecycle events.

Updated Apr 11, 2026

Search Tags:#session logging #state machine #JSON envelope #agent audit trail #turn lifecycle #REPL workflow #history query

Ready to run

npx skills add https://github.com/sharpninja/mcpserver-copilot-plugin --skill session-log-management

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Session Log Management
Source: https://github.com/sharpninja/mcpserver-copilot-plugin/tree/main/skills/session
Command: npx skills add https://github.com/sharpninja/mcpserver-copilot-plugin --skill session-log-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the need to reliably capture, manage, and review an agent’s session activity as a structured audit trail, especially when users want direct control over session and turn lifecycles.

Core Features & Use Cases

Session lifecycle management: Bootstrap the logging subsystem, open sessions, and manage turn progression (begin, update, complete, or fail).
Turn-level audit trail: Record interpretation, summaries, dialog items (reasoning/decisions/observations/tool events), and actions (file edits/creates/design decisions).
History queries for continuity: Search prior sessions by agent (or across all agents) with pagination to resume context after restarts.

Quick Start

Use Session Log Management when you want to start a new session or log/query turn history by invoking the workflow.sessionlog.* REPL namespace with one single-line JSON request envelope per message.

Frequently Asked Questions about Session Log Management

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

FAQPage Schema

How do I record an agent audit trail for turn lifecycle events?▼

To record an agent audit trail, you manage the turn lifecycle by invoking the workflow.sessionlog.* namespace to log begin, update, complete, or fail events. This captures reasoning, decisions, and actions into a structured JSON envelope.

How do I query prior session history for agent context continuity?▼

You query prior session history by searching past logs by agent or across all agents with pagination. This allows you to resume context after restarts by retrieving previously recorded dialog and action items.

What is the JSON envelope format required for session logging?▼

The JSON envelope format requires one single-line JSON request envelope per message. It mandates strict session and turn state handling, adhering to documented sessionId and requestId formats within the workflow.sessionlog.* command namespace.

Can I manually control when to bootstrap a session and begin a turn?▼

Yes, you can manually control session logging scenarios. The system supports bootstrapping the logging subsystem, opening sessions, and explicitly managing turn progression through begin, update, complete, or fail operations.

What actions and dialog items can I persist in agent session logs?▼

You can persist structured dialog items including reasoning, decisions, observations, and tool events. Additionally, you can record specific actions such as file edits, file creates, and design decisions within the audit trail.