GitHub
Your memory lives in a private repository in your own GitHub account. Alwen can only reach the repository you pick.
What changes
- Sets up your private alwen-vault repository with the folders and rules every tool reads
- Commits every change, signed by the tool that made it, with a sentence saying why
- Re-reads the vault when you push edits of your own
Set up
On the Alwen sign-up page, create alwen-vault on GitHub. Name and Private are filled in for you.
Connect GitHub and pick that one repository.
Open the repository on GitHub any time. It's yours.
What it reads and writes
Every write is a commit signed by GitHub, so you can see what it added and undo it.
Reads
- The vault repository, and nothing else in your account
Your vaultyou/alwen-vault
Writes
- Commits to the vault, each signed by the tool that made it
Works alongside
Config file
Plugin
Config file
Slack app
Cursor
Builds with your rules applied. Background agents can take work from Alwen.
Takes work from @alwenPluginGrok Bot
Every bot on your roster shares the memory. Good for research Alwen asks for.
Takes work from @alwenConfig fileClaude Code
Gets your rules as CLAUDE.md and builds what Alwen hands it.
Takes work from @alwenSlack appSlack
Mention @alwen to save a thought, find a decision, set reminders or hand off work.
Reads and writes the memory