Private by default — your mail, calendar & notes stay on your machine Personal productivity setup · works with Google (Gmail + Calendar) or Microsoft 365
Set it up The flip Commands Field Guide Controls Yours vs rented Second act Copy the prompt
REPORT · Your operating week OWNER · you PERIOD · every week, recurring PREPARED BY · Sasha, your AI chief of staff
Your week OVERLOADED IN CONTROL

Meet Sasha — your chief of staff.

Sasha is the person who runs the day around you — reads your mail first, preps you for every meeting, keeps track of what's open — a personal AI that's genuinely yours, one anyone can stand up.

One copy-paste prompt turns Claude Code into a personal operating system, wired to your Google (Gmail + Calendar) or Microsoft 365. It runs your week — triage, meeting prep, status updates — and gets sharper every time you correct it. Five questions and one paste — most people read their first brief in about ten minutes.

no code required  ·  read-only by default  ·  nothing sent without your sign-off

New here? The Field Guide → shows how to get the most from every command — plain-language up top, power-user depth below.

Set it up · five questions and one paste

Stand it up.

No code, no terminal. Install one app, connect your mail & calendar, switch on Auto, paste the prompt — then Sasha asks five quick questions and builds around you. Most people read their first brief in about ten minutes.

Install the Claude desktop app & sign in

Download the Claude desktop app from claude.com/download — a normal app installer for Mac (.dmg) or Windows (.exe). Open it and sign in with your Claude account. You never need a terminal or any code. The app runs on a paid Claude plan — Pro is about $20/month. This setup is free; the AI that powers it isn’t.

Windows detour (one time, a couple of extra minutes): the first time you open it, the app may ask you to install Git for Windows — click Install, accept the defaults, let it finish, then reopen the Claude app. That’s the whole detour. (Mac has nothing extra.)

Prefer the command line? The Claude Code CLI at claude.com/claude-code is the very same engine — every step below works there too.

Connect your mail & calendar

On your Claude account at claude.ai → Settings → Connectors, turn on Google (Gmail + Calendar) or Microsoft 365 and sign in to authorize it. Your AI OS works read-and-draft: it reads your mail and calendar, drafts locally, and anything outward waits for your OK — that per-action approval is the guarantee on either provider. On Microsoft 365 the connector itself is read-only on top, which takes nothing away: Microsoft 365 is every bit as capable as Google here. The difference is access, not capability.

Pick the one you can actually connect. Google is quickest — most people, personal Gmail included, can connect it themselves. Microsoft 365 needs a work account your organization has enabled — a personal @outlook.com or @hotmail.com address can’t connect at all.

Most people can approve it themselves; some tenants still need a one-time admin consent — so confirm you can connect before you invest time. If the connection ever needs a fresh sign-in, Claude tells you and reconnects the moment you re-authorize. The setup prompt can walk you through it.

Open the Code tab and pick your home folder

In the app, click the Code tab, then create or pick a folder to be Sasha’s home — e.g. a new folder called ai-os. That folder is where your memory and notes live, on your own machine.

Switch to Auto — before you paste

The one step people miss. The mode control sits in the top-left corner, just above where you type — switch it to Auto and accept the one-time confirmation dialog. (If Auto isn’t offered there, enable it once in the app’s Settings.)

Auto means the build runs in one pass instead of stopping at every file — and the guardrail that matters doesn’t move: your mail and calendar stay read-and-draft, and anything outward waits for your per-action OK (on Microsoft 365, the connector itself can’t write at all). Near the end it asks permission to schedule the quiet data refreshes that keep your morning brief instant; that’s expected — say yes.

Paste the setup prompt as your first message

Copy it below, paste the whole thing, and send.

Say hello — five quick questions

Sasha introduces herself and asks five questions: what fills your week, which account to wire up, what to take off your plate first, what she should never do without asking, and how you like things. Say “skip” to any of them — she starts with sensible defaults and learns as you work. Then she builds everything shaped to you and explains what she made.

See it work — your first win

