Home

AI OS

Build your own AI Operating System to automate your business and life

AI OS shows you how to build the layer that connects AI to your context, your data and your tools. It's platform agnostic, so it works with any agent and runs wherever suits you.

Navid Moazzezby Navid Moazzez·Updated 25 Sep 2026·5 min read

AI OS is a book about building your own AI operating system (AI OS): the layer underneath your AI tools that connects AI to your context, your data and your tools.

It's platform agnostic and adaptable, so it works with any agent and runs wherever suits you.

I run my own business this way. The same system lets me do the work of more than 10 full-time employees by myself, every day.

In this summary, you'll learn:

  • What the AI OS book is about
  • The 7 layers of an AI OS
  • What's inside the book, and the ideas behind it
  • Who should read it, and my favorite quotes from it
  • Why I'm writing it
  • How to read it first

Let's start with what the book is about.

What is the AI OS book about?

Most people use AI as a series of one-off prompts. They open a chat, paste in who they are, explain their offer again and fix the same wrong guesses. Tomorrow they do it all over again.

An AI OS ends that. You tell it once, and every session after that starts already knowing you.

Because it's platform agnostic, it runs wherever suits you: on your computer, on an always-on VPS, in the cloud from a private GitHub repo, or through tools like Grok Bot that make it simpler to run. Its MCP server, CLI and API hook it up to any agent, even cloud ones like Claude Cowork and ChatGPT. The book shows you how to build yours from scratch, one layer at a time.

AI operating system (AI OS): The layer underneath your AI tools that connects AI to your context, your data and your tools. It's platform agnostic: any agent can use it, wherever it runs.

@thenavidm

Most founders still use AI like a search box.

The ones pulling ahead run their business on their own AI OS.

The 7 layers of an AI OS

Every AI OS is built from the same 7 layers. Each layer needs the one below it, so you build them in order, and the book gives each layer its own chapter.

LayerIts jobWhat goes in it
ContextKnows youYour rules file and your context files: who you are, what you sell, your voice
DataHolds your business in one placeCustomers, sales, content and conversations, linked so it can answer questions
ToolsReaches your appsConnectors to your email, calendar, CMS, payments and more
MemoryKeeps what it learnsYour brain, meetings, decisions, corrections and daily notes
SkillsDoes the workOne folder per job, each with a SKILL.md
AutomationsRuns without youDaily and weekly routines, and scheduled runs
AppsShows you the answerA brief page, a dashboard, a command center

The test is simple. Open a fresh session and type "write a post about my offer." If it names your offer and your price in your voice, your AI OS is working. If it asks what you sell, start with Context.

What's inside the book

The book gives each layer its own chapter, with a chapter before them and 2 after:

  1. What an AI OS is. Why every AI tool starts from zero without one, and what changes when it doesn't.
  2. Context. Everything your AI OS knows about you before you type a word: who you are, what you sell, who you sell to and how you write.
  3. Data. Your customers, sales, content and conversations in one place, linked so your AI can answer questions about your business.
  4. Tools. Connectors to your email, calendar, CMS and payments, so your AI OS reaches the apps you already use.
  5. Memory. Where your decisions, corrections and daily notes land, so you never give the same correction twice.
  6. Skills. one folder per job, so the work you repeat every week runs from a single command.
  7. Automations. Routines that run without you, like a morning brief that's waiting before you sit down.
  8. Apps. A page that answers before you ask: a brief, a dashboard, a command center.
  9. Your first 14 days. What to expect in your first 2 weeks, from your first setup interview to your first skill of your own.
  10. How to measure your AI OS. One number per layer that tells you whether it's working, and a weekly score out of 100.

The ideas behind the book

Systems over goals

A goal is a wish with a deadline. A system is something that produces the result whether or not you are motivated that day. Everything I build, for me or for other people, is an attempt to move something from the first category into the second.

Context comes first

Every layer after it works better because your AI already knows you.

Keep the tools you use

You don't switch anything to build an AI OS. You connect what you already have.

Build it by hand, then automate it

A skill earns its schedule by working first.

@thenavidm

You will not be replaced by AI. You will be replaced by someone who uses AI. And someone who uses AI will be replaced by someone with their own AI Operating System (AI OS).

