Context Manager
Install context-manager to maintain hierarchical context.md files so Claude loads less of the repo and remembers project state between sessions.
Overview
context-manager is a plugin marketplace for the Build phase that maintains hierarchical context.md files to cut agent codebase loading and preserve project state across sessions.
What is this marketplace?
- Single-plugin marketplace from pklaw (pklawansky on GitHub)
- Maintains hierarchical context.md files across project folders
- Reduces full codebase loading by pointing agents at layered context
- Tracks project state across sessions for long-running solo builds
- Sourced from ./ with explicit session and loading benefits in description
- Marketplace lists 1 plugin
- Owner GitHub: pklawansky
What problem does it solve?
Agents reload huge repos and lose session context, forcing solo builders to repeat architecture and status every time they open Claude Code.
Who is it for?
Solo builders on multi-folder repos who use Claude Code daily and want durable, hierarchical context files managed as a plugin workflow.
Skip if: Tiny single-file experiments with no need for layered documentation, or teams that already enforce a monolithic ADR system with no agent integration.
What do I get? / Deliverables
After install, folder-level context.md maintenance gives agents a lighter, persistent map of project state instead of brute-force full-tree reads.
- Installed context-manager plugin
- Hierarchical context.md structure for reduced loading and cross-session state
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Build/pm is the primary shelf because the plugin is about ongoing project state and folder-level context artifacts, usable from idea through operate whenever you touch the codebase. PM subphase fits hierarchical context tracking and session continuity; agent-tooling is a close neighbor but pm better describes state files across folders.
How it compares
Project context documentation marketplace plugin, not a security auditor or deployment MCP server.
Common Questions / FAQ
Who is Context Manager for?
It is for developers using Claude Code on structured codebases who need hierarchical context.md files to track state and limit how much code the agent loads.
When should I use Context Manager?
Use it when sessions span days or weeks, folders multiply, and you need consistent context artifacts instead of pasting repo summaries each chat.
How do I add Context Manager to my agent?
Register pklawansky/Context Manager in Claude Code, install the Context Manager plugin from the marketplace, and adopt its context.md hierarchy in your project folders.