Triggers

Triggers let an agent notice a moment and decide whether it should act.

Most agent behavior starts with the user saying something. Spatial agents also need to respond to session context: a recognized object, a changed scene, a workflow step, a repeated hesitation, or another bounded signal exposed by the runtime.

In WorldAgents, triggers are agent-owned rules evaluated by the server. A trigger should return a structured decision. The runtime can then apply cooldowns, dedupe repeated observations, respect interruption policy, and expose evidence for review.

Triggers can be useful for:

• a museum guide noticing a recognized artwork
• a field coach noticing a visible tool or equipment state
• a review agent flagging a missing or suspicious visual condition
• a workflow assistant noticing that a step appears complete or skipped

The trigger does not need to own the whole session. It should describe the moment and the suggested action. The agent and runtime handle the human interaction.

The practical goal is to let teams adapt agent behavior close to the agent, test it in sessions, and avoid turning every customer-specific rule into platform code.