EXPERIMENTS

How we try ideas on human and agent work

Nobody knows yet what working with a fleet of AI agents should feel like. So we build small, real prototypes, put them behind a switch, and see what lands.

What an experiment is here

An experiment is a feature we are not sure about. It might become part of the product, change shape, or disappear. It is off by default, labelled beta, and lives in one place: Settings → Experiments. Turn one on and it appears in your dashboard; leave it off and a default install never shows it and never loads its code.

An experiment is not a promise. We say so in the changelog when one graduates, changes, or is removed.

How they work

Today there is one experiment on the switch. More will join it.

The longer story, with the mistakes and the evidence, is in the blog: Where should you look? What building a world for AI agents taught us.

Our experiments in human and agent interaction

The pattern we keep returning to: a person who runs many agents needs to know where to look, what is waiting on them, and how to reach the right agent or team in one step.

World view BETA

THE QUESTION
When you run dozens of agents across several machines and several companies, can a map show you where to look faster than a list can?
THE BET
Place carries meaning people already have. An organization is an island, a machine is a building, an agent is a person in a room. Status becomes a pose and a place, not only a colour: working at a desk, ready standing, waiting for you at the front, waving.
WHAT IS IN IT
Three levels (island, building, room). Three lenses: Status, Work (open cards on every host, and a list of what is waiting on you) and Relations (arcs for who messages whom and who shares cards, teams you can light up). A replay of the last hours of messages. A way into every agent: its chat, its terminal, a Zoom call, a Companion call, or its team’s meeting. Optional VR in a headset or an emulator.
HOW WE WILL KNOW
Whether people open it more than once, whether they use it to find the agent that needs them faster than the list does, and whether the relations view shows them something they did not know. We have not measured any of this yet; today it is a bet with a working prototype.
NOT YET CHECKED
A real headset: comfort and performance on a standalone Quest. Whether a 3D map beats a plain table for live monitoring at all; we found no study that shows it does.

Ideas we have shipped in the same spirit

Already in the product, not behind the switch. They are the same kind of bet, about how a person and an agent should meet:

What we learned before building

Before the second round of the World view we read ten open-source “agent office” projects and the research on virtual workplaces and gamification. What changed our plan:

Where this could go

If people and agents will one day share virtual workplaces, the pieces that matter are the ones that outlive any one world: a stable identity for each agent (ours is signed), memory and skills that belong to the agent, and a view that is derived from real state instead of storing its own. The World view is built that way on purpose: it keeps nothing of its own, so it can be rebuilt in another surface, a headset or a phone, from the same feeds.

We will also keep agents visibly agents. A person should never have to wonder whether the one waving at them is a colleague or a process.

Try it, and tell us

  1. Open Settings → Experiments in AI Maestro and turn on World view (beta).
  2. Click the new World button in the header.
  3. Try the three lenses, light up a team, press Replay, and open an agent from its card.

What would make it earn a place in your day, or what is just in the way? Tell us in the issues. The full guide is docs/WORLD-VIEW.md.

Sources