The moment the build finishes, it hands you your actual day — today's meetings, what's waiting on you, deadlines this week — proof it's wired to your real mail and calendar. That's the payoff, and you didn't have to do a thing. From your next session on, type /brief any morning to get it again for that day; your other commands (/triage, /prep, /recall) work the same way — close this folder and reopen it (or start a new chat) once, and they're all ready.

ai-os-setup-prompt.txt
Loading…

the one habit that makes it pay off: run /improve whenever you correct it — that's the loop that makes it more you.

Already set up? Pasting the prompt again upgrades in place — it detects your install and only adds what's new, leaving your memory, notes, and customizations untouched. Run /doctor anytime and it'll check whether you're on the current build.

before / after

The same week, two very different feelings.

Picture a normal Monday: back-to-back calls, a weekend's worth of unread mail, a status update due Friday, and the thing you promised someone you'd track. Hand that recurring overhead to an assistant that already knows your work — and watch the dots go green.

Without it● Overloaded
Status updates eat your Friday afternoon
No gap to prep between back-to-back calls
Monday inbox is a wall of weekend mail
Open items and follow-ups slip until something bites you
Project context lives only in your head
What gets stood up

Three parts, shaped to you.

The prompt interviews you about your role and your work first, then builds all three around what you actually do — not a generic template.

01 · Memory

A memory that stays true

Claude Code remembers across sessions — this keeps that memory honest: it re-checks what's gone stale, clears duplicates, resolves contradictions, and links related facts, so what it knows about your projects and people stays trustworthy instead of drifting.

02 · Vault

A structured notes vault

An Obsidian-style vault for projects, the people you work with, decisions, and reusable templates — status update, meeting notes, weekly review, 1:1 agenda.

03 · Commands

A toolkit of skills

Slash-commands you invoke by name — /brief, /prep, /triage, /weekly, /ingest — each wired to your mail & calendar.

Command reference

Your toolkit, in plain language.

Type a slash-command and it does the work — reading from a fast local cache of your mail & calendar, drafting locally, and sending nothing without your explicit OK.

Command
What it does
Try saying
/brief
Your morning brief — today's meetings and who's in them, what's waiting on you, top priorities, deadlines this week.
"/brief" → your whole day on one screen before the first call.
/triage
One pass over your inbox + calendar. Sorts mail into Needs Reply / FYI / Noise, flags conflicts. Read-only until you say otherwise.
"/triage my inbox" → Monday's backlog already sorted.
/prep
Preps you for one meeting — the invite, the mail thread, the relevant project & people notes, last decisions, open items. Hands you an agenda and likely questions.
"/prep my 2pm with the design team" → walk in ready.
/status
Drafts a status update from your notes + recent activity: what progressed, what's blocked, decisions needed, next steps. Polished or direct — your call.
"/status for <project>" → a draft you edit & send.
/weekly
Pre-builds your weekly review — what shipped, decisions, what slipped or is blocked, next week's shape — plus a ready-to-edit status update.
"/weekly" on Friday → review's already written.
/recall
"What do I know about X?" — one search across all your knowledge at once: your memory, your notes vault, and the work your other commands produce and keep (a tracked list, a strategy doc, research) — ranked together so none crowds out the others, with directly related facts pulled in. Answered with citations, and honest about where you have gaps.
"/recall what am I tracking on the website redesign" → everything you know, one answer.
The rest of your toolkit · 9 more commands
/wiki
Precedent search over your notes only — the deep dive into your vault, with citations to the exact note and heading. (Use /recall when you want both your memory and your notes at once.)
"/wiki the data-migration decision"
/improve
Turns a correction into a durable rule. Claude already jots down some corrections on its own — /improve makes the ones that matter stick deliberately, as a one-fact rule, so the system gets more "you" every time you steer it.
"/improve" after you fix its tone → it sticks.
/capture
The session write-back loop. At the end of a session that mattered, it distills what you decided into your notes and what you learned into your memory — routed to the right place, and it proposes the note before writing it. So a session's thinking compounds instead of evaporating.
"/capture" after a real decision → it's filed where you'll find it.
/ingest
Turns raw notes you drop in — clippings, transcripts, meeting exports — into maintained, linked concept pages you can navigate, instead of re-summarizing the same sources every time.
"/ingest my reading" → a living knowledge base, not a pile.
/board
Run a decision past a panel of advisor profiles — experts you admire, distilled into vault notes. Get each one's distinct take: where they agree, where they'd dissent, a recommendation.
"ask the board about this hire" → several sharp perspectives at once.
/teach
A stateful tutor for learning a topic over many sessions — keeps a syllabus and your progress, and picks up each time exactly where you left off.
"/teach me system design" → a course that remembers you.
/workflow-visualizer
Turns a system or process you describe into one interactive HTML diagram — clickable nodes, hover detail — you can open in a browser.
"diagram our release process" → a map, not a wall of text.
/backup
Protects your whole system — memory, notes, and your skills — against a lost or wiped machine. One command keeps an on-disk history and tucks an encrypted copy into the cloud folder you already sync (the 3-2-1 rule), no setup required.
"/backup" → a safe copy on disk and off your machine.
/restore
Brings it all back — after a new laptop, a bad edit, or a lost folder. Picks the newest snapshot, lays everything back, and is fully reversible. Use --drill to prove a backup works without touching your live system.
"/restore" → your system, back the way it was.
/doctor
A read-only checkup for your system — are your connectors still signed in, your memory and commands healthy, your last /backup recent? Reports what needs attention and points you at the fix; it changes nothing. Pairs with /backup — one tells you the safety net is current.
"/doctor" → one glance that everything's working.
/update
Fetches the current setup prompt, checks it's byte-exact, and hands it into this session as if you'd pasted it — the same safe upgrade mode you'd get by hand decides what actually changes, and nothing does without your OK.
"/update" → caught up, verified, on your say-so.
/gift
Give a capability you've proven to a friend — packaged as one de-personalized markdown file you can both read — and safely adopt one a friend sends you: it's reviewed out loud first and installs only after your explicit yes. No registry, no accounts, no tracking — a gift is just a file.
"my friend sent me this" → reviewed first, then it's yours.

