augur-sdk

Full docs: https://mercurialsolo.github.io/augur-sdk/

Instrument any screenshot-grounded computer-use agent (CUA) with one context manager. Streams traces to Augur (a hosted cloud service for CUA observability) over a Sentry-style DSN AND writes a path-stable bundle to disk — both work, both at once, no extra glue.

This is the public client SDK. The Augur server, viewer, and CLI are a managed cloud service — sign up at augur (URL TBD) to get a DSN. The SDK also works standalone in local-bundle mode with no account.

from augur_sdk import CaptureMode, DebugSession

with DebugSession(
    run_id="run_abc",
    client_name="myagent",
    capture_mode=CaptureMode.SCREENSHOTS,
    out_dir="/var/log/augur/run_abc",
) as session:
    pre  = session.attach_observation(step_index=0, kind="pre",  png_bytes=...)
    post = session.attach_observation(step_index=0, kind="post", png_bytes=...)
    session.record_step({
        "step_id":          "run_abc/step/0000",
        "step_index":       0,
        "step_type":        "click",
        "intent":           "Click the login button",
        "status":           "succeeded",
        "started_at":       "2026-05-19T00:00:00Z",
        "observation_pre":  pre,
        "observation_post": post,
        "action":   {"type": "click", "params": {"x": 100, "y": 200},
                     "coordinate_space": "viewport_css_px",
                     "dispatch_backend": "playwright"},
        "grounding": {"provider": "myagent", "provenance": "screenshot"},
        "verdict":   {"status": "passed"},
    })

Set AUGUR_DSN=… and the same code streams to your Augur server. No code change required to switch between local-only and hosted modes.

Install

From PyPI (when published)

pip install augur-sdk
# or
uv pip install augur-sdk

From source (today)

git clone https://github.com/mercurialsolo/augur-sdk.git
cd augur-sdk
pip install -e .
# or
uv pip install -e .

Requirements

• Python ≥ 3.11
• jsonschema, referencing, urllib3 (installed automatically)

The SDK is self-contained: JSON Schemas are vendored inside the package (augur_sdk._schema), so import augur_sdk requires no other Augur components. The Augur server, viewer, and CLI are operated as a hosted service — you only need this package on the client side (your CUA runtime).

Quickstart — three modes

1. Local-only (no server)

The default. Bundles are written under out_dir/. Use augur view <dir> from the main Augur repo to render them in the viewer, or hand the path to a coding agent.

from augur_sdk import CaptureMode, DebugSession

with DebugSession(
    run_id="run_abc",
    client_name="myagent",
    out_dir="/var/log/augur/run_abc",
    capture_mode=CaptureMode.SCREENSHOTS,
) as session:
    ...

2. Stream to an Augur server (Sentry-style)

Set one env var; nothing else changes.

export AUGUR_DSN='https://augur.example/api/v1?token=<api_key>&tenant=<tenant_slug>'

The SDK heart-beats every 15 s while a session is open so the server's connection-status indicator stays green. Each step + screenshot + event streams over HTTPS with Authorization: Bearer <api_key>. The local bundle is still written; streaming is observe-only on top.

Or pass the DSN directly:

DebugSession(dsn="https://augur.example/api/v1?token=...&tenant=...", ...)

Get a DSN by asking an Augur admin to run:

augur admin dsn-issue --tenant <your-tenant> --label <client-name>

3. Adapter pattern (existing CUA exports)

Already have a trace exporter (Mantis-style)? Write a small adapter that maps your shape to Augur records. See the adapter authoring guide.

What gets written

Every bundle is path-stable — no discovery needed:

