Docs

Everything about how Alwen works, from your first sign-in to the tools your agents call.

Start

From sign-in to your first shared memory.

Getting startedThree steps, a few minutes, no setup files unless you want them.Connect your toolsSetup for every tool: Claude, ChatGPT, Gemini, Perplexity, Cursor, GitHub Copilot, Slack and more.

Concepts

How the pieces fit together.

The vaultA private GitHub repository of plain markdown. Every tool reads it; you own it.RulesWrite how you want every tool to behave once. Alwen turns it into each tool's own format.Writing backHow a tool saves what it learns, and why nothing writes straight into your notes.Tidy-up and “still true?”How Alwen keeps the vault useful instead of letting it fill up.@alwen and jobsWhat happens when you ask @alwen in Slack, Telegram or Discord to get something done.TeamsOne plan for everyone, shared vaults next to each person's own, team channels, and a log of what Alwen did.

Reference

The exact tools and formats.

MCP toolsThe tools every connected app can call, and what each one does.Your own toolsOn Business: a tool of your own joins the memory with a key and takes research or building from @alwen.Note formatThe frontmatter every note carries, field by field.

For developers

One address for every tool.

Alwen is an MCP server. Any tool that speaks MCP connects here, signs in, and gets search, rules and write-back.

Server address

https://api.alwen.ai/mcp