Who should read AI OS

  • Founders, creators and solopreneurs who use AI every day but still start from scratch in every chat.
  • Anyone who wants AI to know their business: their context, their data and their tools.
  • People who use Claude Code, Codex or other agents and want one system behind all of them.
  • Teams of one who want to do the work of a bigger team without hiring one.
@thenavidm

You will not be replaced by AI.

You will be replaced by someone who uses AI.

And someone who uses AI will be replaced by someone with their own AI Operating System (AI OS).

@thenavidm

Your master prompt is your AI identity: who you are, how you write, and what you never say.

Write it once. Use it everywhere.

@thenavidm

The fastest way to get better output from AI is to stop repeating yourself and give it your context once.

@thenavidm

Your first AI setup will be messy. Mine was.

Fix one thing every time it gets something wrong, and it gets better every week.

Why I'm writing it

I'm the founder of AI OS Lab, and the AI OS is the through line in everything I do now. It's what I write about every week, and what I build with people directly.

Your first setup won't be perfect. Mine isn't either. The more you run it, the more it knows, and the book is how I've learned to build it, one layer at a time.

How to read it first

Everyone on the list at aiosbook.com reads the first chapter before the book goes on sale.

Learn more

  • How to build an AI OS: My step-by-step guide to building your AI OS in Claude Code, Codex or any AI agent, from an empty folder to a system that runs every day.
  • The AI OS book: The book's own site, where you join the list and read the first chapter first.
  • How I use AI: The tools, agents and workflows I run my own business on, every day.
  • About Navid: My story, from law school in Stockholm to building my business on AI.

FAQs about the AI OS book

Have questions about the AI OS book? Here are answers to the most common ones.

It shows you how to build your own AI operating system (AI OS), the layer that connects AI to your context, your data and your tools, one layer at a time. It's platform agnostic, so it works with any agent and runs wherever suits you.

An AI OS is the layer underneath your AI tools. It holds your context, your voice, your offers, your customers and your workflows in one structured place that every AI you use can read.

No. It runs on top of the computer you already have, inside an AI agent like Claude Code. The name comes from what it does: the way macOS loads your files and settings when you log in, an AI OS loads your business every time a session starts.

Context, Data, Tools, Memory, Skills, Automations and Apps. Each layer needs the one below it, so you build them in order.

No. An AI OS is plain text files and a few commands. You write the files in plain English, and the agent handles any technical setup for you.

Any agent that reads files from a folder. Claude Code reads CLAUDE.md, Codex and Cursor read AGENTS.md, and Gemini CLI reads GEMINI.md. Make those the same file and they all share one AI OS.

No. It can run on your computer, on an always-on VPS, in the cloud from a private GitHub repo, or through tools like Grok Bot that make it simpler to run. Its MCP server, CLI and API also connect it to cloud agents like Claude Cowork and ChatGPT.

No. A second brain stores what you know. An AI OS puts it to work. Many setups point the AI OS to a second brain folder, so the agent can search your notes when a task needs them.

The agent is the tool that does the work, such as Claude Code. The AI OS is what the agent reads: your context, your connectors and your commands. Switch agents and your AI OS comes with you.

Wherever you run it: in plain files on your computer, on an always-on VPS or in a private GitHub repo. API keys stay in a settings file that git ignores. What gets sent to the AI model depends on the agent you use, so check its data settings.

The AI OS files are free. You pay for the AI agent you run it in, such as a Claude or ChatGPT plan, and for any paid tools you connect.

Yes. Keep the shared context and commands in one folder the team syncs, such as a private GitHub repo, and let each person add their own files on top.

Yes. Everyone on the list at aiosbook.com reads the first chapter before the book goes on sale.

Navid Moazzez

AI business strategist & AI OS builder

Navid Moazzez helps creators and founders master AI and build their own AI Operating System (AI OS) to automate their business and life.

Navid.me is reader-supported. When you buy through links on this site, I may earn an affiliate commission. Learn more.

Free AI newsletter

The most actionable AI newsletter for founders

Every week, get proven AI strategies, curated tools, and step-by-step systems to grow your audience, create better content, and build a profitable creator business.

No fluff, no filler, no BS. Just five minutes each week that might level up your online business and life.

P.S. Sign up now to get free access to my ultimate AI tools guide for creators.

Loved by 10,000+ readers