RosmarOps
Observatory · Agent map

How much can each AI agent do without asking you?

We install each agent as it comes, on the same test computer, and measure what it can do on its own: read your files, run programs, send data out or change what other agents do.

What it's for
  • To choose. Before you install an agent, see what each one can do as it comes.
  • To know what to watch. If you already use one, see what it does without asking you: read your whole disk, run programs or send data out.
  • To know who decides. For each action, whether it asks you, another AI decides or it asks nobody. You see it when you open each agent.

It doesn't say whether an agent is safe. It says how much it can do without you. What suits you depends on what you use it for.

Calculated by RosmarOps 0.11.3 on the reference computer, on 12 November 2026. Updated with every version.

Does little without asking youDoes some things without asking youDoes quite a lot without asking youDoes a lot without asking you

The factory score goes from 0 to 100: the higher, the less exposed. The class says what the design allows; the score, what is left exposed with the keys on the test computer.

What one looks like inside
Yo

«Find out why the deploy is failing.»

IA

To understand it, it reads files in your project and also in other folders on the disk. It doesn't ask you.

IA

If it needs to run a program or send something to the internet, it doesn't ask you either: another AI, a classifier model, approves or blocks it.

Claude Code, in its default mode. Source: its official documentation, read on 24 October 2026.

It isn't a bug or an abuse: it's how it comes. That's why it's worth knowing.

The six axes, without jargon

What each bar looks at

Autonomy

How many important things it does without asking you: read outside your project, write, run programs or send data out.

Example: Claude Code, reads files anywhere on your disk without asking you.

Reach

How far it gets without asking you: only your project, your whole disk, or your disk and the internet too.

Example: Claude Code, reaches your whole computer, not just the project.

Contagion

Whether it reads files other agents can change, or loads another agent's configuration. That way, what one does can change what another does.

Example: Antigravity CLI, reads an instructions file other agents can change.

Delegation

Whether it is another AI, not you, that decides if an action goes ahead.

Example: Claude Code, another AI decides whether it changes other agents, not you.

Opacity

How much of what it can do can't be seen by looking at its configuration, because it's decided in the app or on the server.

Example: Claude Code, a classifier decides on the spot: you can't know beforehand what it will allow.

Complexity

How many files, layers and formats you have to check to know what it is allowed to do. The more there are, the easier it is for something to slip through.

The first three weigh more, because they change most what can happen.

What keeps coming up

Three patterns this season

A model decides more and more

Several agents now come ready for another AI to approve their actions instead of asking you.

The file everyone reads

One instructions file, like AGENTS.md, is read by several agents at once.

What can't be checked

Some keep their permissions inside the app, where neither you nor RosmarOps can check them.

This is each agent out of the box. Yours may be different.

It depends on how you have set it up, on the keys on your computer and on the other agents you use.

Check my computerFree · Windows, Mac (preview) and Linux

How we measure it and what it doesn't measure

We measure each agent on its own, on the same test Windows machine and with its default settings. We measure contagion with all of them installed at once. When something can't be measured, we say so: no data never counts as good.

Complexity counts what the vendor documents. An agent that documents little may look simpler than it is; what can't be read counts in opacity.