Clone it, run /setup, and it becomes yours in Claude Code or Codex — a second brain + Chief of Staff that holds your context, structures your work, drafts in your voice, and runs reliable workflows.
Open-source and opinionated — complete out of the box, not a blank slate. Fork it and make it yours for any role, company, or domain.
- Clone this folder to your machine.
- Open it in Claude Code or Codex and run
/setup(in Codex: invoke thesetupskill or just ask it to "run setup"). - Answer the guided interview (identity, voice, priorities, stack, team, guardrails). It fills
CLAUDE.md,context/,references/voice.md, andconnections.md. - Try the first prompt: "what should I focus on this week?"
Not sure what to write? Skim
examples/first — directional guides by role (founder, ops, regulated medtech, creator, sales) that show the shape of a filled gAIOS. They're direction, not data — you won't copy them.Runtime compatibility (Claude Code · Codex · others) is summarized in Compatibility below.
The Four Cs — Context (knows your business) · Connections (reaches your stuff) · Capabilities (knows how to do the work) · Cadence (runs without being asked).
The Three Ms — Mindset · Method · Machine (references/3ms-framework.md). Both frameworks inspired by Nate Herk's work — see NOTICE.
WAT — Workflows · Agents · Tools. Probabilistic AI reasons; deterministic code executes. Boring, testable, auditable.
Features (all included):
/structure— turn any fuzzy input into a clear brief./triage·/daily·/weekly— the Cadence layer: batch-sort an inbox, get a focused daily brief, run a weekly operating review./wiki— a second brain: drop notes inraw/, get clean cross-linked knowledge inwiki/(with a leakage-scanning lint gate)./graph·/graph-query·/graph-ingest— a knowledge graph (graphify) over your code +wiki/: build/visualize it, query relationships, and ingest external sources into the second brain./draft·/prep·/decide— Chief-of-Staff core: draft comms in your voice, prep a one-page brief for any meeting/person, and frame + log a decision./workflow— dynamic workflows: goal-driven, composable, self-verifying pipelines with a quality gate per step./experiment— an autoresearch loop (try → measure → keep/revert → log), with a runnable forecast example./exec-cockpit— a leadership-transition / exec-cockpit template.tools/— deterministic Python (branded-HTML renderer, wiki lint, experiment log).- Operating discipline baked into
CLAUDE.md(think-before-acting, simplicity, surgical changes, goal-driven, verify-before-done). - A brand kit template (
brand-assets/) so outputs render on-brand.
CLAUDE.md ← the operating manual (filled by /setup)
AGENTS.md ← Codex / cross-tool runtime bootstrap (mirrors CLAUDE.md's rules)
examples/ ← directional guides by role (what good looks like; not pre-filled data)
context/ ← about you, the business, the team, priorities
wiki/ · raw/ ← second brain (wiki committed; raw git-ignored)
projects/ ← active workstreams
experiments/ ← autoresearch harness (+ runnable forecast example)
tools/ ← deterministic Python (WAT execution layer)
references/sops/ ← workflows / SOPs (incl. dynamic-workflows + examples)
references/ ← 3ms framework, voice, API guides
brand-assets/ ← CI/CD template (tokens + preview)
connections.md ← registry of systems the AIOS can reach
decisions/log.md ← append-only decision record
.claude/skills/ ← /setup, /structure, /triage, /daily, /weekly, /wiki, /graph, /graph-query, /graph-ingest, /draft, /prep, /decide, /workflow, /experiment, /exec-cockpit, /onboard, /audit, /level-up
.codex/skills/ ← symlink → .claude/skills (so Codex discovers the same skills)
See EXPANSIONS.md for what to add as you grow.
The Guardrails block in CLAUDE.md ships with safe defaults. Set your sensitive-data line and compliance rules (GDPR / HIPAA / SOC2 / medical-device / …) during /setup — don't run the defaults unchanged for a regulated business.
gAIOS integrates graphify — it turns your code + committed wiki/ into a navigable, queryable knowledge graph (interactive graph.html, a GRAPH_REPORT.md of god-nodes & surprising connections, and an MCP server). Build it with /graph, ask it with /graph-query, and feed external sources into your second brain with /graph-ingest.
python tools/graphify_setup.py install # installs graphify + wires the Claude Code & Codex skills (also offered by /setup)Code is processed locally; only the de-identified wiki/ is sent to your host AI session for extraction (never raw//.env/.tmp/), and graphify-out/ is git-ignored. Details: references/graphify-api.md · SOP: references/sops/knowledge-graph.md.
gAIOS runs on any agentic coding tool that reads a project-instructions file. Claude Code is first-class; Codex / Codex CLI is supported via AGENTS.md.
| Runtime | Reads | gAIOS workflows (skills) | Status |
|---|---|---|---|
| Claude Code | CLAUDE.md |
Native slash skills (/setup, /structure, …) in .claude/skills/ |
✅ First-class |
| Codex / Codex CLI | AGENTS.md → points it to CLAUDE.md + context/ |
Auto-discovered from .codex/skills (symlink → .claude/skills), or invoke by name |
✅ Supported |
| Other agents (Cursor, Gemini CLI, Copilot, …) | AGENTS.md / CLAUDE.md |
Ask for a workflow by name; the agent reads the matching .claude/skills/*/SKILL.md or references/sops/ |
Using gAIOS in Codex: open the repo in Codex CLI — it loads AGENTS.md automatically, which directs it to CLAUDE.md and context/ and restates the hard guardrails. Project skills load from .codex/skills (a symlink to .claude/skills); on Windows without symlink support, the agent reads .claude/skills/ directly as instructed in AGENTS.md. Configure MCP servers in ~/.codex/config.toml and keep secrets in .env. Details: AGENTS.md.
One source of truth:
CLAUDE.mdholds the canonical,/setup-filled content;AGENTS.mdmirrors its rules for other runtimes and defers to it on any conflict.
gAIOS is © 2026 Alireza Rezvani, MIT-licensed (see LICENSE). It is inspired by Nate Herk's AIS-OS starter kit and his Three Ms / Four Cs frameworks, which are credited as inspiration (see NOTICE); those framework names are Nate Herk's trademarks. Everything in this repo — the WAT integration, second-brain wiki, autoresearch harness, dynamic workflows, Operating discipline, and the tools — is Alireza Rezvani's work. Please keep the inspiration credit to Nate Herk.