◦ Prompt · Mind

Give Your AI Agent a Brain and a Memory — From a Stateless Chatbot to an Assistant That Stays Herself and Remembers You, in One Session

Paste this into Claude Code, Cursor, or Aider and it interviews you about the agent you already have — its stack, whether it remembers anything today, whether its voice drifts over long chats — then does a strictly read-only pass over your codebase to see how it actually thinks before it changes a line. Only then does it help you build the brain that runs Trillion: a personality that lives in an editable file and reloads the moment you save it, a two-block system prompt that keeps the whole personality resident every single turn without ballooning your bill, an always-loaded core-knowledge layer so it never re-asks what it should already know, working memory that persists and recovers across sessions, and a typed, file-backed long-term memory with semantic recall — written both by the agent's own hand through tools and by an automatic end-of-session extractor that dedupes before it saves. It finishes with a self-knowledge layer so the agent knows what it is, and a personality checkpoint that stops it sliding into generic-assistant voice deep in a conversation. Interview first, map second, then build tier by tier — each tier ships independently with its own verification.

Jul 3, 2026agentbrainmemoryrecallpersonalitycontext-engineeringclaude-apianthropic-sdktutorial
◦ 4,617 builders waiting

Want the agent behind these prompts?

These prompts came out of building Trillion. The whole thing is going open-source on GitHub. Drop your email and I'll ping you the moment the repo drops.

I'll send a one-time link to confirm your email. Nothing else.

◦ Next prompt
Give Your AI Agent a Scout — From Hard-Coded Prompts to Operator-Tunable Doctrine in One Session

Paste this into Claude Code, Cursor, or Aider and it'll walk your agent codebase through building a scheduled scout sub-agent: a research loop that ends in a validated structured report, an evidence-first rubric with explicit hard kills, rotating hunting lanes that change what it looks for by the day, a review pipeline where a human decides and the agent never does, and — the part almost everyone skips — an instruction set that lives in editable documents your operator can retune from the UI with override, revert, version history and hot reload, instead of a Python constant nobody can reach without a deploy. Interview first, then build tier by tier. Each tier ships independently with verification.