ChatGPT
ChatGPT reads the same memory as your other tools and writes back what it learns.
What changes
- Starts every chat knowing your projects and preferences
- Uses the notes your other tools saved, not just its own
- Logs decisions you make in ChatGPT where Cursor and Slack can see them
Set up
In Alwen, open Tools and copy your Alwen address.
In ChatGPT: Plugins+Add custom MCP server. On Business, Enterprise and Edu a workspace admin does this; Pro can search and read but not save.
Name it Alwen, paste the address under Connection and choose OAuth. Then Create as a pluginAllow on the Alwen page.
Turn Alwen on in a chat and ask: “What did I decide about pricing?”
What it reads and writes
Every write is a commit signed by ChatGPT, so you can see what it added and undo it.
Reads
- Your rules and profile, once per session
- Notes that match what you're working on
Writes
- What it learns, into inbox/chatgpt/ for the tidy-up to file
- Decisions, straight into journal/
- Suggested rules, which wait for you to confirm
Works alongside
Cursor
Builds with your rules applied. Background agents can take work from Alwen.
Takes work from @alwen
PluginGrok Bot
Every bot on your roster shares the memory. Good for research Alwen asks for.
Takes work from @alwen
Config fileClaude Code
Gets your rules as CLAUDE.md and builds what Alwen hands it.
Takes work from @alwen
Slack appSlack
Mention @alwen to save a thought, find a decision, set reminders or hand off work.
Reads and writes the memory