AIR inside Claude Code
Run an AIR risk assessment from your code editor. Only two short files leave your computer, and you see them first.
· 2 min read
AIR now runs inside Claude Code. A developer can assess the AI system they are building, answer the open questions and fix gaps, all from the same place they write the code.
Get started
AIR for Claude Code is in preview. To try it, book a demo and we will set you up.
Once it is installed, open the repository of the system you want to check and type /air:scan. No AIR account yet? Claude opens a short form in the chat to create one. Claude never sees what you type into it.
What happens in a scan
- A few questions first. Claude asks only what the code cannot show: what the system is for, who uses it, where it runs, and whether it is used in the EU. You answer once; the answers are saved.
- A short checklist. Before any credit is spent, you tick what the system does, such as hiring or credit scoring, or pick "None of these". It costs nothing, and nothing is sent yet.
- Two files, shown first. Claude reads the code on your computer and writes two short files: a summary of the system, and the code facts with file and line numbers. You see both before anything leaves your computer. They quote short snippets, never whole source files.
- One credit, after a yes. The assessment starts only after you agree, and Claude Code asks again before the credit is spent.
- Progress as it runs. Claude shows each step, and the scan usually takes 8 to 10 minutes. You can keep working, and you get a link to the full report.
The result
Claude gives you the EU AI Act tier and what it means for your system, the main risks, and the next step for each one:
- Answer a question: in one short form. "Not sure" is a fine answer, and it is not asked again.
- Fix in code: Claude offers the change and makes it only after you say yes.
- Decide: for a point a person must judge, you save a short reason with the project.
- Add a document: when the code cannot show something, such as a policy or an agreement.
The same report is on the AIR website for the rest of your team.
Scan again
After a change, run /air:scan again. Claude first shows the last report. If nothing changed, you answer the open questions on that report with no new credit. If the code or documents changed, a new scan shows what closed, what is still open and what is new.
For your team
After the first scan, Claude can add AIR to the repository settings, so every teammate who opens the project gets the plugin. Each teammate still needs an invitation to the project in AIR.