Step 1
Tell BuildOS what you're making.
Start with rough notes or a message.
Swipe the screenshot to read the full example →
For creators with too much in their head
A project workspace you can talk to.
Paste your rough notes or tell BuildOS what you’re working on. It organizes the pieces into tasks, documents, and next steps. Tell it what changes as you go.
Start a project
One message in. A working project out.
BuildOS creates the structure while you watch, then gives you a project you can keep using.
Real BuildOS screenshots · example book project
Step 2
BuildOS creates the structure.
Tasks, goals, and docs appear as it works.
Swipe the screenshot to follow each action →
Step 3
Keep working outside the chat.
Open the project, make changes, and pick up where you left off.
Swipe to explore the project →
Open the tasks and documents your conversation created.
Real changes, made in chat
Tell it what changed. See the project update.
BuildOS finds the right item, makes the change, and shows you what moved.
Real BuildOS screenshots · example book project
Update a task
Move something on your calendar
Every change stays attached to the project.
Come back to the same project
Pick up your project without piecing it back together.
Your notes, tasks, and decisions stay with the project. Open it, review where you left off, and choose what to work on next.
1 · Open
Find your place.
Review the project’s notes and unfinished tasks.
2 · Update
Tell it what changed.
Tell BuildOS one thing that changed: something you finished, a new idea, or a deadline that moved.
3 · Continue
Choose your next step.
Check the updated project and decide what to tackle next.
Built for both
Use it yourself. Bring agents when you're ready.
Just you
Keep the whole project together.
BuildOS remembers the notes, tasks, decisions, and loose ends so you can return without rebuilding the context.
You + agents
Give agents the context to do useful work.
Agents read and update the same project state you use. No prompt archaeology. No hand-built handoffs.
You
Set direction and make decisions.
Agents
Execute scoped work with real context.
BuildOS
Keeps the shared project memory current.
Shared project memory
One project for you and your agents.
You set direction. Agents execute. Both work from the same live context.
You
Direction
Share ideas, make decisions, and choose what matters next.
Example
"Push the beta-reader pass to next week. Maya's act-3 turn should hinge on her sister."
BuildOS
Project memory
The project, its decisions, and its current state stay connected.
Project: Fading Crown
Doc: Maya — character arc
Task: Beta pass → +1 week
Ch. 12 rewrite
Agents
Execution
Agents pick up scoped work, use the context, and write results back.
Works with
Claude ChatGPT / Codex OpenClaw
Example
"Draft the beta-reader email, move the calendar block, and log the result."
BuildOS is the project memory. You and your agents are the workers.
Project structure
Everything has a place.
The pieces stay connected without forcing every project into the same template.
Projects
The work you're moving.
Goals
The outcome you're aiming for.
Plans
The path from here to done.
Tasks
The next concrete actions.
Milestones
Proof that the work is moving.
Documents
Notes, research, and drafts.
Risks
Blockers and open questions.
Flexible structure
A shape that fits the project.
Optional Google integrations
Connect Google only if you choose.
BuildOS works without a Google connection. Calendar and Gmail are separate, opt-in integrations: you start each connection and approve its requested permissions before BuildOS can access that Google account.
Google Calendar
Bring schedules together.
Choose which connected calendars BuildOS displays. When you enable syncing or request a calendar action, BuildOS can read availability and create, update, or remove events using the permissions you approved.
Gmail · read-only
Find context when you ask.
The current Gmail integration can search and read messages for features you invoke. It cannot send, edit, delete, archive, label, or mark email as read.
You can disconnect either integration at any time. See the Privacy Policy for how Google data is handled and the Terms of Service.
Start with one project
Start with the messy version.
Bring one thing you’re working on. Start with the rough notes you already have.