Tide Runtime SDK
Python SDK for wrapping production agent tools with Tide policy, approvals, and earned-use logging.
Recommended from an agent repo:
npx -y --package rippletide-package@latest tide run
That command creates a local .venv, installs tide-runtime inside it, scans Python
and Node/JS agent code, lets you pick decisions for risky tools, and writes wrappers plus
.tide/ledger/policy.json in one terminal flow.
Omit --pack for baseline; add --pack support-refunds for refund agents.
Python-only install:
python3 -m venv .venv
source .venv/bin/activate
pip install -U tide-runtime
tide run --pack support-refunds
For a non-interactive install, use tide run --pack support-refunds --yes.
tide init --dry-run --pack <name> prints the policy before writing it.
Built-in packs: baseline, support-refunds, sql-analyst, mcp-baseline.
To have Tide suggest wrappers for an existing Python or Node/JS agent:
tide scan --path . --pack support-refunds
$EDITOR .tide/tide-plan.json
tide apply --interactive --write-policy
--interactive shows each proposed tool wrapper with its file, function, inferred tool name,
risk class, captured fields, and runtime decision. Press enter to accept the suggested
decision, or type allow, log, escalate, or deny (block) to write an explicit
per-tool policy override. Use tide apply --yes --write-policy to accept the reviewed plan
non-interactively.
from tide import configure, controlled_tool, record_outcome
configure(agent_id="crm-agent", workflow_id="lead-sync", environment="prod")
@controlled_tool(name="crm.update_lead", risk_class="internal_write", capture=["lead_id"])
def update_lead(lead_id, status):
return {"lead_id": lead_id, "status": status}
try:
update_lead("L-1", "qualified")
record_outcome("success")
except Exception:
record_outcome("failure")
raise
Default files live in .tide/ledger/. Override with TIDE_LEDGER_DIR or
configure(project="...").
tide approvals
tide approve <id>
tide deny <id> --reason "not in scope"
tide report
Release files for tide-runtime 0.2.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tide_runtime-0.2.11.tar.gz | 24.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tide_runtime-0.2.11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 46.5 kB
Release files / tide_runtime-0.2.11.tar.gz
| Download URL | tide_runtime-0.2.11.tar.gz |
|---|---|
| Size | 24.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
09b8b4ddeffa3e272a324d33e5691772f4036ad52d0c87c7d6288b0cb847f1fe
|
|
BLAKE2b-256 checksum How to use checksums |
3504706d6f90e1d39dc6016b48b5a6614401c1ddb721909650cea3a04cdfe79f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 8, 2026.
Transparency logRelease files / tide_runtime-0.2.11-py3-none-any.whl
| Download URL | tide_runtime-0.2.11-py3-none-any.whl |
|---|---|
| Size | 22.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c0744db836e8d63697ae239f115d7b7a932a34fa4a44250cab4fc9e1bd360c8e
|
|
BLAKE2b-256 checksum How to use checksums |
8917bf42da88e5035ecf64777900b20fc3a62a7779dfb435bc431910c3bea727
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 8, 2026.
Transparency log