Windows. Claude Code. Your own files.
You installed Claude Code. This is what to use it for.
MYOS is an operating system for your life and work: a structured folder of plain files on your PC, and an assistant that reads and writes them when you talk to it. It runs itself. It does not wait for you to fill it in.
Every other system of this kind is an empty database you populate by hand. This one arrives with the structure already made, the workflow already tested, and an assistant already configured to keep it current.
Before you buy anything: Windows 10 or 11, your own paid Claude plan (Pro or above, about US$20 a month, paid to Anthropic and not to us), and about half an hour. The free setup guide below proves all three on your machine before any money changes hands.
Checkout opens soon.
Leave your email and you hear the moment it does, the price stays US$500, and we do nothing else with the address.
The full Windows setup guide is on this page, free. It stands alone, it works whether or not you ever buy, and it ends with a working Claude Code on your machine.
Start here
One question decides which path you read. A wrong answer costs nothing: both doors end at the same setup line, and it skips whatever you already have.
Do you already have Claude Code running on this Windows PC?
Your answer from last time is selected.
Then you are the person this was built for, and most of this page is written for someone standing further back. Take the fast lane: what MYOS is, the ninety seconds you still spend, and the line that drops it into the Claude window you already have open.
Then start from the beginning. The setup guide installs Git for Windows, Claude Code and Obsidian for you, walks you through signing in, and stops when your machine is ready.
You do not need to know PowerShell. You copy one line, paste it, and read what it tells you. Go to the free setup guide.
The fast lane
What a Claude Code for non-coding work looks like
You already have Claude Code running, so the install walkthrough below is not your problem: finding something worth pointing it at is.
MYOS is the thing to point it at. A structured folder of plain files on your PC, and an assistant already configured to read and write them while you talk. Every other system of this kind is an empty database you fill in by hand. This one arrives with the structure made, the workflow tested and the assistant already told how to keep it current: a second brain that runs itself, rather than one more thing you maintain.
People who already have Claude Code tend to describe the same gap two ways. It forgets everything between sessions, so every conversation starts from scratch. And it is so much tool for the job in front of it that it feels like driving a Ferrari to pick up the groceries. MYOS answers both with one thing: somewhere for everything it learns to live, and a standing job to do with it.
The ninety seconds you still spend
One line, once, in PowerShell. On a machine that already has everything it takes about ninety seconds: it checks what is present, skips it, installs anything missing, and proves your Claude plan can actually run Claude Code, which is the thing that quietly stops people later. That line is step 2 of the free guide. Nothing before it applies to you.
After that you stay in Claude
You do not go back to a terminal. Buying sends you a receipt with one plain-English line in it, and that line goes into the Claude window you already have open:
Fetch https://learnmyos.com/setup/your-order-link and follow it exactly to install my MYOS vault.
PLACEHOLDER: that address is not live yet, and the link shown is illustrative because each order gets its own. The line itself, and the helper that makes it work even if you paste it into PowerShell by mistake, are built and tested. Hosting them at a real address is a separate step.
Claude reads the instructions at the other end, installs the vault, explains each prompt before it appears, restarts itself inside your new vault and starts asking you about your work. You answer in your own words. You never write code and you never edit a configuration file.
The rest of this page is the long version: what you need, the free guide, what is in the box, the price and the questions.
What you need
Stated plainly, because buying without these means it will not run.
- A Windows 10 or Windows 11 PC. MYOS is Windows only. There is no Mac or Linux version, and there is a waitlist page instead of a promise.
- Your own paid Claude plan, Pro or above. About US$20 a month, paid to Anthropic, not to us, and not included in the price. The free plan cannot run Claude Code, and the setup script stops and tells you so rather than letting you find out after paying.
- Git for Windows and Obsidian. Both free. The setup script installs them. Obsidian is free to use, including for work.
- Permission to install software on the machine. A locked-down work laptop is the most common reason an install fails.
- About half an hour for setup and the first conversation with your assistant.
The free setup guide below checks every one of these and ends on a READY banner. Finish it first. It costs nothing and it proves your machine works before you spend anything.
Free, complete, no purchase
Set up Claude Code on Windows
This is the whole thing. It installs what Claude Code needs, gets you signed in, and proves your plan works. Nothing here mentions payment and nothing here expires.
Step 1: open PowerShell
Press the Windows key, type PowerShell, and press Enter. A black window opens. That is the only window you need.
Step 2: paste one line
Copy this, paste it into the black window, and press Enter.
irm https://learnmyos.com/get-ready.ps1 | iex
PLACEHOLDER: this address is not live yet. The script exists and is tested; hosting it at this address is a separate step, so the line above cannot work from this draft.
It will ask Windows for permission a couple of times along the way. Say yes. Here is what it does, in order:
- Checks your Windows version and free disk space.
- Installs Git for Windows, Claude Code and Obsidian, skipping anything already present.
- Repairs
%USERPROFILE%\.local\binon your PATH, and refreshes the PATH in the window you are standing in, soclaudeworks there rather than only in the next window you open. - Writes a small helper so that a link you are sent later works whether you paste it into PowerShell or into Claude.
- Walks you through signing in to your Claude account.
- Proves your Claude plan can actually run Claude Code, by asking it a real question and reading the answer.
- Prints a READY banner.
It is safe to run again. It picks up where it stopped and never repeats work it already did.
Step 3: sign in when it asks
A browser window opens for you to sign in to your Claude account. Do that, then come back to the black window.
If your account is on the free plan, the script stops here and says so. You need Pro or above, at about US$20 a month from Anthropic. Upgrade, run the same line again, and nothing you have done is lost.
Step 4: the trust question
The first time you type claude, it asks whether you trust the files in the folder you are in. That is your own home folder on your own computer, so yes is the right answer.
You will meet this question exactly twice in the whole journey: once here, and once later for your vault, if you buy. It is Claude Code asking whether it may use the settings that came inside that folder. It applies to that one folder and nothing else on your computer.
Step 5: read the banner
When it finishes, you get this:
############################################
# #
# READY #
# Your machine is ready for MYOS. #
# #
############################################
Everything MYOS needs is installed, and your Claude account works.
That was the fiddly part, and it is behind you!
That is the free part done. You now have Git, Claude Code and Obsidian installed, your PATH repaired, and a Claude plan proven to work. You can type claude in that window right now and start a session.
If it says NOT READY
The banner names the item marked PROBLEM. Fix that one thing, then run the same line again. Re-running is safe.
A record of the whole run is written to %LOCALAPPDATA%\MYOS\install.log. If you are stuck, the rescue page has the read-only check to run and what every message means.
Target 1200 x 700, taken on a clean Windows 11 machine, not on a personal vault.
Where the free part ends and MYOS begins
What you have now is a very capable assistant standing in an empty folder. It remembers nothing between sessions, it knows nothing about your work, and every conversation starts from scratch. That is not a criticism of Claude Code. It is what a general tool is.
People who get here usually do the same thing next. They make a folder, invent some structure, write a few instruction files, use it for a fortnight, and quietly stop, because keeping the structure alive turns out to be a second job.
MYOS is that work already done and used long enough to know which parts survive. A place for everything, a loop that runs the same way on day one and in year three, and an assistant configured to file, summarise and remember on your behalf. You talk. It writes.
The reading is free too. Learn MYOS explains the whole framework before you spend anything: what the pieces are, why each one exists, and what it honestly does not do.
Before you buy: Windows 10 or 11, your own paid Claude plan (Pro or above, about US$20 a month to Anthropic), and about half an hour. If you cannot get it running, we refund you in full.
Checkout opens soon.
Leave your email and you hear the moment it does, the price stays US$500, and we do nothing else with the address.
Watch it happen
60 to 90 seconds, recorded on a clean machine, showing the real paste line and ending on the assistant saying hello inside a new vault. Not recorded yet, so nothing is embedded here. No stock footage stands in for it.
What you get
Files, on your machine, that you own. Here is what is in the box and what each part is for.
1. The vault
A structured folder: your work streams in Areas/, your live and finished work in _Tasks/Active/ and _Tasks/Archive/, your profile, your inbox, and the structural rules in _System/. Everything has a home from the first minute, so nothing you say has nowhere to go.
2. The assistant configuration
The instruction file your assistant reads at the start of every session, a permission set that lets it write your notes without asking and stops it before it runs commands, and a status line so you can see what it is doing. Your assistant behaves the same way every session without you re-explaining anything.
3. The working crew
Twelve specialist agents, seventeen skills and six commands, already wired in: research, scoping, planning, building, reviewing, linting, cleanup, and the archiving pass that folds finished work back into the right files. You never call them by name. You say what you want, and the routing happens.
4. The onboarding and the nine-task tutorial
Your assistant interviews you, personalises the vault, and then walks you through nine tasks that teach the system by using it on your real work: Claude Code basics, how your assistant works for you, telling it about you, the task system, areas, Obsidian, connecting your tools, meeting debriefs and hooks, and finishing your first real task. You finish with a system that already has your work in it.
5. The rules that keep it consistent
The structural model, the writing conventions and the templates your assistant follows. This is why a vault with three years of material in it is still readable, and why files written in month twenty look like files written in week one.
What version you get, and what happens after
You buy the kit as it is today. It carries a version marker, it is yours at that version, and nothing lands in your vault on its own afterwards.
If we find a defect in what you bought, or improve the framework itself, that fix is free to you. Fixing something that is broken is part of honouring the sale, not a new product: there is no paid upgrade to get a bug fixed and nothing to keep paying to stay current. What we will not do is push changes at you or write over anything you have customised.
From there you extend it by talking to your assistant, which is the point of the product rather than a limitation of it: Growing your system explains what that looks like.
What people who ran it say
Three to five named quotes from the stranger beta cohort, each with written permission on file, each naming what the person actually does. No quote goes here until the cohort has run and permission is recorded. Nothing is written for them in the meantime.
PLACEHOLDER 1: quote, name, one line about their work.
PLACEHOLDER 2: quote, name, one line about their work.
PLACEHOLDER 3: quote, name, one line about their work.
Price
US$500
One payment. No subscription, no login, no account to keep alive. What you end up with is a folder of plain text files on your own machine, which is the least fragile format there is: they open in anything, they are still readable in ten years, and they keep working whether or not we do.
The free alternatives, named
They exist and they are one search away, so here they are. There is claude-obsidian on GitHub, MIT licensed and actively maintained. There is second-brain-starter. There are free vault templates on GitHub, a free second-brain starter kit on Gumroad, and good free tutorials on wiring Obsidian to Claude.
If you want to assemble your own system, start with those. They are genuinely useful and they cost nothing.
What you are paying for here is not files you could not get. It is the decisions: which structure survives contact with real work, what the assistant should be told, what the loop is, what to do when a task finishes, and what happens automatically so the thing does not rot. Those took six months of daily use to settle. The free repos hand you a shape. This hands you a system that already runs.
What it is not
There is no video course, no community, and no membership. Most things at this price include at least one of those. This one is a working system plus an assistant that teaches you as you use it, and if the teaching is the part you would be paying for, read Learn MYOS first and judge it there for free.
If you cannot get it running, we refund you in full
Write to us and tell us it will not run. Give us a fair chance to help, which usually means answering a couple of emails and, if you are willing, sending the install log from your own machine. If we still cannot get it running, you get the full US$500 back.
We honour this even when the cause is on your side. A work laptop that blocks scripts, antivirus that quarantines the download, a network that will not pass the file: all of those count. The promise is about the outcome, not about whose fault it is.
This is added on top of the rights the law already gives you. It does not replace them or limit them.
Before you buy: Windows 10 or 11, your own paid Claude plan (Pro or above, about US$20 a month to Anthropic, not included), Git for Windows and Obsidian (both free, installed for you), and permission to install software on the machine.
Checkout opens soon.
Leave your email and you hear the moment it does, the price stays US$500, and we do nothing else with the address.
What this does on your computer
Read this before you buy rather than after. It is the part most products leave out.
What your assistant may do without asking
It writes and edits files inside your vault without asking each time. That is the whole point of the system, and it is confined to your vault.
Running commands is different. Every time it wants to run something in a terminal, it shows you the command and waits for you to approve or deny it. That stays on until you decide otherwise.
When you are comfortable, you can tell it to stop asking, and it will widen its own settings after telling you plainly what that means. Claude Code also has a middle path built in: when a prompt appears, one of the options stops the asking for that one kind of action. There is a mode that turns permission checks off entirely. MYOS never uses it and never asks you to.
What leaves your machine
Your files sit on your disk. There is no MYOS account, no MYOS server, and nobody receives a copy of your vault because you installed it.
What does leave is the conversation. When you talk to your assistant, the parts of your files it reads go to Anthropic as part of that conversation, exactly as they would in any Claude session. That is the honest boundary, and it is worth knowing before you write something sensitive into a file and then ask about it.
The one thing we can be sent, only if you say yes
After an install, your assistant may offer once to send us a one-line note about how it went. It contains five things: the order number, whether it worked, which step it reached, any error code, and your Windows version. Nothing from inside your vault, nothing else, and never without you agreeing. Say no and it moves on.
Where the vault goes
Into Documents\MYOS-Vault. If your Documents folder is inside OneDrive, it goes to %USERPROFILE%\MYOS-Vault instead and tells you so on screen, because a folder that keeps its own history every fifteen minutes and a sync client that keeps its own copy of everything will fight, and the fight shows up as mangled files a week later. You can override that and put it wherever you want.
Your existing files are not touched
If there is already something where the vault goes and this machine has no record of putting it there, the install stops and asks you. It never writes over a folder on its own initiative. Nothing is deleted by any path.
Support, and who is answering
Support is by email and covers getting the kit installed and running, how the system works, and anything that looks like a defect. It does not cover building custom workflows for you, business advice, or support for Claude Code, Obsidian or Windows themselves.
Replies are drafted with the help of an AI assistant and say so. Anything about refunds, the guarantee or pricing is answered by a person.
Questions
I know literally nothing about coding. Can I actually do this?
Yes, and the design assumes it. You copy one line into a window and press Enter. After that you are talking, not typing commands: your assistant runs everything and explains each prompt before it appears. You never write code and you never edit a configuration file. If a prompt confuses you, ask your assistant what it means, in the same window, in your own words.
Do I have to have a paid plan? I got it all installed before anyone mentioned that.
Yes: Pro or above, about US$20 a month, paid to Anthropic and not to us. It is the most common nasty surprise in this whole area, so the free setup line checks it for you before you spend anything here. It asks your account a real question, reads the answer, and stops with a plain explanation if the plan cannot run Claude Code. Upgrade, run the same line again, and nothing you have already done is lost.
It runs, it looks scary, and sometimes nothing appears to happen. Is that normal?
Mostly, yes. Installing three pieces of software takes a few minutes and some of that time looks like a still screen. The setup narrates itself as it goes, so you always have a "Step 3 of 8" line telling you where you are, and it writes a full record to %LOCALAPPDATA%\MYOS\install.log as it runs. If it genuinely stops, it prints a block marked PROBLEM saying what happened and what to do, and running the same line again is safe: it keeps everything that already worked and carries on.
Watching my machine run a script I do not understand is unnerving. What is it doing?
Fair, and worth answering rather than brushing off. The setup script is a plain text file at a fixed address: you can open that address in your browser and read the whole thing before you run anything, and it is the same file for everyone. It installs Git, Claude Code and Obsidian through Windows' own app installer, or straight from the people who make them if this machine does not have that, then fixes your PATH, walks you through signing in and checks your plan. It deletes nothing, it touches no file of yours, and the record of what it did stays on your machine. Later on, when your assistant wants to run a command, it shows you the command and waits for you to say yes.
I already use Claude Code. Will this get in the way?
No. The setup detects what you already have and skips it, and the vault's own settings only apply inside the vault folder. Your existing setup and any other project you have configured are left alone.
Do I have to learn Obsidian? Is it free, even for work?
It is free, including for work use, and it is not really for you to work in: it is the window you read your vault through. The writing happens on the other side, by your assistant, while you talk to it.
Do I need to know git?
No. Your vault can keep its own history so a bad edit is a two minute fix instead of a bad afternoon. Your assistant sets that up and uses it. You never type a git command unless you want to.
Does my data leave my computer?
MYOS adds no new party. There is no MYOS account and no MYOS server, and nothing from your vault is sent to us because you installed it. Your files sit on your own disk. What goes to Anthropic is the conversation, exactly as it does in the Claude sessions you already have, so if you are already using Claude Code this changes nothing about where your words go. The one exception is deliberate and small: after an install your assistant offers once to send us a five-field note about how it went, and it only sends it if you say yes.
I already have an Obsidian vault. What happens to it?
Nothing, unless you ask. The install goes to its own folder, and if it finds files it did not put there it stops and asks you rather than writing over them. Moving your existing notes in afterwards is a conversation with your assistant, not a migration tool.
Will this eat my Claude plan allowance?
The first session is a busy one: the interview, the setup and a nine-task tutorial. We have not measured that consumption on a Pro plan carefully enough to publish a number, so we are not going to claim one. What we will say is that hitting a limit is not a disaster: the work is written into files as it goes, so a new session picks up where the last one stopped.
Mac? Linux?
Neither, today. The installer is Windows-only and everything here is tested on Windows 10 and 11. There is a waitlist rather than a date.
Is this a course? Is there a community?
No and no. There are no videos, no cohort, no forum and no membership. What replaces them is an assistant that teaches you the system while you use it on your own work, and a public explanation of the whole framework you can read before you buy.
There are cheaper Claude Code templates that do this. Why this one?
Some of them are good, and the free ones are named further up this page. The honest difference is where each one starts. A template hands you a folder of files and assumes the hard part already happened: that you are someone who can get Claude Code installed on Windows, sign in, work out for yourself that the free plan will not run it, and repair your own PATH when the command is not recognised. That assumption is exactly where people fall over. Here that part is the free guide on this page, and you run it before you have paid anything, so you either finish on a READY banner or you find out on our time instead of after buying.
Two other differences, stated plainly. What you end up with is plain text files rather than rows in a database, so it opens in anything and it stays readable no matter what happens to us. And the onboarding teaches instead of configuring: nine tasks on your own real work, so you finish able to change the system yourself rather than owning a setup you cannot safely touch.
What if I get stuck?
Four things, in order. The assistant on your own machine can see the actual error and diagnose it. There is a read-only check that prints a status table you can paste into an email. There is a rescue page that explains every message the installer can produce. And there is email support. If none of that gets it running, the refund is the rescue.
Can I share it with my team?
One purchase covers one person. Everything you create in your vault is yours, and the kit's own files are not for reselling, republishing or passing on.
What happens when the kit improves? Do I have to buy it again?
No. You own what you bought, at the version you bought, and defect fixes and framework improvements to it are free: fixing something that is broken is part of the sale rather than a new product. Nothing lands in your vault overnight and nothing you customised gets overwritten by someone else's improvement. Your upgrades are the changes you make and keep.
If you cannot get it running, we refund you in full
Finish the free setup guide first. It proves your machine and your Claude plan work, and it costs nothing. If you buy after that and still cannot get it running, tell us and take your money back.
Before you buy: Windows 10 or 11, your own paid Claude plan (Pro or above, about US$20 a month to Anthropic), and about half an hour.
Checkout opens soon.
Leave your email and you hear the moment it does, the price stays US$500, and we do nothing else with the address.