Developer event routing for agent operations

Rainrail routes development events into agent workflows.

Turn issues, pull requests, project queues, webhook deliveries, and operational signals into deterministic agent tasks with stable contracts between every source, plugin, and runtime.

Start with the workflowInspect the contractsOpen GitHub repo
Sources
GitHub, Cloudflare tail, project queues
Boundary
Neutral Rainrail event envelope
Output
Agent workflow with audit context
rainrail/routerlive route preview

Development event

issue.openedrepo: reirei-lab/rainrail

Neutral event

rainrail.event.v1source, actor, payload, trace

Policy and plugin routing

workflow: product-sitededupe, assign, observe

Agent workflow

codex.issue.implementationbranch, tests, PR, result callback
matched source adapter github.issuenormalized payload with contract rainrail.event.v1dispatched to runtime provider openclaw

Why teams put Rainrail in the middle

Automation stays understandable when the routing is explicit.

Webhook storms become ordered work

Incoming events are normalized before they reach an agent, so retries, duplicate deliveries, and project queue changes are handled as routing decisions instead of improvised scripts.

Contracts stay stable

Source payloads can evolve while workflow plugins keep receiving a predictable event envelope with the context they need to act.

Operators can audit every handoff

Dispatch reasons, assignment choices, and runtime inputs are designed to be visible enough for reviews, incident follow-up, and local replay.

Core workflow

From repository signal to repeatable agent run.

01

Source adapters capture events

GitHub issues, pull requests, project queues, and runtime telemetry enter through source-specific adapters.

02

Rainrail normalizes the envelope

Provider details are preserved behind a stable event contract with traceable actor, source, and payload context.

03

Plugins own the routing logic

Workflow plugins match events, apply policy, and choose the runtime without hard-coding every source to every agent.

04

Runtimes receive deterministic work

Agents start with explicit instructions, branch context, observable execution state, and a completion path.

Plugin model

Keep integrations small enough to reason about.

Source plugins

Translate provider-specific signals into Rainrail events.

GitHub issueCloudflare tailProject queue

Workflow plugins

Decide what should happen and why.

triageimplementationreview follow-up

Runtime providers

Start agents with reproducible input and reporting.

OpenClawCodexlocal runner

Initial content

Read the vocabulary, then trace the operating paths.

Concepts

Learn the event envelope, source plugin, workflow plugin, provider, and bridge room vocabulary before reading implementation contracts.

Guides

Follow the first GitHub issue automation, PR review loop, and Cloudflare event reporting paths at an operator level.

Examples

Trace the GitHub issue to Project queue to agent PR to review and merge workflow end to end.

Build the route before the agent runs

Use Rainrail when event-driven automation needs contracts, not another one-off webhook handler.

Follow the event pathEngineering docsRuntime contractIssues