Skip to main content
Rippletide connects to agents you already run. It shows their declared instructions and tools, records runtime evidence, and evaluates business rules at the boundaries where actions or responses happen. Start by observing. Review which rules match real activity, then deliberately enable enforcement for the releases you trust. Your agent keeps its existing model provider, application lifecycle, credentials, and infrastructure.

Quickstart

Connect a JavaScript or TypeScript agent, verify a real run, and observe your first Rule.

​
Choose your connection

Using a coding agent to instrument your application and connecting Codex itself are different paths. Choose the application guide for the former and the Codex guide for the latter.

​
From evidence to enforcement

1

Connect and prove a real run

Inspect Context & actions, then confirm the required evidence in Traces. Saving credentials alone does not prove a connection.
2

Find an action worth controlling

Use the fleet, action risks, and recorded interventions to choose a concrete problem.
3

Write or propose a Rule

Start from plain English, Business context, or captured traces. Review its scope, evidence, and required setup.
4

Test in Observe

A blocking match records Would block, while the action continues. An Allow rule records an explicit allowance.
5

Enforce deliberately

An enforced blocking match must prevent the protected effect. Check the receipt to see what the caller reports actually happened.
The generic action/response dispositions are Allow, Would block, and Block. Human reviews and approvals can be recorded from your runtime; they are not a separate generic Escalate disposition returned by the policy API. Read Observe & enforce for policy behavior and Privacy & capture before choosing which content to export.