What Creed is

Your Creed holds the identity, goals, work, preferences, constraints, people, health, routines, and current context that should shape future replies. You own the file and decide what stays in it.

Connected agents read it before meaningful work. When they learn something durable, they propose a focused change. You approve it, reject it, or allow trusted agents to edit selected sections directly.

Creed is not a journal, chat history, or place to save everything. Keep only context that should change how an agent treats you.

Run Creed Open

You need Node.js 22 or newer, npm 10 or newer, Git, and a Supabase project.

git clone https://github.com/connorhpbrn/creed.git
cd creed
npm install
npm run setup
npm run dev

1. Open http://localhost:3001.

2. Enter the owner secret created in apps/open/.env.local.

3. Complete Personal onboarding and save your first Creed.

4. Open Connections and connect one agent.

Run the read-only doctor whenever you want to check the installation:

npm run doctor

Install Creed

npm run setup

Setup preserves unrelated environment values and asks before it changes the database. Secrets are written to apps/open/.env.local and are never printed after creation.

Manual setup

Use the manual path when the installer cannot run interactively.

cp apps/open/.env.example apps/open/.env.local
openssl rand -base64 48
openssl rand -base64 32
chmod 600 apps/open/.env.local

Then link Supabase, preview the migrations, apply them, and run the doctor.

cd apps/open
npx supabase login
npx supabase link --project-ref YOUR_PROJECT_REF
npx supabase db push --dry-run
npx supabase db push
cd ../..
npm run doctor

Deploy Creed

Vercel

1. Fork the repository and import it into Vercel.

2. Set the project root to apps/open.

3. Add the production values from apps/open/.env.example.

4. Set NEXT_PUBLIC_SITE_URL to the final HTTPS origin.

5. Preview and apply Supabase migrations from a trusted local clone.

6. Deploy, claim the installation, then verify a save and one agent connection.

Other Node.js hosts

npm install
npm run build --workspace creed-open
npm run start --workspace creed-open

The host must provide the required environment values and expose the configured site origin over HTTPS.

Configure the installation

Supabase

• NEXT_PUBLIC_SUPABASE_URL is the project URL.

• NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY is safe for browser requests because Row Level Security protects the data.

• SUPABASE_SECRET_KEY is server-only and must never use a NEXT_PUBLIC_ prefix.

Owner access

The owner secret authorises a browser once. Rotating it invalidates existing owner cookies. Keep the owner and encryption secrets in a password manager.

Optional services

GitHub OAuth adds manual Markdown push and pull. OpenRouter enables analysis, Panel, Tab, and onboarding composition. The editor and agent connections work without either service.

Maintain the installation

Read the changelog, back up Supabase, preview migrations, and run the doctor before restarting.

git pull
npm install
cd apps/open
npx supabase db push --dry-run
npx supabase db push
cd ../..
npm run doctor

A Markdown export preserves the profile. A full recovery also needs revisions, proposals, settings, tokens, and avatars from Supabase.

Write the context that matters

Every Personal Creed begins with five core sections: Identity, Goals, Work, Preferences, and Routines. Beliefs, Constraints, People, Health, and Context appear when you use them.

• Write facts that should affect future answers.

• Prefer concrete defaults, names, deadlines, and trade-offs.

• Remove stale details instead of preserving history.

• Create a custom section only when the context does not fit an existing one.

A short Creed that changes an answer is better than a complete biography that does not.

Control every change

Agents can read visible sections. Each section separately decides whether an agent may propose changes, edit directly, or only read.

• Propose: the agent drafts a change for you to accept or reject.

• Direct edit: a trusted agent applies the change immediately and records it in activity.

• Read only: the agent can use the section but cannot change it.

Use direct edit selectively. Identity, health, relationships, and strong constraints usually deserve review.

Keep the file sharp

Quality guidance looks for context that is specific, relevant, current, internally consistent, and complete enough to act on.

• Resolve contradictions before adding more detail.

• Turn vague preferences into observable defaults.

• Delete temporary states and completed goals.

• Review the weakest section first rather than rewriting the whole file.

Connect related sections

Type # in the editor and choose a visible section to create a Graph Tag. Two to four useful relationships per section is usually enough.

Nexus shows those relationships as a read-only graph. It ignores plain hashtags that do not match a real section.

Use Graph Tags for section relationships, not for topics, brands, tools, or decorative labels.

Connect an agent with MCP

1. Open Connections in your Creed installation.

2. Choose the agent and use its generated command, configuration, or connector link.

3. Complete authorisation in a browser that has owner access.

4. Ask the agent to read Creed once and confirm access.

The MCP address is your installation origin followed by /mcp.

https://your-creed.example/mcp

Common agent setup

Claude Code

claude mcp add --transport http creed https://your-creed.example/mcp --scope user

Run /mcp in Claude Code to authorise.

Codex

codex mcp add creed --url https://your-creed.example/mcp

codex mcp login creed

OpenCode

opencode mcp auth creed

Add Creed as a remote HTTP server in opencode.json before authorising.

ChatGPT, Claude, Cursor, and other clients

Add a custom remote MCP server using the URL shown on Connections. The application provides the exact connector action or configuration for supported clients.

How an agent should use Creed

1. Read the visible Creed before meaningful work.

2. Use it to shape tone, assumptions, priorities, and constraints.

3. When something durable is learned, propose one narrow update to the right section.

4. Do nothing when the information is temporary, uncertain, or already present.

Good proposal

“Lead replies with the answer, then give supporting detail.”

Bad proposal

“The user is tired today and wants a short answer.”

Use the HTTP fallback

Create a connection in Creed, store its token privately, and send it in the Authorization header. Never put a token in a query string.

curl -fsS https://your-creed.example/api/creed   -H "Authorization: Bearer $CREED_TOKEN"

Read access uses GET /api/creed. Proposals use POST /api/creed/proposals. Direct edits use POST /api/creed/write only where the section permits them.

MCP tools

Read

read_creed, list_creeds, list_sections, get_write_policy, creed_get_section, creed_search, creed_get_recent_activity, and creed_get_quality_report.

Change

creed_update_section, creed_append_to_section, creed_create_section, creed_delete_section, creed_rename_section, creed_recolor_section, and creed_reorder_section.

The focused change tools choose proposal or direct-edit mode from the live section policy. Agents should call get_write_policy instead of guessing.

HTTP API

• GET /api/creed returns the visible profile and its operating contract.

• POST /api/creed/proposals submits a structured proposal.

• POST /api/creed/write applies an authorised direct edit.

All endpoints require Authorization: Bearer <token>. Tokens are scoped to one connection and Creed. A missing or invalid token returns 401; rate limits return 429.

Troubleshooting

Database needs setup

Run setup again. It relinks Supabase, previews unapplied migrations, and asks before applying them.

npm run setup

The doctor cannot verify Supabase

Confirm the project is active and that the project URL and server secret belong to the same project, then run npm run doctor.

No browser authorisation opens

Run the client’s login or MCP authorisation action again. Confirm the browser already has owner access to the Creed installation.

An old connection returns 401

Remove the connection, add it again using the current MCP URL, and complete OAuth once more.