Open-source • local-first • persistent AI on your machine
Turn Codex into persistent creatures that can actually do things.
CreatureOS gives Codex memory, purpose, worklists, and teachable habits so it can keep operating across real work instead of starting over every chat.
What creatures can do
Concrete work, not another abstract AI promise.
CreatureOS is for work that keeps coming back: drafts that need another pass, servers that need another audit, research that needs continuity, and open threads that should still matter tomorrow.
> ask the writer creature to tighten chapter 3
→ rewrites for clarity and rhythm
> ask the ops creature to audit server security
→ checks configs, flags risks, proposes fixes
> ask the social creature to post on X for you
→ drafts, edits, and posts from your machine
> return tomorrow
→ creature remembers context, open threads, and next actionsCopy-edit a book chapter
Hand a creature a draft, let it tighten rhythm and clarity, and keep the next revision alive.
Audit repo or server configs
Let a creature inspect the environment, flag risks, and come back with a concrete follow-up list.
Post on social media for you
Let a creature draft, revise, and post on platforms like X from the actual machine where your tools live.
Keep an ongoing worklist alive
Purpose, memory, and worklists survive past one session so the work does not reset every day.
Organize long-running research
Creatures can keep track of sources, open questions, and the next useful thread to pull.
Remember unresolved threads
When you come back later, the creature is still carrying the unfinished shape of the work.
Why blank-slate chat breaks down
One-off prompting is fine for a trick. CreatureOS is for continuity.
Normal chat resets context. Rigid automation breaks when the work changes. CreatureOS is built for the messy middle where memory, judgment, and repeated contact with the real environment actually matter.
Context keeps collapsing.
You rebuild the same background, decisions, and unresolved threads every time you come back.
Memory and worklists stay alive.
A creature keeps its purpose, memory, chats, and active work instead of starting from zero again.
The script breaks as soon as reality shifts.
Static rules work until the task changes shape, then they become another thing you have to babysit.
Recurring work grows out of use.
CreatureOS lets habits emerge from conversation so they can be shaped before they get trusted.
More helpers is not the same as better help.
Without judgment, you just collect overlapping assistants with vague responsibilities.
The habitat gets shaped carefully.
The Keeper helps decide whether another creature should exist at all and whether the current ones are serving you well.
How CreatureOS works
One creature at a time. Purpose first. Habits only when they are earned.
Begin with the Keeper
The Keeper reads the shape of the work, notices what kind of help is actually missing, and resists needless complexity.
Summon a creature with a reason to exist
Each creature arrives with purpose, memory, chats, and a live worklist tied to the job it is there to do.
Teach habits as trust builds
Recurring work becomes a habit only after the creature understands the trigger, the method, and what success looks like.
Why this feels different
CreatureOS is designed to stay useful after the first impressive moment.
Persistent memory
Creatures remember decisions, constraints, preferences, and open threads instead of making you restate them.
Work with a reason to exist
Each creature is grounded in a clear role in the habitat instead of drifting into generic assistant behavior.
Teachable repetition
Repeated work can become a habit without getting frozen into brittle automation too early.
The Keeper decides carefully
New creatures are summoned conservatively, with a stronger bias toward usefulness than spectacle.
Close to the real machine
The runtime lives near your files, tools, repos, and browser flows instead of floating above them as a SaaS abstraction.
Private phone access
Run CreatureOS on your computer and still reach it privately from your phone over Tailscale.
Install
Make the install path obvious, fast, and hard to mess up.
CreatureOS is easiest to install by asking Codex to do the whole thing for you. If something is missing, that same prompt can usually fix it.
Install Codex
Get the app or CLI at chatgpt.com/codex/get-started.
Give Codex full access
That lets Codex install packages, fix problems, and start the habitat without hand-holding.
Paste the command
Codex can install CreatureOS, troubleshoot any issues, and get the server up for you.
Paste into Codex
install creatureos using pip and spin it up, troubleshoot any issuesConnect from your phone
Run CreatureOS on your computer, then reach it privately from your phone.
The usual path is creatureos serve --tailscale on the computer, with Tailscale installed on both the computer and the phone.
- Run
creatureos serve --tailscaleon the machine hosting CreatureOS. - Install Tailscale on both the computer and your phone.
- Open the Tailscale CreatureOS URL from your phone and you are in.
Ask Codex to guide it
please give me exact instructions on how to connect to this on my phone using Tailscale on this device and my phoneSupport
If you want this kind of AI future to exist, help keep CreatureOS alive.
CreatureOS is being built openly and iteratively. Donations help keep the habitat independent, local-first, and still moving.