Meridian

Behavioral guardrails for Claude Code — enforced workflows, persistent context, and quality gates for complex tasks.

Current version: 0.3.1 (2026-02-23) | Changelog

If Meridian helps your work, please star the repo and share it. Follow updates: X (@markmdev) • LinkedIn

The Problem

Claude Code is powerful, but on complex tasks it struggles with:

| Problem | What happens | |---------|--------------| | Context loss | After compaction, Claude forgets decisions, requirements, and what it was working on | | No built-in memory | Claude can't remember lessons learned — it repeats the same mistakes because it doesn't know it already made them | | Forgets prompt details | With large context, Claude starts ignoring parts of your CLAUDE.md instructions | | Shallow planning | Plans lack depth, miss integration steps, and break during implementation | | No task continuity | When you return to a task next session, Claude doesn't know what was done, decided, or tried |

You can write instructions in CLAUDE.md, but with large context Claude starts forgetting details from the prompt.

What Meridian Does

Meridian uses Claude Code's hooks system to enforce behaviors automatically:

| Capability | How it works | |------------|--------------| | Context survives compaction | Hooks re-inject task state, guidelines, and your docs after every compaction | | | Agent workspace () tracks decisions, discoveries, and context across sessions — Claude picks up where it left off | | | Monitors token usage and prompts Claude to save context before compaction happens | | | Planning skill guides Claude through thorough discovery, design, and integration planning | | | Plan-reviewer and code-reviewer agents validate work before proceeding | | | Add your architecture docs, API references, etc. to — they're injected every session |