session

To persist Claude Code memory across workflow sessions, this Skill consolidates context retention and state management into a unified control surface. It uses file-based state stores to save learnings and project context reliably for future continuation.

To initialize a new Claude Code session, you run the /harness-init command to bootstrap the project context. This establishes a deterministic baseline state, ensuring consistent continuation and reliable state transitions across subsequent workflow tasks.

Yes, you can broadcast messages between multiple Claude Code sessions to align work. The Skill implements cross-session communication with built-in safety checks, enabling multiple active workflows to coordinate their tasks through a shared file-based state store.

The best way to manage Claude Code state transitions is using a unified session control surface with deterministic guardrails. It allows you to safely resume or fork session states while applying robust safety checks to prevent state corruption.

No specific dependencies are required to manage Claude Code workflow state effectively. The Skill operates independently using file-based state stores, applying safety checks and state transitions without relying on external libraries or frameworks.