CC-thread v2.1

Context drift and session limits often force developers to repeat themselves or lose track of decision logic across long-running projects. CC-thread v2.1 solves this by providing a structured, local-first system for archiving and restoring conversation state, key decisions, and technical milestones without relying on brittle chat histories.

What it does

• State Restoration : Matches and reloads specific workflow contexts based on project IDs or keywords.
• Milestone Archiving : Extracts conclusions, decisions, and next steps into a versioned local index.
• Context Condensation : Automatically maintains a context-condensed.md for workflows exceeding five records to keep context windows lean.
• Project Memory Sync : Dual-writes to both a readable local archive and project-scoped memory to ensure persistence across environments.
• Startup Management : Configures opt-in startup candidates to suggest relevant workflows when a new session begins.

How it works

1. Save : Invoke /cc-save at a milestone. The skill extracts key points, matches them to a workflow ID, and performs an atomic dual-write to your local archive and project memory.
2. List : Use /cc-load to view active workflows for the current project, filtered by last update and session count.
3. Restore : Select a workflow to inject historical conclusions and unfinished items into the current session.
4. Archive : Update metadata to hide dormant workflows from active lists without deleting the underlying data.

Frameworks & tools

Built for local filesystem integration using .json indexing and Markdown bodies. Supports Python 3.10+ for automated archive validation but can operate via host tools in restricted environments.

Why this beats prompting it yourself

Standard prompts lack a consistent storage schema, leading to fragmented notes that the LLM eventually forgets. This skill enforces atomic writes, index integrity, and a strict condensation threshold that prevents your context window from being flooded by irrelevant history.

Use cases

• Resuming a complex refactor after a multi-day break.
• Syncing architectural decisions between a CLI agent and a GUI-based IDE.
• Archiving "lessons learned" from a completed feature branch for future reference.
• Managing multiple concurrent workstreams within the same project directory.

Known limitations

Does not support cross-project memory access or whole-disk backups. Context restoration is limited to 500 Unicode characters for condensed files. Requires local file write permissions.