Skip to content
Airsup

Agents propose. People decide.

Agents watch your twin for new revisions, late parts and slipping stations. They bring a fix already tested on the twin, and nothing changes until a person applies it.

Get your plant simulated
  1. 01An agent proposes
  2. 02The twin tests it
  3. 03A person approves
Line agentDrone line, today 08:00

Drone X2 reaches the line on Monday. Camera calibration would run at 100% and hold back the week.

Proposal

Add a second camera calibration cell.

Testing on the twin

629 to 987 drones a week. The bottleneck moves to arms and top plate.

ApplyDismiss

Applied by the line lead. Logged with the week before and after.

Nothing changes on the line until a person applies it.Illustrative line, simulated

What agents watch.

They run in the background, so proposals are waiting when you open your workspace.

01New revisions

A change to a part or a product, and the stations and cycle times it touches.

02Late parts

A supplier running behind, and the day the line would run out.

03Slipping stations

A station running slower than its plan, and what that costs the week.

04The next bottleneck

The station next in line to limit output when demand or the mix changes.

The decision stays
with people.

Proposals, not changes
An agent prepares the change and its simulation. It never applies anything on its own.
Tested first
Every proposal comes with the week it was run on the twin, before and after.
A person applies it
The person responsible reviews it and applies it, or dismisses it.
On the record
Every applied change is logged with who applied it and the result before and after.

Bring your own agents.

Claude, ChatGPT, Codex and Cursor work on the same twin over MCP, inside the same approval path.

  • Claude

  • ChatGPT

  • Codex

  • Cursor