Filesystem Context Manager

Persist task state and decisions across Claude Code sessions using filesystem directories.

1|Updated May 5, 2025

Search Tags:#context #Claude Code #memory #persistence #filesystem #session-management

Ready to run

npx skills add https://github.com/jdeweedata/circletel --skill filesystem-context-manager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Filesystem Context Manager
Source: https://github.com/jdeweedata/circletel/tree/main/.claude/skills/filesystem-context
Command: npx skills add https://github.com/jdeweedata/circletel --skill filesystem-context-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains context across Claude Code sessions by persisting state to the filesystem, preventing loss of decisions and progress during long multi-session tasks.

Core Features & Use Cases

File-based context persistence: stores current task, decisions, blockers, and memory in a structured filesystem (e.g., ~/.claude/context, memory, scratch, plans).
Plan and memory continuity: preserves implementation plans and learned patterns across sessions.
Session continuity: resume work across conversations and agents, enabling multi-task workflows.

Quick Start

Start a new Claude Code session; the skill activates automatically when you save or resume work.
Create or edit context files under ~/.claude to persist current tasks, decisions, and memory.
In subsequent sessions, review the planned state and memory to continue where you left off.

Frequently Asked Questions about Filesystem Context Manager

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

FAQPage Schema

How do I preserve context across Claude Code sessions?▼

To preserve context across Claude Code sessions, you can use a filesystem-based layout to store current tasks, decisions, and memory in structured directories like ~/.claude/context. This automatically saves your progress for later resumption.

Why does Claude Code lose my implementation plans when conversations end?▼

Claude Code loses implementation plans when conversations end because state is not persisted by default. Saving learned patterns and plans to a filesystem memory directory ensures continuity across new sessions and agents.

What is the best way to resume work on long-running multi-session tasks?▼

The best way to resume work on long-running multi-session tasks is to persist state to the filesystem using context and plans directories. Subsequent sessions can then review the planned state and continue exactly where left off.

How do I save current tasks and blockers in Claude Code?▼

You can save current tasks and blockers in Claude Code by creating or editing context files under the ~/.claude filesystem directory. This stores your active working state and blockers for later retrieval.

Are there limitations to using a filesystem-based context manager for Claude Code?▼

A limitation of using a filesystem-based context manager for Claude Code is that it relies on manual or automated file edits within specific directories like scratch and plans, requiring deterministic activation via frontmatter metadata to function properly.