One folder. Every tool reads it first.

Alwen keeps your notes, rules and decisions in a private repository, in your GitHub or kept for you, and gives every AI tool the same way in.

Read firstClaudesearch("pricing")ChatGPTget_rules()Cursor.cursorrulesClaude CodeCLAUDE.mdCodexAGENTS.md
you/alwen-vault Private
  • profile.mdWho you are
  • rules/How tools behave
  • global.mdAlways, never, tone
  • knowledge/Notes, people, projects
  • journal/Decisions, dated
  • inbox/Saved by each tool
  • claude/3 new
  • slack/1 new
  • jobs/What @alwen did
  • .alwen/Built for your tools
Write backClaudejournal/…-pricing.mdSlackinbox/slack/…-onboarding.mdGrok Botinbox/grok-bot/…-research.mdCursorrule proposal, waits for youClaude Codepull request #128

Five things happen, every time.

From the moment you sign in to the day a note goes out of date.

  1. The vaultA private repository in your GitHub, made of plain markdown.
  2. Read firstTools search your notes and read your rules before they answer.
  3. Write backWhat they learn lands in the vault, signed by the tool.
  4. Tidy-upAlwen files, links and asks “still true?”
  5. Follow through@alwen in chat hands work to your agents.
Rules

Write your rules once. Every tool follows them.

Alwen compiles your rules into each tool's own format — CLAUDE.md, AGENTS.md, .cursorrules — and serves them live to the tools that connect. Change one line in your vault; every tool has it on the next commit.

How rules work

rules/global.md
  • Check the vault before suggesting anything
  • Lead with the answer
  • Never delete notes
  • Ask before anything involving money
  • .alwen/CLAUDE.mdClaude Code
  • .alwen/AGENTS.mdCodex
  • .alwen/.cursorrulesCursor
  • grok-bot-description.txtGrok Bot
  • get_rulesClaude, ChatGPT, Slack
Write back

What one tool learns, the others know.

Tools save three kinds of things, each in its own place, as a commit signed by the tool that made it. And your own edits always win.

  • Something learnedGoes to the tool's own inbox, inbox/<tool>/, until the tidy-up files it.
  • A decisionGoes straight to journal/, dated, with who made it and why.
  • A suggested ruleWaits for you. Tools never change your rules on their own.
  • Your own editAlways wins. Push a change and every tool reads your version.
Tidy-up

It stays useful because Alwen asks “still true?”

Every week on Free, Alwen files what your tools saved, merges exact duplicates and links notes that share a title or tag. On paid plans it runs daily with AI: it merges notes about the same thing, flags contradictions, and when a note looks out of date, asks you in a digest. You keep it, update it or archive it.

How the tidy-up works

AlwenWeekly digest
Launch is planned for the first week of December.
Written by Claude in March. A decision from last week says otherwise.Still true?

Three promises that don't change.

  • Your memory is yours.One private repository in your own GitHub. Leave any time and take everything with you.
  • Every tool, one memory.Claude, ChatGPT, Cursor, Claude Code, Codex and Grok Bot read and write the same notes; Slack, Telegram and Discord add to them.
  • Nothing is deleted.Old notes get a “still true?” question, never a delete. Every change can be undone.
Follow through

When work needs doing, @alwen hands it off.

It checks the memory, asks one question when something can't be undone, sends research to Grok Bot and building to Claude Code, Cursor, Codex or GitHub Copilot, then reports back in the same conversation.

Team vaultsjobs/7k2q9a.md Done
  1. AskedMaya, in #productTue 10:12
  2. Checked memoryFound 3 notes and last week's researchTue 10:12
  3. Used researchGrok Bot, Oct 9Tue 10:12
  4. ApprovedMaya chose behind a flagTue 10:14
  5. BuiltClaude Code opened #128Thu 16:31
  6. Reported backIn the thread and in the journalThu 16:40

Give every AI the same memory.

Start free