out_dir/
  manifest.json           # envelope: schema_version, bundle_format, paths, signatures
  trace.json              # session + ordered steps[]
  AGENT.md                # coding-agent-friendly index (first-read hints, layout)
  steps/0000.json         # one StepTrace per file
  events/0000.jsonl       # decision events per step (planner / grounding / verifier / recovery)
  screenshots/0000_pre.png
  screenshots/0000_post.png
  diagnostics/findings.json   # if `augur diagnose` has been run
  schema/*.schema.json    # canonical record schemas (vendored for offline validation)

The same bundle drives the viewer, the CLI, and any coding agent. See docs/concepts/bundle-layout.md for the full normative spec.

Capture modes

The capture_mode arg controls how much the SDK writes:

Set via capture_mode=CaptureMode.FULL or AUGUR_CAPTURE_MODE=full.

Redaction

default-pii-v1 ships in the box and is applied to every bundle:

• Drops Authorization, Cookie, Set-Cookie, X-API-Key headers entirely.
• Masks token, api_key, ssn, credit_card, cvv keys.
• Regex-scrubs bearer tokens, AWS keys, JWTs, password=… patterns out of strings.
• Honors sensitive=True on a step: pre/post screenshots are dropped.

Subclass augur_sdk.RedactionPolicy for tighter rules:

from augur_sdk import DebugSession, RedactionPolicy

class StrictPolicy(RedactionPolicy):
    id = "strict-v1"
    drop_keys = RedactionPolicy.drop_keys | frozenset({"customer_email"})

DebugSession(redaction_policy=StrictPolicy(), ...)

Diagnostics

Augur ships a generic CUA rules pack you can run against any bundle:

from augur_sdk.diagnostics import RulesEngine, load_pack

engine = RulesEngine(load_pack("cua"))
findings = engine.evaluate("/path/to/bundle")
for f in findings:
    print(f["severity"], f["rule_id"], f["summary"])

Adapter-specific packs (e.g. mantis) are registered via the augur.rule_packs entry-point group; install the corresponding adapter package alongside this SDK and they appear automatically in load_pack(...).

CUA contract — what the SDK enforces

Per Augur's design invariant: runtime action selection MUST remain screenshot-grounded. The SDK doesn't enforce this at write time, but the diagnostic-rules engine and the viewer both flag DOM-derived coordinates that show up in grounding.provenance != "screenshot" and get used as runtime inputs. Tag DOM probes as provenance: dom so they stay visible as diagnostic evidence without being mistaken for the agent's real target.

Develop

git clone https://github.com/mercurialsolo/augur-sdk.git
cd augur-sdk
uv sync                 # creates .venv and installs dev deps
uv run pytest           # tests
uv run ruff check .     # lint
uv run mypy -p augur_sdk  # types

Publish to PyPI

Releases are tag-driven and run through .github/workflows/release.yml, which authenticates to PyPI via OIDC Trusted Publishing — no API token is stored anywhere.

One-time setup

1. Register the project on PyPI as a pending publisher: https://pypi.org/manage/account/publishing/

   • PyPI project name: augur-sdk
   • Owner: mercurialsolo
   • Repository: augur-sdk
   • Workflow name: release.yml
   • Environment name: pypi

2. (Optional) Pre-create the pypi GitHub Environment if you want to gate releases behind required reviewers:

   gh api -X PUT /repos/mercurialsolo/augur-sdk/environments/pypi
   

Cut a release

1. Bump __version__ in src/augur_sdk/_version.py and version in pyproject.toml.

2. Move the [Unreleased] block in CHANGELOG.md under the new version.

3. Commit, tag, push:

   git commit -am "Release v0.1.0"
   git tag v0.1.0 -m "Initial release"
   git push origin main v0.1.0
   

The tag push triggers release.yml: lint → typecheck → test → uv build → publish to PyPI via OIDC. The wheel + sdist are also uploaded as workflow artefacts.

Local build / manual upload (escape hatch)

If you need to publish outside CI (don't, normally):

uv build              # produces dist/*.whl + dist/*.tar.gz
uv publish            # uses ~/.pypirc or UV_PUBLISH_TOKEN

Where Augur lives

Augur (server, viewer, CLI, diagnostic rule packs, Mantis adapter) is a hosted cloud service — not open source. This SDK is the only component your CUA runtime needs; everything else is operated for you.

• Get a DSN / sign up: contact your Augur workspace admin, or reach out at the project email below.
• Issues for this SDK: https://github.com/mercurialsolo/augur-sdk/issues
• Schemas: vendored under src/augur_sdk/_schema/json/ in this repo.

License

Apache 2.0 — see LICENSE.