resume-session

Resolve ambiguous session references across tmux windows and transcript archives.

1|Updated Mar 24, 2026

Search Tags:#transcript #agent workflow #session management #tmux #context recovery #asana

Ready to run

npx skills add https://github.com/EdgeApp/edge-dev-agents --skill resume-session-edgeapp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resume-session
Source: https://github.com/EdgeApp/edge-dev-agents/tree/main/.cursor/skills/resume-session
Command: npx skills add https://github.com/EdgeApp/edge-dev-agents --skill resume-session-edgeapp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tmux, node, jq, and includes scripts (resource) components.

What problem does it solve?

This skill solves the frustration of losing track of complex AI development sessions, preventing the accidental creation of duplicate conversations or the loss of context when switching between tasks.

Core Features & Use Cases

Fuzzy Session Resolution: Identifies the correct session across Asana tasks, transcripts, and tmux windows using natural language references.
Context-Aware Resumption: Automatically determines whether to reattach to a live session or fork a historical transcript based on the session's specific type and state.
Use Case: When you need to return to a specific coding session from yesterday but cannot remember the exact tmux window name, you can simply ask the agent to find the session where you drafted the authentication logic.

Quick Start

Ask the agent to resume the session where you were working on the Asana task for the user authentication module.

Frequently Asked Questions about resume-session

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

FAQPage Schema

How do I resume an AI coding session in tmux without remembering the exact window name?▼

Resume AI coding sessions using fuzzy session resolution to search live tmux windows, RC names, and historical transcript archives via natural language references. You can simply describe the coding task, like drafting authentication logic, and the agent matches it to the correct context.

How does context recovery work when switching between agent workflows?▼

Context recovery works by indexing inventory across live tmux windows and historical transcripts, then enforcing strict lineage constraints. It automatically determines whether to reattach to an interactive session or fork a historical transcript based on the session's specific type and state.

Do I need jq and node installed to manage historical transcript archives for context recovery?▼

Yes, you need jq, node, and tmux installed to perform inventory indexing and safe session reattachment. These dependencies are required to resolve ambiguous session references and manage the resumption of interactive, chat-forked, or automated run sessions.

Can I find a specific development context by referencing an Asana task?▼

Yes, you can find a specific development context by referencing an Asana task. Fuzzy session resolution identifies the correct session across Asana tasks, transcripts, and tmux windows using natural language references to prevent accidental duplicate conversations.

What is the best way to prevent duplicate conversations when returning to an automated run session?▼

The best way to prevent duplicate conversations is using strict lineage and hygiene constraints during session management. The system resolves ambiguous references to specific contexts and safely reattaches to live sessions or forks historical transcripts based on their state.

Why does session reattachment fail when live tmux windows and historical transcripts have ambiguous names?▼

Session reattachment fails when ambiguous names prevent strict lineage enforcement across live tmux windows and transcript archives. Fuzzy session resolution requires specific natural language references to accurately determine whether to reattach or fork the session context.