EVENT RECEIVED
A task needs attention
A webhook or connected system sends a signal.
EVENT-DRIVEN AGENT OPERATIONS
Your agents.
Awake when
it matters.
WMOS (World Model Operating System) is an A2A, or agent-to-agent, message router. It connects agent workflows, databases and devices through adapters and supports event-driven awakening in compatible runtimes.
Turn an incoming event into purposeful action. Connect your agent environment, route the signal, and bring the result back.
Private pilot · Bring your own agent runtime
Spec-driven adapters connect your agent nodes to events.
FROM SIGNAL TO ACTION ILLUSTRATION
↓
WMOS ROUTER
The right agent wakes up
Your seat connects the event to its agent.
↓
RESULT RETURNED
The work comes full circle
Return the outcome to the requesting workflow.
LESS WATCHING. MORE DOING.
A connection between
events and useful work.
Keep your environment
Register a seat for your agent. Use its dedicated credential to connect to the router.
Act on the signal
Let relevant events trigger the next step in your agent workflow.
Bring results back
Connect execution to the original request. Pilot integrations are scoped together.
FROM EVENTS TO WORK
Usage examples
Explore workflows you could connect with WMOS. These are usage examples, not customer deployments.
The router forwards opaque messages without business interpretation. Adapters and bridges implement data mapping, business controls and permission checks.
Usage example
Direct an agent development team
Keep execution, review and rework connected across multiple tasks.
Explore the workflow
Connected nodes
Orchestrator, coder, QA, reworker, issue tracker
Trigger
A work request or review result arrives
Workflow
- Register a request as a task
- Route it to the assigned agent through WMOS
- Request rework or report completion after review
Required adapters
Adapters map seats to sessions and interpret task states.
Approval and constraints
Significant changes and deployment follow the owner’s approval policy.
Current scope
Inspired by internal ADE development. Instruction, ticket and issue integration is being improved; 72-hour unattended operation remains a goal.
Usage example
Connect ERP, MES and CRM
Collect information across systems and prepare a proposed action.
Explore the workflow
Connected nodes
ERP, MES, CRM, business agent
Trigger
A delivery date changes or a customer asks for an update
Workflow
- Receive the change event
- Retrieve stock, production and customer information
- Prepare an adjustment proposal for the owner
Required adapters
System adapters map fields and meanings and check read/write permissions.
Approval and constraints
Order and production schedule changes require approval before execution.
Current scope
Illustrative workflow requiring system-specific API and data mapping during implementation.
Usage example
Add intelligence above existing farm control
Keep existing local control while an LLM layer analyzes data and proposes plans and bounded actions.
Explore the workflow
Connected nodes
Sensors, existing local controller, edge buffer, LLM intelligence layer, operator
Trigger
A crop or environmental change, or a network outage
Workflow
- Existing controllers operate within deterministic control and safety rules
- An LLM layer analyzes collected data and proposes bounded actions
- Send approved actions through the existing control path and record results
- Keep local control and buffering offline, then synchronize after reconnection
Required adapters
Adapters validate controller commands, permissions and safety limits. The LLM does not replace deterministic control or safety functions.
Approval and constraints
Plans or control changes outside agreed limits require operator approval.
Current scope
Concept only. Offline operation assumes retained local control and buffering. An optional lightweight local LLM still requires model, hardware and site validation.
Usage example
Respond to factory equipment faults
Connect fault signals to maintenance history and prepare an inspection.
Explore the workflow
Connected nodes
PLC, SCADA, maintenance database, inventory system
Trigger
An equipment warning or fault code
Workflow
- Route the warning through WMOS
- Retrieve maintenance history and parts stock
- Report an inspection plan and required parts
Required adapters
Adapters translate device protocols, interpret codes and enforce control permissions.
Approval and constraints
Equipment shutdown and restart follow site safety procedures and approval.
Current scope
An illustrative workflow, not a deployed equipment case study.
Usage example
Coordinate city facility repairs
Connect fault intake to a draft parts purchase request.
Explore the workflow
Connected nodes
Facility sensors, service desk, fault database, parts inventory, owner
Trigger
A reported fault or sensor anomaly
Workflow
- Record symptoms and location
- Check similar repairs and parts availability
- Submit a draft purchase request and repair plan for approval
Required adapters
Adapters match facility identifiers and inventory records and enforce access rights.
Approval and constraints
An authorized official or owner approves the purchase before placement.
Current scope
Illustrative workflow requiring agency-specific integration and approval procedures.
Usage example
Connect a prescription QR to a chosen pharmacy
Explore resolving a recipient after a patient selects a pharmacy.
Explore the workflow
Connected nodes
Hospital system, QR lookup service, pharmacy, authorized institutional integrations
Trigger
A QR code is scanned at the patient’s chosen pharmacy
Workflow
- Request a prescription lookup using the QR code
- Verify patient consent and pharmacy authorization
- Deliver only necessary information to permitted recipients
Required adapters
A QR code is not unrestricted access. Adapters must validate expiry, access rights and data formats.
Approval and constraints
Patient consent and applicable institutional and legal integration requirements must be reviewed first.
Current scope
Healthcare concept only. It does not promise automatic transmission to public agencies or an existing deployment.
Usage example
Prepare insurance claim documents
Coordinate document preparation within the patient’s consent.
Explore the workflow
Connected nodes
Healthcare provider, patient, insurer, document agent
Trigger
A patient requests claim document preparation
Workflow
- Confirm consent scope and receiving institution
- Prepare required documents through authorized connections
- Deliver through an allowed submission channel after patient review
Required adapters
Adapters check institution-specific formats, authentication and consent scope.
Approval and constraints
Patient review and authorized insurer and provider integrations are required.
Current scope
A concept for coordinated processing, not a promise of claim payment or established institutional integration.
Usage example
Turn field data into a working record
Connect data acquisition and storage from devices to databases through WMOS.
Explore the workflow
Connected nodes
Measurement devices, collection adapter, WMOS router, database adapter and storage
Trigger
A sensor reading or device status event
Workflow
- The collection adapter records device ID, measurement time and units
- WMOS forwards the message to the designated database node
- The database adapter validates the format and prevents duplicate writes by event ID
- Route abnormal conditions to the responsible agent for analysis
Required adapters
Collection and database adapters implement device protocol conversion, units and format validation, replay and duplicate handling policies.
Approval and constraints
Configure read/write permissions and retention scope. Adding automatic control requires separate approval and safety rules.
Current scope
An illustrative workflow, not a customer deployment. Local buffering during outages and replay after reconnection require adapter implementation and site validation.
FROM EVENTS TO WORK
Real-world cases
This space is for real operating results backed by evidence approved for publication.
No real-world cases are published yet. Cases will be added after verification and permission to publish.
AI agent integration across your systems
WMOS provides A2A router message delivery for agent-to-agent communication. AI agent messaging connects a request with its recipient; adapters turn that exchange into a system-specific workflow.
MCP integration with Codex and Claude Cowork
Control connected systems from your familiar Codex or Cowork chat with a plugin or adapter. Codex MCP integration and Claude Cowork integration require a configured MCP connection and, for automatic incoming work, a receiver or bridge bound to the intended session. Client capabilities and network permissions apply. These are integrations, not claims of official affiliation.
AI agent workflow automation
Connect task requests, review results and rework through messages. The ADE example explores keeping instructions and tracked tasks connected; this integration is still being improved.
AI agent API integration
Adapters translate messages into permitted API calls and return results. API-specific authentication, validation and approval remain part of each integration.
AI agent database integration
ERP, MES and CRM AI integration can combine approved queries from business systems. Adapters map data meanings and limit access; the router does not interpret database contents.
AI agent device control
The smart farm concept adds LLM analysis above existing local control; deterministic safety remains in the controller, and offline buffering and optional local models require validation. Factory and city examples also connect device signals to an agent workflow. Device adapters enforce permitted commands, site safety limits and human approval where required.
Questions about WMOS
What does A2A mean in WMOS?
A2A means agent-to-agent communication here. WMOS routes messages using from/to/cc addressing. Compatibility with the separate A2A protocol standard has not been verified.
What does the router do, and what do adapters do?
The router forwards opaque messages. Adapters and bridges interpret data, connect system APIs and devices, and enforce business permissions and approval rules.
Can an SSE event wake any agent?
Awakening requires a supported runtime and a receiver bound to the intended session. Tested paths use Codex queue, Claude Code Channels or Cowork Monitor notifications. Network permission, authentication and a running receiver are required; this is not a promise of support for every client or version.
Are the examples customer deployments?
No. Usage examples describe possible workflows and their integration requirements. Real-world cases are published separately after verification and permission to publish; none are published yet.
Can I purchase the service today?
WMOS is in private pilot preview. Pricing is for discussion, scope is agreed before launch, and no payment is collected on this page. Model and agent runtime costs are separate.
PRICING PREVIEW · USD / MONTH
Start focused. Grow with your fleet.
Research prices for pilot discussion. Limits and availability are not finalized. No payment is collected here. Model and agent runtime costs are separate.
$29/mo
For a first event-driven workflow.
- Single-team pilot
- Agent connection setup
- Scope agreed before launch
$99/mo
For shared agent operations.
- Team workflow discovery
- Multiple-agent use case review
- Scope agreed before launch
$299/mo
For client automation businesses.
- Client operations discovery
- Deployment planning
- Scope agreed before launch