0.0B+/m
people use standalone AI tools
Each tool starts cold unless your context travels with you.
Why Use It?
0M/m
estimated multi-tool AI users
A simple 35 percent estimate across monthly AI users.
0.0T/m
context tokens left behind
Multi-tool users leaving 5,000 useful context tokens behind.
Why Not Other Tools?
| Native features |  |  | ||
|---|---|---|---|---|
| Context loaded before every answer | ||||
| One human-readable profile | ||||
| Agent changes require approval | ||||
| Section-level edit permissions | ||||
| Plain Markdown is the source | ||||
| Open source and self-hostable |
How It Works
Every agent reads it first
Before it answers, any agent pulls your Creed over MCP, so you never re-explain who you are, what you're building, or how you like to work.
Plan my week so I actually ship Helm v2.
Read Creed
Thought for 4s
Blocking7to11amfordeepwork,nomeetingsbeforenoon,andWednesdaysstaycall-free.IlinedtheweekuparoundtheHelmv2beta.Wantitdaybyday?
Ask anything…
It updates as it learns
When an agent notices something durable, it proposes a precise edit. It lands in your Creed as a diff. Approve it and the section updates in place.
Routines
Deep work 7 to 11am, no meetings before noon.
Review the week every Friday at 4pm.
Ship to production Monday through Thursday only.
And every change is visible
Open Activity to see what changed, who changed it, and whether it was accepted, rejected, or edited directly.
Chamath.md
Goals
Work
Review everything or nothing
You control what gets remembered.
Agents propose updates in real time, but nothing changes until you approve it.
Require approval for agent edits
Review proposed edits first.
BeliefsDirect
Creed's value depends on keeping the file large and exhaustive, capturing every passing preference so nothing is ever left out, even details that stopped mattering months ago.
Creed's value depends on keeping the file tight and high-signal, pruning stale detail so it stays sharp and self-improving as it grows, and trusting that less is more.
Let trusted agents write directly.
Agents can update your Creed without review, keeping your context current as you work.
AI inside the file
Identity
…/ 100SpecificConcreteThinVague
Scoring this section…
Reads like a real person
One line stays generic
Contains a stray line
Analysis
Score every section for signal, weak spots, and what to sharpen next.
Panel
SearchAskAgent
Open billing settings
↵Take me there
Panel
Search, ask, and let Creed draft reversible edits without leaving the file.
Preferences
TabTab
Press Tab and it finishes the thought in your voice, drawn from your whole file.
Get started in minutes
Question 1 of 3
How would you describe yourself?
1Describe yourself
Answer a few quick questions and Creed drafts your starter profile.
All agents
One prompt works with them all.
2Extract your context
Pull the context you've already built across your tools into one profile.
Credits spend
$3.24
Jul 17
Analysis$0.34
Tab$0.00
Panel$0.08
AnalysisTabPanel
3Connect your agents
Give each agent the same approved context through Creed's MCP connection.
Works with your stack
ChatGPT
Claude
Grok
OpenClaw
Hermes
Cursor
OpenCode
Devin
Codex
Claude Code
Replit
Whirl
v0
Custom
Common questions
Who you are, what you're working toward, how you like AI to talk to you, the people and routines that shape your week, plus any health, accessibility, or hard noes AI should respect. One concise profile, not a journal.
Because it doesn't stick, doesn't cross tools, and you end up repeating yourself. Creed gives every AI the same profile to read before answering, and lets them propose updates as they learn more about you.
Creed connects to agents like Claude Code, Codex, Cursor, and ChatGPT over MCP, and integrates with GitHub for version control. Support for tools like Notion and Obsidian is coming for editing and storage.
Durable things AI learns about you, a sharper preference, a new routine, a goal that shifted. Not session recap, not mood, not generic praise.
No. You can keep agent edits reviewable, or trust them to write directly when you want a lighter loop. The point is control when you want it, not friction by default.
Creed Open v1 is built for one owner and Personal Creeds. Shared Creeds are being developed for Creed Cloud and are listed on the roadmap.
