We give you your own private codebase and database. Set up for you in one click. No surgery yourself.
Details
Someone shared this with you so your AIs actually remember you.
No account with us.
- No payment. Everything sits under your own accounts.
A private codebase and a database. - GitHub. One click. If sign-in fails, a code option sits under “Having trouble?”.
Never a fake “connected”. - Supabase. One click. Same deal.
A code option if sign-in fails. - AI tools. One paste each. No shared sign-in exists across them.
So each gets a ready-to-paste block. - Credentials never go in the codebase. No server of ours touches your keys.
Pasted codes are checked in your browser. Never saved. - “Done” means read back. A step counts only after the provider confirms it.
Provider errors are shown unedited. - You start from everyone's best setups — one shared register.
- You never sync anything yourself. Your AIs do it for you.
Explain this to me
I am looking at a page called PowerUpMyAI. Its address is powerupmyai.com. Explain it to me, simply. What it does. What I get. What could go wrong. Use short lines. If you can open web pages, read powerupmyai.com first, then explain. If you cannot open web pages, say so. Then explain from this description only. Description: the page creates one shared memory for every AI I use. It sets up a private codebase and a private database under my own accounts. Every AI reads and writes the same memory, so I do not repeat myself.
Download every template file and set things up by hand. Fill in what you already have (or plan to have) and the paste blocks below update to match.
Your browser will save each file one by one. Allow multiple downloads if it asks. Files:
00-MUSE-MANIFEST.md · README.md · SOUL.md · IDENTITY.md · USER.md · AGENTS.md · MEMORY.md · DECISIONS.md · CONNECT.md · ORCHESTRATION.md · CAPABILITIES.md · BEST-PRACTICES.md · UPGRADES.md · skills/README.md · skills/memory-hygiene.md · skills/verify-before-claiming.md · skills/import-and-reconcile.md · agent.config.example.json · .env.example · .env.service-role.example · .gitignore · db/001_starter_schema.sql · tools/import_md.py · tools/export_home.py · skills/building-things-simply.md · skills/building-things-simply-field-notes.md · skills/software-craft.md · skills/front-end-craft.md · skills/orchestrating-your-agents.md
So they know who you are.
Details
- One identity runs through everything.
- It prefills your USER.md and suggests your repo name.
- Use the same name for GitHub and Supabase. The accounts line up as yours.
Suggested from your name; change it freely. Lowercase letters, numbers and hyphens. It will be created private. Nothing public, ever.
Details
A “codebase” is a private folder online.
It keeps every version of your files. Only you can see it. Checking…
- ✓Token verified against GitHub (reads back your username) · ~10 seconds
- ✓Private folder created · ~10 seconds
- ✓Template files uploaded · ~10–30 seconds
- ✓Folder read back. Confirmed private, files present · ~10 seconds
Having trouble? Connect with a code instead
Only if the button above fails. Make a one-time code on GitHub, paste it here:
- Tap here — GitHub opens, right screen, boxes ticked.
- Name box: “agent-home setup”. Empty? Type it in.
- Scroll down. Tap the green Generate token.
- Copy the long code starting
ghp_(copy icon). - Back here, paste it below. It's checked instantly.
Sent only to GitHub, from your browser. Never saved. Delete it on GitHub once setup finishes.
Details
A “database” is where your memory is stored safely.
Organised, searchable, locked so only you can open it. Checking…
No Supabase account yet? Create one free (it offers GitHub sign-in — use the same account as step 1 so everything lines up).
- ✓Token verified (organisations listed) · ~10 seconds
- ✓Free project created · ~10 seconds
- ✓Project is live · can take a few minutes
- ✓Starter schema applied · ~10 seconds
- ✓Tables verified by querying the database · ~10 seconds
Having trouble? Connect with a code instead
Only if the button above fails. Make a one-time code on Supabase, paste it here:
- Tap here — Supabase opens on the token page.
- Tap Generate new token. Name it “agent-home setup”.
- Copy the long code starting
sbp_. - Back here, paste it below. It's checked instantly. Then “Create my memory store” above works.
Sent only to Supabase, from your browser. Never saved. Delete it once setup finishes.
Completed steps stay done. You lose nothing you finished.
Details
Your AIs can't see this by themselves. One paste per AI — this message does the rest.
Details
Links may include the sharer's referral code.
Paste once into each app.
Copy-paste messages
The one safety rule:
- Everything created is private and yours: repo under your GitHub, database under your Supabase.
- This page keeps no copy of your tokens or keys.
- To cut access: revoke the token in the provider's settings, delete keys from your local
.env. - Now revoke the two setup tokens you pasted. Setup is done, and they've served their purpose.
Confirm each app is wired: paste it this message
How to read the reply:
- Correct verification phrase + correct facts = strong evidence it's wired. Not proof.
- Wrong or missing phrase = not wired. Even if the rest sounds plausible.
- It names a blank field = wired, just not filled in yet. Not a failure.
- It says “I can't read your agent home yet” = not wired. Paste the full setup block from
CONNECT.mdfirst.
Send the matching message to each AI app you use. It asks the app to reply with: the verification phrase from MEMORY.md (verbatim), your name from USER.md, one fact from MEMORY.md (word for word), and the canonical-store line.
Full setup blocks
The longer first-time blocks (also saved as CONNECT.md in your repo). There is no shared one-click sign-in across these tools. A generated paste block is the honest version.
Your local .env. Save this, never commit it
This is the only key file an AI app may ever draw from, and the only key in it is SUPABASE_ANON_KEY.
.env.service-role (importer only — never give this to any AI app)
Save this as a separate local file next to your .env. Only the importer (tools/import_md.py) on your own machine uses it. It has full access to your database.
Read back from your home just now.
Save this database password now
Save it now.
If you ever lose it, you can reset it in Supabase.
Nothing breaks.
Made in your browser for the new project.
Supabase shows it once. It is never saved in your codebase.
You need it only for direct database connections.
Most tools use the API keys in your .env instead.
- ✓
agent.config.jsoncommitted (ref + URL only) - ✓
CONNECT.mdcommitted - ✓Wiring read back from the codebase and verified
Optional: GitHub Secrets (manual — this page does not do this for you)
- Only needed if you later run GitHub Actions against your database. Most people never need it.
- This page doesn't do it for you. Adding secrets needs GitHub's encryption flow.
- Manual path: your repo → Settings → Secrets and variables → Actions → New repository secret.
- Add
SUPABASE_URLandSUPABASE_ANON_KEYfrom your local.env, one at a time. - Add
SUPABASE_SERVICE_ROLE_KEYonly if an Action truly needs it. It has full access.
From BEST-PRACTICES.md, the shared register of what we've learned building agent setups like this. Only checks this page actually verified during your setup are listed. Anything not verified is not claimed.
Already have memory files? An export, notes, plain local files — add them here.
- Read in your browser only.
- Exact duplicates dropped.
- Every conflict shown to you — you pick.
- Nothing is silently overwritten. Ever.
Honest label: this is a file import, not a live connection. You export once, and the files join the same reconcile below.
- Open the Notion app → Settings → Export all workspace content.
- If it arrives as a zip, unzip it.
- Come back here and add the Markdown (.md) files with the picker below. They reconcile exactly like an AI app's export.
- Appends reconciled memories to
MEMORY.md. - Writes an
IMPORT-REPORT.md: sources, dropped duplicates, conflict resolutions. - Needs the repo from setup — import earlier and it rides along when the repo is created.
Rows prepared for the memories table
Load them with tools/import_md.py from your repo, or paste into your own import. owner_id is left as YOUR-AUTH-USER-ID on purpose: it must be your Supabase auth user id, and this page will not invent one.
Download every template file and set things up by hand. Fill in what you already have (or plan to have) and the paste blocks below update to match.
Your browser will save each file one by one. Allow multiple downloads if it asks. Files:
00-MUSE-MANIFEST.md · README.md · SOUL.md · IDENTITY.md · USER.md · AGENTS.md · MEMORY.md · DECISIONS.md · CONNECT.md · ORCHESTRATION.md · CAPABILITIES.md · BEST-PRACTICES.md · UPGRADES.md · skills/README.md · skills/memory-hygiene.md · skills/verify-before-claiming.md · skills/import-and-reconcile.md · agent.config.example.json · .env.example · .env.service-role.example · .gitignore · db/001_starter_schema.sql · tools/import_md.py · tools/export_home.py · skills/building-things-simply.md · skills/building-things-simply-field-notes.md · skills/software-craft.md · skills/front-end-craft.md · skills/orchestrating-your-agents.md
Details
Your agent home lives in your GitHub and your Supabase now, not here.
You don't need this page again. But it stays here as your check-up if you ever want one. Your repo and database links are above; everything else lives inside the repo itself.
Who's set up
Names and repo links only.
This link is your key. Anyone who has it can see this list (names and repo links only), so keep it private, the way you'd keep a password.
Make a personal share link
A personal link for someone you know — it greets them by name and notes that you shared it. It isn't a beta code; the invite codes above are the gate.