skills.rest
ahostbr
ahostbrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ls-sessions

Save, restore, list, and check Windows Terminal agent sessions.

Updated Aug 5, 2026
Search Tags:#claude code#agent orchestration#session restore#snapshot management#windows terminal#terminal sessions#codex copilot
One-click install
npx skills add https://github.com/ahostbr/liteharness --skill ls-sessions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ls-sessions
Source: https://github.com/ahostbr/liteharness/tree/main/liteharness/catalog/skills/ls-sessions
Command: npx skills add https://github.com/ahostbr/liteharness --skill ls-sessions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You lose your running Claude/Codex/Copilot terminal workflows when you close, restart, or reshuffle terminals, and you need a reliable way to capture and resume the exact working state.

Core Features & Use Cases

  • Session snapshotting: Captures running Windows Terminal agent sessions and writes a reusable snapshot you can reference later.
  • Deterministic restore: Reopens Windows Terminal layouts and resumes sessions from the chosen snapshot, optionally using different window/tab/pane layouts.
  • Operational visibility: Lists available snapshots and reports current running sessions grouped by terminal for quick troubleshooting.
  • Example use case: You’re mid-way through a coding session across multiple agent CLIs and you need to restart your machine without losing context—save a snapshot now, then restore it after reboot.

Quick Start

Tell your AI to save a named snapshot of your current agent terminal state by running: /sessions save morning-layout

Frequently Asked Questions about ls-sessions

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

FAQPage Schema
How do I save and restore Windows Terminal agent sessions after a reboot?▼

You save terminal agent session snapshots by running a session manager script with a save argument, capturing the exact working state of Claude, Codex, and Copilot CLIs to restore after a machine restart.

Can I resume a multi-agent coding workflow across terminal restarts without losing context?▼

You can resume multi-agent workflows by saving a named snapshot of your active terminal layout before closing it, then restoring that snapshot to reopen the exact window, tab, and pane configurations with your agents intact.

Does this session snapshotting approach work with Claude, Codex, and Copilot CLIs on Windows?▼

Yes, this session snapshotting approach works with Claude, Codex, and Copilot CLIs running in Windows Terminal, capturing their running agent states and restoring them using configured layouts and snapshot storage paths on Windows.

How do I list available terminal session snapshots and check running agent status?▼

You list available terminal session snapshots and check running agent status by launching the session manager script with list and status arguments, which groups currently running sessions by terminal for quick operational troubleshooting.

What's the best way to manage terminal session continuity for agent orchestration workflows?▼

The best way to manage terminal session continuity for agent orchestration is to use deterministic snapshot management, saving your current multi-agent layout and restoring it to maintain workflow continuity across terminal restarts and operational debugging.

Related Skills

Explore More Software Engineering Skills→
ahostbrahostbr

ls-liteharness

Orchestrate multi-CLI agent terminal sessions with naming and message routing.

Community
Advanced
chriswesttchriswestt

context-restore

Load the most recently saved context across branches to resume work.

Community
Intermediate
jonmummjonmumm
2

cmux

Manage multiple Claude Code agent sessions across named workspaces in a terminal.

Community
Advanced
lirrensilirrensi
4

screenshot

Capture terminal screenshots across Windows, macOS, and Linux.

Community
Intermediate