gAIOS workflow
Open-source personal AI OS blueprint for Claude Code and Codex: context, second brain, daily briefs and drafts in your voice.
- 50 ★ on the repository
- Last commit
Extended access
Why this level
- The blueprint holds personal context, voice and priorities, and mail and calendar connections give the agent access to your data.
Install
- Works in
Manual install
Clone the `alirezarezvani/gaios` repository, open the folder in Claude Code or Codex and run `/setup`. In Codex invoke the `setup` skill or ask to run setup.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The blueprint holds personal context, voice and priorities, and mail and calendar connections give the agent access to your data.
This is third-party code. Review the repository files before installing.
What it does
gAIOS is a blueprint delivered as a repository: you clone it, open it in Claude Code or Codex, run `/setup` and answer an interview about identity, voice, priorities, stack and team. The answers fill `CLAUDE.md`, the `context/` directory, `references/voice.md` and the `connections.md` registry. After that the agent acts as a personal chief of staff. The set includes skills `/structure` to turn a raw thought into a brief, `/triage`, `/daily` and `/weekly` for inbox sorting and reviews, `/wiki` for a second brain built from notes, `/graph` for a knowledge graph, `/draft`, `/prep` and `/decide` for drafts, meeting prep and a decision log, plus `/workflow` and `/experiment`. The deterministic part lives in Python tools in `tools/`.
Who it is for. Founders, executives and consultants who want a personal AI assistant with memory of their business instead of writing system instructions from scratch.
Good fit when
- Each morning you need a short brief of tasks and weekly priorities from your own data
- Notes and documents should become a linked knowledge base with cross-references
- A letter or post should sound like you instead of a generic template
- A one-page brief on a person or project is needed for a meeting
- An important decision should be framed and logged
Not a fit when
- You want a ready product without setup: the template is filled through an interview and is useless empty
- You want data kept only in a cloud service: the template lives in your folder and in git
- You need one separate skill: the set is meant to be used as a whole
Example request
What should I focus on this week given my priorities and context? Build a weekly review.Limitations
The blueprint works in Claude Code or Codex, other environments are described briefly. The main branch of the repository is named `dev`. Full value appears only after the `/setup` interview and filling in context, voice and connections. `raw/` is ignored by git while `wiki/` is committed, so check it holds no personal data before publishing the repository. Mail and calendar connections are set up by you in `connections.md`, and their rights decide what the agent can do. GitHub metadata shows no detected license, and the `NOTICE` file credits the inspiring project.
How to disable. Delete the cloned gAIOS folder. Revoke mail and calendar connections added through `connections.md` in the services themselves.
FAQ
Where do I start after cloning?
Open the folder in Claude Code or Codex and run `/setup`. The interview on identity, voice, priorities, stack, team and guardrails fills `CLAUDE.md`, `context/`, `references/voice.md` and `connections.md`.
How does the second brain work?
Drop notes in `raw/` and the `/wiki` skill turns them into linked pages in `wiki/`. A lint gate scans for leaks of personal data. The `raw/` folder stays out of git.
Does it suit Codex?
Yes. `AGENTS.md` mirrors the rules of `CLAUDE.md` and `.codex/skills` is a link to `.claude/skills`, so Codex finds the same skills.
What is `/workflow`?
Dynamic pipelines: a goal, composable steps and a quality gate at each step. Example SOPs live in `references/sops/`.
Are there examples of a filled blueprint?
The `examples/` directory has role guides: founder, ops, regulated medtech, creator and sales. They show direction and are not data to copy.
Discussion
No questions or reviews yet.
Related
WorkflowsPersonal assistant kit for Claude Code, Codex CLI and Grok CLI: file-based memory, 23 skills and a guided first-run setup
A starter skill kit for Claude Code and Codex: personal onboarding, a knowledge base, a system audit and a visual map of knowledge
Local AI commands for voice and text: clipboard dictation, text fixes, speech, an assistant and parallel agents in worktrees
Claude Code skill that builds an Obsidian wiki from ChatGPT and Claude exports, articles and email, Karpathy style.
Set up Claude Code and Codex in one conversation: global instructions, rules, plugins, skills, a status line and correction memory
A plugin for Claude Code and Codex: department folders with rules and 35 skills to run a one-person company through AI agents
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| gAIOS (this card) | no | 50 | |
| Obsidian Agent Vault Template | no | 67 | an Obsidian vault template with skills beside the notes; gAIOS adds a setup interview, cadence skills and a decision log |
| obsidian-second-brain | no | 5,297 | persistent agent memory in Obsidian; gAIOS is broader and includes context, voice and pipelines |
README in short
The README covers the quick start, a four-layer architecture (context, connections, capabilities, cadence), the skill list, directory structure and compatibility with Claude Code and Codex. The blueprint is presented as open and self-contained.