Session Context

Carry intent, constraints, and governance context across Odylith session restarts.

34|3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/odylith/odylith --skill session-context-odylith
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Session Context
Source: https://github.com/odylith/odylith/tree/main/odylith/skills/odylith-session-context
Command: npx skills add https://github.com/odylith/odylith --skill session-context-odylith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures grounded Odylith sessions by carrying intent, constraints, governance context, and memory across restarts and workstreams, eliminating the need to re-discover repository state from scratch.

Core Features & Use Cases

  • Deterministic session restarts with exact seeds and context
  • Context carry-forward across workstreams, components, and memory
  • CLI-first policy enforcement and governance continuity
  • Recoverable memory of constraints, validation obligations, and risk signals

Quick Start

Instruct Odylith to resume the current session from its known seeds and preserve governance context for consecutive turns.

Frequently Asked Questions about Session Context

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

FAQPage Schema
How do I maintain session context and governance state across CLI workflow restarts?

Session context is maintained across CLI workflow restarts by carrying intent, constraints, and governance memory using deterministic seeds and exact-ref lookup, ensuring grounded continuity without re-discovering repository state.

What is deterministic session memory for preserving intent and constraints?

Deterministic session memory preserves linked workstreams, components, and decision history by applying exact seeds during session starts and context refreshes, ensuring recoverable validation obligations and risk signals across runs.

How do I carry forward decision history and workstream links after a session restart?

Carry forward decision history and workstream links by resuming from known deterministic seeds, which preserves governance context, validation obligations, and risk signals for consecutive turns without re-discovering state.

Does this session memory approach enforce CLI-first policy governance during context refreshes?

Yes, CLI-first policy enforcement and governance continuity are applied during session starts, restarts, and context refreshes, ensuring constraints and validation obligations remain active across consecutive workflow turns.

When should I use deterministic seeds for session continuity instead of manual context recovery?

Use deterministic seeds for session continuity when you need to preserve governance context, linked workstreams, and decision history across multiple restarts, eliminating manual repository state re-discovery.