Boot a session in minutes.
There is nothing to install and no account to create. You bring a chatbot and a project; AIR — short for AI Resource — brings the structure: a teammate that works the project with you, not an autopilot you hand it to.
Get the boot bundle
Open the AIR repository and grab the boot files. Nothing to install, no account to create — AIR is a prompt-based framework.
Open your AI chatbot
Start a fresh session in whatever you already use — ChatGPT, Claude, Gemini, Grok, Mistral, or your own model. AIR depends on none of them in particular.
One requirement does apply: the boot bundle is ~130k tokens, so use a model tier with a 200k-token context window or larger. On smaller windows the files load only partially — and a partially loaded AIR role-plays instead of running (see: real boot vs roleplay).
Activate AIR
Paste the boot bundle into the session. AIR loads, configures the environment, and takes over the structure of the work.
Answer the onboarding
AIR asks a short, deterministic set of questions to fix what you are building and how it should work with you — files, diffs, review, pace. That agreement scopes the whole session.
Work, with structure
From here AIR runs the work: roadmap first, one active step at a time, with the AIR objects printing into the chat so you can see exactly what it is doing.
Continue anywhere
When you stop, AIR emits a handoff card — a JSON block capturing the project and the next step. Paste it into a new session, on the same model or a different platform, to pick up exactly where you left off.
A real boot prints a formal AIR_SESSION object into the chat — structured JSON, not prose. If your model only describes AIR without emitting the object, it is role-playing, not running; re-boot or try another model. Behavior varies by model — some boot cleanly, some role-play, some refuse the files — so if yours refuses or role-plays, tell us in Discussions. More on the tell: real boot vs roleplay, or see a full session. The glossary defines AIR_SESSION and the other objects.
The full reference — boot files, methods, and the concepts behind each step — lives in the repository. This page is the short path; the repo is the manual.
Ready when you are.
Grab the boot bundle and start your first session, or read the model behind it first.