Skip to content
Pathrule

pathrule.iodocs

Pathrule

docs

DocsGet started

Signals overview

Pathrule Signals records runtime errors and events, groups them by the code path they came from, lets your coding agent read them, and verifies a fix with evidence from a newer release.

On this page

Pathrule Signals connects what your app does at runtime with the developers and coding agents that change it. You instrument your code once with the open-source SDK. It reports errors, and the events that show a flow working, together with the code path and flow they belong to and the release that produced them. Signals groups what it receives, keeps it, makes it readable by your coding agent, and decides from runtime evidence whether a fix actually holds.

What it does

  • Instruments your code. pathrule.error() and pathrule.event() report what happened, each linked to a code path (node) and a flow. See the quickstart.
  • Collects events. The SDK batches them into envelopes of the Signals protocol and retries on failure without ever rejecting.
  • Groups them. One group per environment, kind and fingerprint, so thirty-seven occurrences of the same error are one thing to look at.
  • Verifies fixes. A group is verified only after a newer release has been observed long enough and its own flow has succeeded. See verification and lifecycle.
  • Observes across releases. A newer release restarts observation, and an occurrence in any later release reopens the group as recurred.
  • Reaches your agent. The agent integration gives coding agents a runtime line in their context and a tool to read the groups under the path they are working on.

Three operating modes

ModeAccountWhere events goWhat you get
StandaloneNoneAn HTTP collector you run, through httpCollector()The SDK and the protocol. You store and process events yourself.
Pathrule LocalNoneThe Pathrule host on your machine, through pathruleLocal()Storage, grouping, verification, agent access and the CLI, all local.
Pathrule CloudPathrule accountManaged ingestion, through pathruleCloud({ key })Retention and agent access with your own session, on Pro, Team and Enterprise.

Standalone and Local are on every plan, are not metered and need no paid plan. Cloud Signals is part of Pro, Team and Enterprise; see Cloud Signals and pricing.

What Signals is not

  • Not analytics. There are no users, sessions or funnels. Signals records errors and flow outcomes, grouped by code path.
  • Not an automatic fixer. Signals tells you and your agent what happened and whether a fix held. Changing the code stays with you and your agent.
  • Not a manual resolve button. Recording a fix is a claim. Only runtime evidence resolves a group.

What ships

  • The SDK (@pathrule/signals 0.2.0, Apache-2.0) with the HTTP collector, Local and Cloud destinations, and protocol version 1.
  • Pathrule Local: storage, grouping and verification on your machine, the agent tools and the pathrule instrument events command.
  • Pathrule Cloud: the managed ingest pipeline, recording fixes and verifying them with the same policy as Local, envelope deduplication and automatic retention.