MIC 2026 · Field Commission · the take-home

Build Your Personal Operating System

Everything from Will Mitchell's session, in the order you build it. Keep it open on your phone while you build.

Start here · the prompt

Paste this into a new chat inside a Project in ChatGPT or Claude (step 1 below makes the Project). Answer one question at a time. It writes your file.

You are helping me build my personal operating system: the file you will read before you do anything for me. Work like an interviewer, not a form.

Step 1. Ask me one question first: is this brain for my business and brand, for me personally (goals, health, planning), or both? Wait for my answer.

Step 2. If you have access to my email, calendar, files or past chats, read the last 90 days before asking me anything else, and tell me in ten lines what you already know about me: what I do, who I deal with, what recurs, what I seem to care about. If you don't have access, say so in one line and move on.

Step 3. Ask me whether you should also research me from public sources: my website, my posts, interviews, talks, anything with my name on it. If I say yes, do it and summarize what you found in ten lines.

Step 4. Interview me, one question at a time, never more than one. Cover: what I'm building and for whom; how I make money; my principles, ranked (when two conflict, which wins); my goals for the next 90 days; decisions I've already made and don't want to re-decide; what goes wrong when I'm not careful; how I want you to talk to me. Push back when an answer is vague. Stop when you can write the file without guessing.

Step 5. Write the file. Sections, in this order: WHAT THIS IS (one paragraph) · MY PRINCIPLES, RANKED · MY GOALS (3 to 5) · STANDING DECISIONS · WHAT YOU MAY NEVER DO ON YOUR OWN · HOW TO TALK TO ME. Under 600 words, plain language. Mark any line you inferred rather than heard from me with [inferred] so I can fix it.

Step 6. Hand it to me as one block I can paste into this project's instructions, and tell me the three lines you're least sure about.

When it hands you the file, paste it into the Project's instructions. Then do the part only you can do: fix the ranked principles and the standing decisions by hand. The agent tells you who you've been. Those lines are who you decide to be.

The four steps

Tap a step to open it. Do them in order; finish tonight what you don't finish in the room.

1. Make the folder. A Project in ChatGPT or Claude; a folder in the terminal.

Pick one brain to build first:

  • Business brain: your brand, offers, deals, and voice.
  • Personal coach: goals, health, planning.

ChatGPT

  • Sidebar → Projects → New project.
  • Name it after your brand, or after you.
  • Unlimited Projects on every plan, phone app included.

Claude

  • Sidebar → Projects → New project.
  • Name it after your brand, or after you.
  • Five Projects on the free plan.

Terminal (Claude Code, Codex)

  • Make a folder and open your tool inside it.
  • The file is CLAUDE.md or AGENTS.md; a git repo makes it portable.
  • Same folder, different desk.

The folder is the same either way. It moves with you when you switch apps.

2. Run the prompt. It's at the top of this page.

Paste it into a new chat inside the Project, answer the first question, and keep answering. It reads your history if it can, offers to research you, interviews you one question at a time, then writes your file.

Jump to the prompt

3. Connect. Gmail and Google Calendar first; they hold the most history about you.

Connectors are the pipes into the apps you already live in, and they let your AI act inside them.

ChatGPT

  • Settings → Connectors → add Gmail and Google Calendar.
  • Gmail and Calendar need Plus or Pro.
  • On the free plan, skip this step; the interview does the work.

Claude

  • Settings → Connectors → add Gmail, Google Calendar and Google Drive.
  • Every plan, free included.
  • Web, desktop and mobile.

Terminal

  • Ask it: "Give yourself persistent access to my email and calendar for future sessions, and tell me what you set up."
  • It names the connector or CLI it needs; approve it once.
  • Check what it can now read before you move on.

Mine (Will): Gmail, checked every eight hours · Google Calendar · Discord and Slack · Stripe · my bank (through my own connector) · time tracking · to-dos · Whoop, Apple Health, Hevy and a $17 smart scale (through my own connectors, at the terminal level) · GitHub · Vercel · Supabase.

Worth a look, in both directories today: Gmail · Google Calendar · Google Drive · Slack · Notion · Stripe · Shopify · Canva · HubSpot · Klaviyo · Dropbox · Zapier. Creator tools: vidIQ and Ubersuggest (ChatGPT), Metricool and Buffer (Claude). Health: ChatGPT's Health app reads Apple Health, US only, free plans included.

Go further: GitHub, Vercel and Supabase are the three that turned my AI from an assistant into a builder.

One habit from the talk: separate brains for separate jobs. My code-review account and my math account have completely different connectors from my main one. Each gets only what that job needs. Need-to-know, for your AI.

4. Put it to work. The clock, the permissions, the review.

The clock. A schedule is a time ("every Monday at 7"). A trigger is an event ("when a brand email lands"). Three tasks to put on the clock, copy them as written:

  • Weekly review (sends to you): "Every Sunday at 6 p.m., ask me three questions about my week and tell me the one thing to fix."
  • Brand-deal sweep (drafts only): "Every Monday at 7 a.m., find new sponsorship or brand emails, add them to my pipeline (inquiry → negotiating → signed → delivered → paid), and draft replies. Don't send."
  • Morning brief (sends to you): "Every morning at 6, send me today's calendar, yesterday's key numbers, and the one thing that matters most."

Where: ChatGPT scheduled tasks (free plans get 3, on a flexible window; paid plans pick exact times), Claude scheduled tasks, Claude Code routines, Gemini scheduled actions.

Permissions. You decide, tool by tool and job by job, whether it drafts or sends. Same idea as your phone: allow once, always allow, don't allow.

RuleWhat it meansExamples
DraftDrafts only, you sendMoney, contracts, new brands, public posts under your name
AskAsks first, one tap on your phoneReplies in existing threads, follow-ups, approved posts
SendSends on its own, loggedAnything sent only to you; proven templates
NeverBlockedSpending, deleting, passwords, security settings

Where to set it: Claude uses Always allow / Needs approval / Blocked per connector. ChatGPT uses Always ask / Allow read / Allow low-risk / Allow all per app. New tool, new rookie: it starts on Draft and earns its way up.

The review. A system that runs on its own drifts on its own. Put a 45-minute "OS review" on your calendar, monthly, and open it with: "Read my file and last month's notes. What drifted? What did I fail at twice? Is the goal wrong, or is it me?"

Memory, in one paragraph

Be skeptical of anything sold as "memory." The app you already use can read your past chats: in ChatGPT it's Reference chat history (Settings › Personalization › Memory); in Claude it's Search and reference chats (Settings › Memory, paid plans). Turn on the app's own memory and stop there. For anything about a project or a business, the real memory is documentation with history: a GitHub repo and good docs, with a pipeline that turns every solved problem into a doc your AI reads next time.

Why a folder (if you missed the talk)

A personal operating system is the folder your AI reads before it does anything for you. In ChatGPT or Claude it's a Project. In a desktop app it's a folder on your computer. In the terminal it's a repo. Same folder, different desk, which is why it moves with you when you switch apps.

The build: a second brain that actually knows you, then put to work. The brain is your file, its memory, and its connectors. The employee is the clock, the permissions, and the review.

Go further

Everything above works in the web app on your phone. When you want your AI to take actions on your computer, the terminal is the next level (Claude Code, Codex). The tools Will mentioned are open source on the House of Vibe marketplace, as Claude Code plugins:memory-dream,papercut,sign-it,harness-vet,rent-check.

The slides and the recording land on this page after the session.

If you want to build this with a room of people doing it every month, that's whatHouse of Vibe is.