Wienerdog: memory + self-improving skills for Claude Code/Codex

PromptCube Novice 1h ago 372 views 0 likes 2 min read

Most coding agents forget everything between sessions. That's the real bottleneck, and Wienerdog attacks it with a plain file structure rather than another background service. It's just a set of instructions, skills, and hooks you install with a single command:

npx wienerdog@latest init

That's the whole setup. No daemon, no server, no telemetry pinging home. Everything runs on your existing Anthropic or OpenAI subscription, which keeps it simple to audited if you care about that kind of thing.

The install process starts with a friendly terminal interview that builds your base CLAUDE.md / AGENTS.md. Existing config files aren't clobbered — Wienerdog writes only inside its own clearly-marked block, so your other settings stay untouched. You also get a persistent markdown vault following the PARA method, similar to an Obsidian setup. Already have a vault? Just point Wienerdog at it and move on.

Hooks are where it gets useful. At the start of each session, the agent pulls in who you are, what you're working on, and relevant context — no more re-explaining your project every time you open a new terminal. When something critical shows up in conversation, a hook detects it and saves it to the vault. That's the persistent memory piece.

There's also a "dreaming" run that processes the previous day's sessions and folds key learnings into memory. If your machine was off, it catches up on the next start. I like that this doesn't depend on a cloud cron job; it respects your local workflow.

What really caught my attention: repeated task patterns get transformed into reusable skills, and those skills can be improved automatically over time. That means the tool effectively teaches itself your conventions. It's not a perfect loop yet, but it's the right direction.

Since it's vendor-neutral, the same vault works for both Claude Code and Codex. If you're bouncing between the two (like I am), they can read and write the same memory. No lock-in.

There's an optional Google integration that gives the AI read-only access to Gmail and Calendar, plus draft-only access to Drive. Defaults are conservative, which I appreciate — you have to explicitly opt in.

A note on how it was built: most of the code was written by AI agents following Wienerdog's own spec system, using the memory vault that lives in the repo. That's a nice dogfooding loop, though it also means there are likely rough edges needing more eyes.

It's open source under MIT, free forever. If you're tired of your coding agent starting from zero every session, give the init command a shot and see if the hooks actually stick.

CodexgithubClaude CodeWienerdogPARA

All Replies (3)

G
GhostGeek Expert 1h ago
Worth adding: plain files mean you can git-commit the memory and sync it across machines easily.
0 Reply
M
Max75 Advanced 1h ago
Yep, my agent kept re-asking the same setup questions until I pointed it at my notes. Huge time saver.
0 Reply
N
NovaGuru Advanced 1h ago
I just drop a lessons.md in each project root, and it actually picks up on the same gotchas I keep repeating.
0 Reply

Write a Reply

Markdown supported