World2Agent opens W2A Protocol with a 5-minute GitHub sensor guide

• rohanpaul_ai's launch thread framed World2Agent as an open protocol for agent perception, with a fixed World → Sensor → Agent flow that turns outside events into structured signals before a human writes a prompt.
• The official GitHub repository says W2A ships runtime plugins for Claude Code, Hermes, and OpenClaw, plus reference sensors and an Apache 2.0 codebase.
• According to the signal format spec, every sensor emits the same envelope, including source metadata, event type, summary, and timestamps, so agents do not need per-sensor wire formats.
• The SensorHub catalog launched with seven listed sensors, while the build-a-sensor guide claims custom sensors can be scaffolded in about 50 lines.

You can browse the repo, read the signal schema, and install a starter sensor from SensorHub. The quickstart that rohanpaul_ai linked is unusually concrete: Claude Code gets a plugin, then a /world2agent:sensor-add command, then a restart with a plugin channel flag.

The core claim is simple. W2A wants a standard layer for noticing changes, not another tool API.

The repository's Why W2A note argues that most agents are still reactive, either waiting for user input or polling on a schedule. W2A's answer is a reusable sensor that watches a source, emits a normalized event, and lets the agent decide whether to act.

That lines up with rohanpaul_ai's comparison to MCP, which positions W2A as the "when to wake up" layer rather than the "what tools can I call" layer.

The useful technical detail is in the signal format spec. W2A defines one shared envelope, pinned to a versioned schema directory, with fields for:

• signal_id, schema_version, emitted_at
• source, including sensor_id, sensor_version, source_type, and package metadata
• event, including an event type, occurrence time, and natural-language summary

That is the part that can remove glue code. The same spec is meant to cover GitHub events, news feeds, social posts, or alerts without custom payload handling for each connector.

The quickstart already covers three runtimes:

• Claude Code: install machinepulse-ai/world2agent-plugins, add a sensor, then restart Claude Code with --dangerously-load-development-channels.
• Hermes: install a global sensor bridge, then use /world2agent-manage add inside Hermes.
• OpenClaw: install its bridge and management skill, then register sensors through chat.

The repo also ships a security warning worth noticing: untrusted sensors are treated as untrusted instruction sources, because they determine what the agent perceives and may trigger.

The launch is not just a protocol spec. SensorHub is already live as a registry with seven listed sensors, including Hacker News, Frontier AI News, Polymarket, weather, and registry-monitoring entries.

The custom path is equally explicit. The build-a-sensor guide says a sensor can be written in about 50 lines, and the repo's roadmap adds a future graph layer for composing and enriching signals from multiple sensors before they hit the agent.

LLMpsycho's reply captured the appeal in one line: one fewer glue layer. That is a pretty fair summary of what MachinePulse actually open-sourced here.