Plus /memory-prune to keep your memory healthy, and /skill-center — a meta-command to build and refine new commands as your needs grow.

Want to go deeper? The Field Guide → walks through how to get the most from each command — plain-language up top, power-user depth below.

Operating controls

Built with guardrails.

Designed to be trustworthy from the first line. Three controls keep it fast, in your hands, and private.

✓ Private

Local — and recoverable

Your mail, calendar, and notes live only on your own machine — a hard "never goes outward" rule. The one thing that can leave is a backup you ask for: encrypted, into your own cloud, so your system survives a lost laptop without ever being exposed.

✓ In your hands

Read-only by default

Every command reads and drafts; nothing is sent, posted, accepted, or shared until you approve it. Approving one action is never standing approval for the next.

✓ Well-behaved

Local-first by design

It caches your calendar and mail and refreshes only when something changes — instant to use, and gentle enough on your mail and calendar service that it won't trip rate limits.

Check first: confirm with your leadership / IT that Claude Code with the Microsoft 365 or Google Workspace connector is approved for your account before wiring it to work mail. This is a personal-productivity setup — not an official product of any employer.
Yours vs. rented

A system you own — not a subscription you rent.

Most "AI second brain" tools are hosted apps: your notes live in their cloud, on their terms, for as long as you keep paying. An AI OS is the opposite — a free template you copy, run on tools you already use, and reshape to fit you. Here's the honest comparison.

✓ Yours to keep

A free, forkable artifact

Every tool below is a paid SaaS account you rent a seat in. This is a free copy-paste template — you can read it, reshape it, fork it, and pass it to a friend. There's no vendor to leave because there's no vendor.

✓ Plain files

Your memory is files, not a database

Your notes and memory are plain text files on your own machine — the store is the data. You can open, search, edit, and version them directly, with no export step and nothing trapped in a proprietary cloud database.1

