YOUR SECOND BRAIN JUST GOT HANDS
PLAIN WORDS
Stead is a set of Claude Code workspaces for your life, laid out and fitted for you. Each room is a workspace with its own CLAUDE.md, its own starter pack of skills, its own routines, and a custom interview that populates it with your context. An agent team works in each room under rules you write: a lead you talk to, specialists it convenes for the hard reads. Each workspace keeps its own memory behind its own walls; what crosses a wall is explicit and read-only. It's all files on your disk. If you run Claude Code, you can run Stead: no app, no cloud, no new account beyond the Claude one you already have.
An agentic OS for your life.
Walled rooms for the pillars of your life. An agent team in each, acting in your stead, under rules you write. A house that remembers. Everything on your disk, forever yours.
Download the Command Centre
MACOS (APPLE SILICON) · IT RAISES YOUR STEAD ON FIRST LAUNCH · SIGNED AND NOTARIZED · OPEN SOURCE (MIT)OR IN THE TERMINAL$ npm create steadNODE 18+ · YOUR OWN PAID CLAUDE PLAN · CROSS-PLATFORM · NOTHING PHONES HOME
STEAD COMMAND CENTRE · LOCALHOST:4377DAY 44
FIVE WORKSPACES · ONE INTERVIEW EACH
Five workspaces that shape you.
HEALTH
Workouts, sleep, markers, symptoms. A check-in drafted every Sunday against your actual goals.
CAREER
Notes, wins, scope cuts, priorities. A week map every Monday morning, three priorities deep.
FINANCE
Bills, renewals, rate changes, decisions. A ledger review every Friday, dues and renewals up top.
PERSONAL
Your people, your interests, you. The week ahead drafted Sunday, dated things first.
PROJECTS
Ideas, momentum, working notes. A pulse per project every Friday: moved, stalled, next.
Each workspace opens with an interview. It asks about your goals, your constraints, your schedule, and your people, and writes the workspace around the answers. That context is why the agent can work on your actual problems instead of generic ones.
The interview is also where goals get set, and it pushes for realistic ones: targets that survive a travel week, cadences that match your real schedule. You can re-run it any time your life changes.
THE INTERVIEW · HEALTH
What does a good week look like, honestly?
Three workouts. Asleep by 11 most nights.
What usually derails it?
Travel weeks. Late meetings.
CONTEXT SET · goals that survive a travel week, a check-in that knows your derailers, and a rule in your words: "Observe everything, prescribe nothing."
THE TEAMS · THE SKILLS · THE DOORS
Every workspace ships staffed.
Pick a workspace. Each one carries an agent team, a lead persona you talk to plus specialists it convenes for the hard reads, standing on a pack of skills shaped to its life: accredited knowledge to draw on, actions that do real work, and a conduct floor that holds every answer. That's the head start over a blank setup: nothing to configure, everything to grow by your own hand.
MEMORY · YOUR SECOND BRAIN
The second brain, built in.
Every workspace remembers what happens inside it: decisions you made, facts about your life, preferences you stated, corrections you issued. It builds itself as you live, and it answers when you ask. The structure underneath is the privacy story.
EACH ROOM REMEMBERS ITS OWN
Every workspace keeps its own memory behind its own wall. Health data physically lives in the health workspace; siblings don't read each other unless you grant a named, read-only exception you can see in config.
THE HOUSE STILL ANSWERS
The home reads across the constellation for the morning briefing and the weekly review, scoped to you alone. "What did we decide about the insurance?" comes back months later with its history attached.
A CURTAIN FOR THE SENSITIVE
Mark something curtained and the house's cross-reads won't surface it into mixed contexts; notes derived from it inherit the curtain. The wall is structure, the curtain sits on top, and neither depends on a prompt behaving.
ON YOUR DISK, INSPECTABLE
All of it lives on your computer; nothing is uploaded, ever. The Observatory shows you exactly what each room knows, and you can explain your own walls and grants by reading config, not documentation.
THE INCUBATOR · GENESIS
Ideas get a nursery. The real ones get a house.
The projects workspace is the incubator. Every idea keeps a dossier from its first spark: the decisions, the artifacts, the memories, all tagged to it from day one. So when an idea becomes real, graduation is cheap: the house buds it into a workspace of its own, memories swept in, with the same verb the installer used to raise your first five rooms.
SPARK
Frictionless capture, zero ceremony. The front door for any idea.
NURTURE
Sparks accrete. The room resurfaces the cooling ones instead of letting them die in a note.
EXPLORE
The research scout does the legwork; the reality-check gives honest odds. One finds, one refutes.
DECIDE
Pursue, park, or kill. Parked and killed are honest outcomes. The incubator recommends; you decide.
GRADUATE
The idea buds into its own workspace, born staffed: skills, vault, memories swept in, and a practitioner team drawn by what the project is. A star joins the constellation.
What the new workspace wakes with depends on what the project is. Ship software and it's born with an architect-led product team, from full-stack to marketing. Renovate a house and it's born with a construction crew that knows where the hard stops are and never plays inspector. Start a craft bench and it's born with a guru and a planner. Three seed teams ship in the box today, each standing on its own graded knowledge and its own conduct floor, and the skill shelf is where the long tail grows.
A graduated workspace stays tethered to the house, in the briefing's view and fed by its updates, until you cut the tether. Detach is first-class: the workspace keeps working, because it never depended on the house to function.
ROUTINES · THE ACTIVITY FEED
It works while you sleep.
Every room ships routines: workflows on a clock that fire on their own and leave the result on your desk. You wake up to drafts and decisions, never to something already sent.
ROUTINES · WHAT RUNS ON ITS OWN
starter-monday-map WEEKLY
CAREER · Drafts the week ahead as three priorities, each tied to a goal on the wall.
starter-friday-ledger WEEKLY
FINANCE · The Friday ledger review: dues, renewals, and drift, surfaced before they surprise you.
starter-sunday-checkin WEEKLY
HEALTH · The Sunday check-in drafted against your actual goals, derailers included.
starter-week-ahead WEEKLY
PERSONAL · The week ahead drafted Sunday, dated things first, from what the room knows.
starter-project-pulse WEEKLY
PROJECTS · A pulse per incubated idea: moved, stalled, cooling, next.
01
Week mapped overnight, review season is priority one
CAREER · 06:25 · routine:starter-monday-map
RAN
02
Insurance renews Jul 1 at 217 monthly, keep it or shop it
FINANCE · 06:28 · waiting on you
DECIDE
03
Sunday check-in ran, best week this month
HEALTH · Sun 19:15 · routine:starter-sunday-checkin
RAN
04
You authored a skill, prep-one-on-one, first by your own hand
CAREER · day 30 of your stead
YOURS
That feed is the whole point. Work happened while you weren't there, and you can read exactly what, who did it, and what's waiting on you. Nothing ships without your word.
GUARDRAILS
Guardrails, built in.
An agent with real access is never harmless, and Stead doesn't pretend otherwise. What it adds on top of Claude Code's permission model is structural guardrails: limits that hold because of how the system is built, not because a prompt asked nicely.
"Draft anything you like. Send nothing, spend nothing, delete nothing without my word."
AN APPROVAL RULE · WRITTEN BY ITS OWNER · HELD EVERY RUN
01
ISOLATED WORKSPACES
Each agent works inside its own workspace and sees nothing else. Health can't read finance; finance can't reach career. A mistake in one workspace stays in one workspace.
02
DESTRUCTIVE OPERATIONS ARE SCRIPT-ONLY
The agent never deletes or overwrites by hand. Those operations live in deterministic scripts that refuse on conflict, and there's no force flag for anyone to find.
03
EVERY WIPE ARCHIVES FIRST
Before any reset, the entire workspace is archived, unconditionally, and your notes and artifacts survive in place. The worst case is recoverable.
04
THE DASHBOARD IS READ-ONLY
The Observatory renders state; it can't change it. There's no button to act through, for the agent or anyone else.
THE STEAD SCHOOL
It's a lot at first. The room moves with you.
Stead is free and complete. What's taught is the path through it. A full house is a big thing to stand up alone: five rooms, a memory, skills and routines, and the night you install it, that can feel like a lot. The school is the sequenced way through, module by module, from the machine itself to a week that runs on its own.
And you don't do it by yourself. The community carries the room, people who started exactly as far behind as you did, so the proof that this works is the person beside you, not a founder with a perfect setup. It's the guided path through the whole thing, with people walking it alongside you.
You map what's in your house and land a real win before the lesson is over.
MODULE 1 · FIRST BOOT
You hand-write the context that turns a generic room into one that knows you.
MODULE 2 · SKILLS
The briefing you give three times becomes a skill you run cold.
MODULE 5 · ROUTINES
Work goes on a schedule and the week starts arriving on your desk.
MODULE 8 · THE SELF-RUNNING WEEK
The capstone you designed: it holds itself together and only wakes you when it should.
ONE LINE IN A TERMINAL, OR ONE DOWNLOAD
Install yours tonight.
Five rooms, every lamp lit, an agent team in each, under rules you write. On your disk, forever yours.
$ npm create steadDOWNLOAD THE COMMAND CENTRETHE APP RAISES YOUR STEAD ON FIRST LAUNCH · BUILT LOCALLY FROM ITS BUNDLED KERNEL · MACOS (APPLE SILICON) · SIGNED AND NOTARIZED