akm-mcp
stillyou
English | 中文
Memory tools remember what your agent did. stillyou remembers what you decided — and what actually shipped.
Your agent forgets. What remains is still you. — distill yourself, one session at a time.
Every session ends in amnesia: the deliverables, the decisions, the rejected alternatives, the methodology you settled on — gone. stillyou captures them automatically and hands them to your next session.
$ claude
> Continue the AI video tool comparison from last time
⏺ Your ledger has relevant history:
[5802983d] video-tool-pricing-comparison@v1 (file/final, verified)
Last conclusion: Kling wins on cost-per-second (¥66/mo ≈ 66s of video).
Building the incremental comparison on that methodology — not re-deriving it...A fresh session, zero re-explaining. That answer cites a ledger entry distilled from a session three weeks ago — same methodology, human-verified conclusion.
Install (30 seconds)
curl -fsSL https://raw.githubusercontent.com/An-idd/stillyou/main/install.sh | sh
~/.stillyou/bin/stillyou init # pick a ledger location + register Claude Code hooks — doneWorks with Claude Code today; Codex / ZCode / Cowork read the same ledger via MCP. Building from source needs bun: bun install && bun build --compile packages/cli/src/main.ts --outfile ~/.stillyou/bin/stillyou.
The five commands you'll actually use
| find past conclusions, files, methodology (superseded versions hidden) |
| full entry + provenance: which session, from what inputs, why |
| endorse what you've checked — it ranks up and never decays to zero |
| ledger health: entry breakdown, stale warnings, failed-distill alerts |
| prefer one nightly batch over per-session distillation |
Everything else is automatic: writes are journaled by hooks (zero LLM), sessions distill in a detached background process, and your first message each session pulls in relevant history under a hard token budget.
How it differs from what you already have
Versus | The one-line boundary |
Just re-running | Re-runs can't buy back consistency or verified status — no model speed fixes two reports that disagree |
claude-mem & memory frameworks | They record the process (what happened); stillyou records the results (what remains, what superseded what, what's verified) |
CLAUDE.md / platform memory | Platforms remember facts about you, locked in their fence; stillyou records your outputs, in plain files you can walk away with |
git | stillyou's territory is git's blind spot: decision rationale, rejected alternatives, outputs that never enter a repo |
Built for: solo creators, serial writers, analysts, vibe coders — anyone whose work is a series, not one-offs, and whose outputs live outside git. Not for: one-off tasks, chat-only use, heavyweight engineering teams (git + CI is their home turf).
Three promises: your data stays in plain markdown + jsonl you can grep (delete stillyou, keep everything); hooks never block or break your sessions; uncertain provenance stays blank — no guessing, ever.
Learn more
Full guide — data format, cost & privacy (read this before cloud-syncing the ledger), scopes, MCP, architecture, roadmap
Design rationale (Chinese) · A usage story (Chinese)
The long game: externalized judgment — what the ledger becomes after months of use
MIT © An-idd
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/An-idd/stillyou'
If you have feedback or need assistance with the MCP directory API, please join our Discord server