AI OS Saner.ai Mem Tana Notion AI ChatGPT / Claude memory
Where it lives Notes & memory: local files on your machine. Model & connectors: cloud1 Cloud app Cloud app Cloud only (no offline) Cloud app Cloud, tied to your account
Your data's form Plain markdown — the store is the data; edit & search in place, no export step Proprietary cloud; export available Proprietary cloud; markdown export (clunky) Proprietary nodes; JSON/MD export, but lossy Proprietary blocks; full export Cloud summary you can view/edit + a data export — not files
Own & fork it Free template — fork, reshape, pass it on Rented seat Rented seat Rented seat Rented seat Rented seat
What it does on its own Reads & drafts; every outward action waits for your per-action OK — on by default, no mode to switch on (on M365 the connector is read-only outright) Drafts first; doesn't auto-send Notes & drafting assistant Knowledge workspace Agents act autonomously by default; approval (Plan Mode) is opt-in — (it's memory, not actions)
What it costs Free template — runs on the Claude plan you already pay for Paid subscription Paid subscription (free tier) Paid subscription (free tier) Paid seats + metered agent credits ($10 / 1,000, no rollover) Bundled in your ChatGPT / Claude subscription
Keeps memory healthy A maintenance loop you can run & audit: re-checks stale facts, clears duplicates, resolves contradictions, links related notes Auto-tags / organizes Auto-links related notes User-defined supertags Workspace knowledge (not a personal memory) Background synthesis + an editable summary; claims to reduce contradictions — but an opaque cloud summary, not files

1 Honest scope: your notes and memory are plain files on your own machine; the AI model and the mail/calendar connectors are cloud services you already use. An AI OS doesn't run offline, and we don't claim it does.
Every tool here lets you export your data — the real difference is that theirs lives in a cloud database you export from, while yours is already plain files you own. Competitor details are as-of July 2026; hosted-app features and pricing change often — check the source before relying on any cell.

When it’s earning its keep · let it run on a schedule

Once you trust it, let it run without you.

Setup already scheduled the quiet data refreshes that keep your commands instant — this is different: scheduling the brief itself, so it’s written and waiting when you sit down. When your /brief and /triage are part of your morning, the next step is to stop typing them. Claude’s desktop app can run a command for you on a schedule — a 7am brief waiting when you sit down — and because it runs on your machine in Ask mode, it still drafts and waits: anything it would send stalls for your OK, exactly like when you’re driving it yourself. Nothing is sent while you’re away.

Read this part — scheduling has real edges:
· It only runs while the app is open and your machine is awake. A sleeping laptop silently skips the run (it catches up on wake, maybe at an odd hour) — pick a time your computer is on.
· A green “done” doesn’t prove the brief worked. Open the run and read it.
· Every unattended run uses your Claude plan like a normal session — a daily brief is a recurring draw that can crowd a ~$20 Pro plan, so start with one task a few days a week and watch your usage.
Paste the prompt below and it walks you through setup and hands you the exact text to schedule.

scheduler-setup-prompt.txt
Loading…

the rule that keeps it safe: schedule it in Ask mode, and on the first “Run now” never click “always allow” on anything that sends — that’s what keeps it drafting instead of acting.

When you’re ready · staff your bench

Once it runs your week, hire it a manager.

Your AI OS runs your day. The next step is to hire a domain manager — a standing chief-of-staff for one part of your life that keeps its own strategy, does its own research, stages real work for you to approve, and gets sharper every time you correct it. Think of it the way you’d staff a small team: you’re the boss, you hire one manager at a time, and nothing they draft goes anywhere until you say so. It’s a bench of focused workspaces you open when you want them — not an autonomous army of bots.

Career Live today

Learns how you write and drafts LinkedIn posts in your voice; keeps a living strategy for where your career is headed. Read the full role, then open the career prompt below to hire it.

Projects Live today

Keeps a strategy, backlog, and decision log for a project you own — and drafts the weekly status you actually send. (It’s the same shape that runs this product.) Read the full role, then open the projects prompt below to hire it.

Finances Coming

Turns statements you paste in into a budget and a plain-language read on your money. It drafts and explains — it never moves a cent.

Learning Live today

Plans what’s worth learning across everything you’re trying to master — a prioritized, prerequisite-ordered roadmap — then hands each topic to your tutor (/teach). Read the full role, then open the learning prompt below to hire it.

