Resume, checkpoint, or forward tmux team workflow state after context resets.
npx skills add https://github.com/geoyws/atmux --skill session-geoyws
Please help me install this Agent Skill. Skill: session Source: https://github.com/geoyws/atmux/tree/main/plugins/atmux/skills/session Command: npx skills add https://github.com/geoyws/atmux --skill session-geoyws
You need reliable session continuity across team work in tmux (and an OpenCode orchestration path), so that after a /clear you can resume the right in-flight work, and when ending the day you can cleanly shut everything down without losing context.
cont, preclear, handoff, and stop coordinate the correct behavior for resuming, checkpointing, forwarding, and end-of-day shutdown.team start/shutdown in the wrong context.handoff.md (and optionally HANDOFF.md / CONT.md) to preserve next-step instructions across /clear and across Claude vs OpenCode plugin orchestration.Run /atmux:session cont to continue after you’ve cleared context, using your saved handoff and dispatching the correct first actions to teammates.
High-intent search queries and answers about installing and using this skill.
To resume an agent tmux session after a context clear, you run the `cont` verb. It restores workflow state by reading a canonical `handoff.md` file to recover next-step instructions, tasks, and open decisions, then dispatches the correct first actions to teammates.
The safest way to shut down a tmux agent team at the end of the day is using the `stop` verb. It triggers a destructive end-of-day shutdown workflow that preserves in-flight context and performs necessary cleanup to prevent data loss.
Session checkpointing for agent orchestration works through the `preclear` verb, which performs non-destructive checkpointing. It writes current tasks, memory, and open decisions to a persistent handoff file before a context reset occurs.
Yes, you can forward an in-flight task to a different teammate in a tmux session using the `handoff` verb. It routes the preserved workflow state and next-step instructions to the correct teammate or operator using handoff read/write conventions.
Yes, this session continuity tool supports dual-harness orchestration for both Claude and OpenCode. It reads and writes canonical handoff files like `handoff.md`, `HANDOFF.md`, or `CONT.md` to preserve context across both orchestration paths.
The session lifecycle prevents team start in solo mode due to mode-aware safety detection. It identifies whether you are in driver, lead, solo, or no-team mode to block destructive actions and ensure operations match the current orchestration context.
kurokeitaDesign structured agent configurations for Claude Code plugins.
jlawsGenerate structured HANDOFF.md documents with session decisions, file paths, and next steps.
zach-sourceConfigure and troubleshoot tmux and zsh with plugin management and vi-mode.
DektoraGenerate and read structured DekSpec session handoff records in dekspec/.scratch/rotation-handoff/.