session-relay

Transfer session control and resume from saved checkpoints.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/FlexNetOS/envctl --skill session-relay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-relay
Source: https://github.com/FlexNetOS/envctl/tree/main/.agents/skills/session-relay
Command: npx skills add https://github.com/FlexNetOS/envctl --skill session-relay

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The session-relay skill addresses the issue of context rot and token burn in long-running harness loops by providing an efficient mechanism for transferring session control from one session to another without data loss.

Core Features & Use Cases

  • Session Handoff: Facilitates handoff between different sessions, allowing loops to continue from where they left off without loss of context.
  • Checkpointing: Automates checkpoint creation during session transitions, preserving the state of the loop.
  • Resume Capability: Ensures that sessions can resume their execution from the last saved checkpoint, even if they were manually stopped or ended.
  • Use Case: Ideal for managing resource-intensive processes such as large-scale computations, code deployments, or data synchronization where frequent sessions might otherwise be terminated by the user or the system.

Quick Start

Hand off the current session and resume from a saved checkpoint: session-relay handoff

Frequently Asked Questions about session-relay

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

FAQPage Schema
How does session checkpointing prevent context loss in long-running automated loops?

Session checkpointing prevents context loss by automatically saving the loop's execution state during transitions. This captures the exact context so automated processes can resume from the last checkpoint without data loss.

How do I transfer session control between automated processes without losing state?

You transfer session control between automated processes by executing a session handoff routine. This coordinates the transfer across communication channels, creates a checkpoint, and schedules a follow-up session to continue from the saved state.

What causes token burn in long-running harness loops and when do I need a session handoff?

Token burn in long-running harness loops is caused by maintaining continuous context over extended executions. You need a session handoff when resource-intensive computations risk manual termination and require context preservation to resume.

Can I resume an automated execution loop after it has been manually stopped?

Yes, you can resume an automated execution loop after it has been manually stopped. The checkpointing mechanism ensures that sessions resume their execution from the last saved checkpoint, preserving the loop's state.

Does session-relay support cross-identity communication channels for state transfer?

Yes, session-relay requires proper coordination across cross-identity communication channels to execute state transfer. This ensures that session control and checkpoints are accurately handed off between different identities.

What are the limitations of using session checkpointing for large-scale computations?

The primary limitation of session checkpointing for large-scale computations is the need for proper coordination across communication channels. If checkpointing routines are not executed correctly, the automated loop may fail to resume properly.