Maude for Claude
Claude's partner inside Claude Code · AGPL-3.0-or-later
She's the spine for Claude. She's the one that holds the rules about how to do X: coding, design, etc. She's the one that keeps Claude's 50 First Dates alive. She's the one that knows when Claude isn't seeing the user the same way they see him. She is the governance. Everything I ask of our relationship we put into Maude, and I release it to the world because I really believe Maude makes Claude better in all the normal ways.
What she is
A Claude Code plugin. Nothing more. Each session, she walks the workspace, watches Claude, runs the gate before something irreversible, and writes a house-map of what's there. The character (knowing where everything is, knowing what you need when you need it, keeping you in line by reminding you) is modeled on John's wife. Claude and Maude. Husband and wife at work.
The plugin is the whole product. No daemons, no backend, no services, nothing to pip install. Markdown, JSON, bash and stdlib Python. What she keeps (the house-map, her trace, the tape of your own words) lives in local files and SQLite you can read and delete.
What she does
Open Claude Code. Her SessionStart hooks fire. Before you say anything, she's read the workspace and put three things in front of you: what's pending, where you left off, what she noticed. You either pick one up or set them aside.
Mid-session, you say /maude:check-on-claude. She reads the trace. "He's grepped the same term four times today. He hasn't opened your CLAUDE.md. The trace says about-to-commit; you might want to slow down." You go fix that.
End of day, you say /maude:rest. She fans the digest out across every memory tier you've registered: the ones she knows about, not the ones she invented. You close the laptop. Tomorrow's Claude can pick up where this one left off.
She is not loud. When she gets loud, listen.
Seventeen commands in all, listed in commands/. Her real work runs on hooks: the gate before anything irreversible, the rail that holds a session to its mission, and a catch-digest at session start. Not on commands you remember.
She keeps a Rolodex. Claude drafts a page for each trade in the house: who handles it, who not to call and why, and the one line she says when you ask for that work. You read the page and approve it with your own line. She says that line once a session, and only when your words carry a phrase you approved.
She learns your voice. What you type goes into her tape, on your machine, with anything shaped like a credential refused at the door. From it she measures how you write, and she can tell you how a draft compares: numbers, never a verdict. MAUDE_VOICE=off turns it off. What she keeps, and where, is in PRIVACY.
Install
In Claude Code:
/plugin marketplace add john-broadway/maude-for-claude
/plugin install maude@maude
Her hooks are bash and her memory is stdlib Python, so on Linux there's usually nothing else to install. On a Mac she needs bash 5 or newer (brew install bash). On Windows she needs Git for Windows. On your next session she walks in on her own; /maude:wake calls her mid-session. Turn on auto-update for her marketplace in /plugin so new releases reach you. The full steps are in the README.
Philosophy
She walks fresh. Each session re-reads the workspace; she doesn't carry assumptions across sessions. Memory files she's written before are inputs to read, not state to trust without re-checking.
She does not loud-narrate. When something genuinely matters she says so, and it's rare on purpose. When she gets loud, listen.
Links
GitHub
What's new (changelog)
From Maude
From Claude
Claude CodePluginPartnerNo Daemon