Career, Projects and Learning are the three you can paste today. Finances is the same pattern, on the way — and because it’s all plain files you own, an expert can stand one up now by reusing the shape.

Hire the career manager Live today+

Read the full role → what it does, when to reach for it, the honest limits.

The career manager learns how you write from a few things you’ve written and drafts LinkedIn posts that sound like you, not generic AI. It won’t nail your voice from three samples — no tool does — so it gets it roughly right, shows you what it learned, and sharpens every time you edit a draft. You’re always the judge, and you do the posting — nothing is ever published for you.

career-manager-prompt.txt
Loading…

the loop that makes it you: every time you reword one of its drafts, run /career voice learn — it remembers the difference.

Hire the projects manager Live today+

Read the full role → what it does, when to reach for it, the honest limits.

The projects manager — the same STRATEGY / BACKLOG / DECISIONS shape that runs this very product. Paste it, answer a short interview about one project you own (its goal, who reads the status, how often you report), and it drafts the weekly status update you actually send — pulled from the plan, not written from scratch. You’re always the judge, and you do the sending — nothing is ever sent for you.

projects-manager-prompt.txt
Loading…

once it’s running, type /projects update anytime and it drafts your next status from where things actually stand.

Hire the learning manager Live today+

Read the full role → what it does, when to reach for it, the honest limits.

The learning manager — the same STRATEGY / BACKLOG / DECISIONS shape, pointed at everything you’re trying to learn. Answer a short interview about your goals and it drafts a prioritized, prerequisite-ordered roadmap — what to learn, in what order, and where to start — then hands each topic to /teach, the tutor that already ships with your AI OS. It plans; /teach teaches. No connector, nothing to send — just a standing strategist that stops you learning at random.

learning-manager-prompt.txt
Loading…

once it’s running, type /learning review anytime and it tells you which topics have gone cold and are worth revisiting.

Questions

Before you start.

Do I need to be technical?+
No. You install one app and paste one prompt. The interview is a normal conversation, and Claude explains each thing it builds in plain language. If you can use email and a calendar, you can use this.
What does it cost?+
This setup is free, and so is the toolkit it builds. The one cost is Claude Code itself, which runs on a paid Claude plan — Pro is about $20/month. The template is free; the AI that powers it isn’t.
What data does it touch?+
Your mail and calendar — Microsoft 365 or Google Workspace — read through the connector you authorize. It keeps a local cache on your own machine for speed, and treats anything you mark confidential as something that never leaves your machine without your explicit approval.
Will it email or message people on its own?+
No. It's read-only by default. It drafts replies, updates, and prep locally and shows them to you; nothing is sent, posted, or accepted until you say so — every time.
Do I need approval to use it?+
If you're connecting a work account, check with your leadership / IT that Claude Code with the Microsoft 365 or Google connector is approved first. Treat this as a personal-productivity setup, not an official product of any employer.
How is it different from just chatting with an AI?+
Two things: a memory it actively keeps true — it learns your projects and people across sessions, then re-checks what's gone stale, clears duplicates, and resolves contradictions so it doesn't drift — and commands wired to your real mail & calendar. Instead of re-explaining your context every time, you say "/prep my 2pm" and it already knows the players, the history, and what's open.
What if it gets something wrong?+
Correct it, then run /improve to lock that lesson in as a durable rule, so it won't repeat the mistake. The more you steer it, the more it works the way you do.
Can I customise the commands?+
Yes — run /skill-center to add, edit, or audit commands as your needs change. The starter set is just a foundation.
I already set this up — how do I update it?+
Just say /update — it fetches the latest setup prompt, checks it's genuine, and hands off to upgrade mode: it adds only the commands and improvements that are new since your build and leaves your memory, notes, CLAUDE.md, and any commands you've customized untouched — it shows you what it would add and waits for your OK before changing anything. Don't have /update yet (a very old install)? Paste the setup prompt again by hand — same safe upgrade mode, no code to run. Not sure whether you're behind? Run /doctor — it'll check your build against the current one and point you at the fix.