Made for people who use more than one AI.
Alwen helps most when your work is spread across tools and the decisions behind it are spread across weeks.
Decide once. Every tool builds on it.
Your plans live in ChatGPT, your code in Cursor, your decisions in Slack threads nobody can find a month later.
- Decide something in Claude in the morning; Cursor builds with it that afternoon
- @alwen turns a “let's build this” in Slack into research, a judgment call and a pull request
- Every decision lands in the journal with who made it and why
- Decision
- Pricing stays usage-based, never per seat.
- Why
- Per seat punishes teams for sharing the memory.
- Linked
- Billing page task in Cursor, thread in #product
Claude, from a chat about pricingSwitch clients without the recap.
Five clients, five sets of preferences, and the same background questions every time you switch.
- Contact
- Lena, head of ops. Prefers one-page memos.
- Never
- Mention the pilot in writing until they announce it.
- Tone
- Plain words, numbers first, no slides.
A note per client with the people, the history and what they care about
Rules per client — tone, formats, what never leaves the room
Every session starts with context instead of a five-minute catch-up
Findings that remember where they came from.
Sources, findings and half-formed ideas spread across chats you'll never scroll back to.
- Finding
- Most people keep notes in three places or more.
- Sources
- 4 links, checked Oct 9
- Tags
- research, onboarding
Grok Bot, research for a job- Grok Bot research saved with its sources and tagged so you can find it
- “Still true?” questions on findings that may have aged
- Search across everything any tool ever saved for you
Every coding agent starts from your conventions.
Each coding agent starts from zero: your stack, your conventions, last week's architecture decision.
- One rules file, compiled into CLAUDE.md, AGENTS.md and .cursorrules
- Architecture decisions logged the moment they're made
- @alwen hands tasks to Claude Code, Cursor or GitHub Copilot and reports back
- Always
- Server components by default; client only for state.
- Never
- Add a dependency without a note in the journal.
- Applies to
- Claude Code, Cursor and Codex
What the team knows, in one place everyone can ask.
Knowledge lives in people's heads, private chats and threads nobody can find.
- Decision
- Team vaults ship behind a flag first.
- Asked by
- Maya, approved in the thread
- Job
- jobs/7k2q9a.md, done Thursday
Slack, saved from #product