# Watchline - The Event Layer for Agents

Build agents that react at the right time. Watchline gives developers APIs, MCP tools, webhooks, and runtime plugins so agents can watch app events, filter noise, and receive only the events that match a user intent.

## Getting Started

- [Start](https://watch.qordinate.ai/app): Create a Watchline project and get setup instructions.
- [Docs](https://watch.qordinate.ai/docs): Choose the setup guide for OpenClaw or Hermes.
- [OpenClaw setup](https://watch.qordinate.ai/docs/openclaw.md): Install the Watchline OpenClaw plugin and register watches from OpenClaw.
- [Hermes setup](https://watch.qordinate.ai/docs/hermes.md): Install the Watchline Hermes plugin and register watches from Hermes.

## Documentation and Resources

- [Homepage](https://watch.qordinate.ai): Product overview for Watchline.
- [Docs index](https://watch.qordinate.ai/docs): Setup guide index for supported local agent runtimes.
- [OpenClaw docs](https://watch.qordinate.ai/docs/openclaw.md): Step-by-step setup for OpenClaw users.
- [Hermes docs](https://watch.qordinate.ai/docs/hermes.md): Step-by-step setup for Hermes Agent users.
- [Dashboard](https://watch.qordinate.ai/app): Project setup, API key, channel, and integration instructions.
- [Blog index](https://watch.qordinate.ai/blog): Practical articles about event layers, proactive agents, and delivery patterns.
- [RSS](https://watch.qordinate.ai/feed.xml): Blog feed.
- [Full Markdown corpus](https://watch.qordinate.ai/llms-full.txt): All public docs and articles as Markdown.

## Features

- Intent-based watches: Register what a user wants to be notified about.
- App event filtering: Watchline filters noisy source events before waking the agent.
- App connection flow: Watchline asks for connection links when an app needs to be authorized.
- Webhook delivery: Send matched events to a hosted agent backend.
- Pull delivery: Let local agent runtimes poll for matched events.
- Hosted MCP: Let agents create and manage watches through MCP tools.
- OpenClaw plugin: Add local pull delivery to OpenClaw while hosted MCP provides the watch tools.
- Hermes plugin: Add local pull delivery to Hermes Agent while hosted MCP provides the watch tools.

## Articles

- [Cron is the wrong primitive for inbox and calendar watchers](https://watch.qordinate.ai/blog/cron-is-the-wrong-primitive-for-inbox-and-calendar.md): Scheduled checks can ship a demo, but inbox and calendar assistants need event-aware wakeups with evidence and delivery semantics.
- [Tokens per useful wakeup](https://watch.qordinate.ai/blog/tokens-per-useful-wakeup.md): A first look at WatchBench Email v0 and why proactive-agent benchmarks should measure useful interruptions, not only task success.
- [What wakes the agent?](https://watch.qordinate.ai/blog/what-wakes-the-agent.md): The most important question for proactive agents is not what model they use. It is which event is allowed to interrupt them.
- [What agent builders are learning from OpenClaw, Hermes, Claude Code, and Codex](https://watch.qordinate.ai/blog/agent-runtime-pain-points-2026.md): The 2026 assistant stack is converging on the same pain points: context cost, handoff, permissions, local delivery, and reliable interrupts.
- [The event layer is becoming agent infrastructure](https://watch.qordinate.ai/blog/event-layer-for-agents.md): Why proactive agents need an event layer between raw app streams and expensive reasoning turns.
- [Local agents need interrupts, not bigger background loops](https://watch.qordinate.ai/blog/make-openclaw-proactive-without-polling-everything.md): A broader view of why desktop and local agents need upstream event filtering before they can become truly useful.
- [Proactive assistants need interrupt infrastructure](https://watch.qordinate.ai/blog/proactive-assistants-need-interrupt-infrastructure.md): Why Pi, OpenClaw, Hermes, Claude Code, and Codex point toward event-driven assistant runtimes.
- [The cascade architecture for proactive agents](https://watch.qordinate.ai/blog/the-cascade-architecture-for-proactive-agents.md): Why agent systems should filter events through cheap deterministic layers before spending large-model reasoning.
- [Agent events need delivery semantics](https://watch.qordinate.ai/blog/webhook-vs-pull-delivery-for-agent-events.md): Why local agents, hosted agents, and MCP clients need different event delivery contracts.

## Markdown Pages

- [Hermes setup](https://watch.qordinate.ai/docs/hermes.md): Connect Hermes Agent to Watchline with the first-party platform plugin.
- [OpenClaw setup](https://watch.qordinate.ai/docs/openclaw.md): Connect OpenClaw to Watchline with the first-party plugin.

## Community and Support

- [Discord](https://watch.qordinate.ai/discord): Join the Watchline community and get support.