runfile-ai
The Runfile SDK for Python. Tamper-evident audit capture for AI agents.
pip install runfile-ai
# framework extras:
pip install 'runfile-ai[langgraph]' # or [openai-agents], [anthropic], [mcp]
import os
import runfile_ai
from runfile_ai.integrations import langgraph as runfile_langgraph
runfile_ai.init(api_key=os.environ["RUNFILE_API_KEY"], environment="production")
graph = runfile_langgraph.instrument(
graph, agent_identity="did:web:bank.com:agents:loan-triage:v2"
)
Supported framework versions
| Extra | Framework | Supported | Notes |
|---|---|---|---|
langgraph |
langgraph |
>=1.0 |
HITL interrupt / resume capture needs 1.0+ |
openai-agents |
openai-agents |
>=0.1,<0.18 |
Capped. On newer releases (seen on 0.23.1) a human-approved tool call is captured out of order (tool_call before tool_approval_requested), which misstates human oversight in the audit trail. Also caps openai<2.42: newer openai adds a required usage field that openai-agents 0.17 doesn't set, so runs crash inside the framework. Tracked in #16. |
anthropic |
claude-agent-sdk |
>=0.1.29 |
needs the Notification / SubagentStart / PermissionRequest hooks |
mcp |
mcp |
>=1.0 |
adapter not implemented yet |
Configuration
Explicit args take precedence over environment variables, which take precedence over defaults:
| Arg | Env var | Default |
|---|---|---|
api_key |
RUNFILE_API_KEY |
— (required) |
region |
RUNFILE_REGION |
eu-west-2 |
environment |
RUNFILE_ENVIRONMENT |
from the key: rf_live_… → production, rf_test_… → non-production (the platform labels the run with the key's exact environment, e.g. sandbox) |
disabled |
RUNFILE_DISABLED |
false |
base_url is derived as https://api.<region>.runfile.ai unless overridden.
RUNFILE_DISABLED=1 makes the SDK a silent no-op (handy for local dev). So
runfile_ai.init() with RUNFILE_API_KEY set is enough.
- Import name:
runfile_ai(distribution:runfile-ai). - Wire
sdk.name:runfile-ai. - Python: 3.11+.
- Schema dependency:
runfile-ai-schemas(PyPI), pinned>=0.5,<1.0.
🚧 Scaffold — module skeletons are in place; logic is being filled in. See the repo root
README.mdanddocs/STATUS.md.
Local development
pip install -e '.[dev]'
ruff check .
mypy runfile_ai
pytest
1 maintainer
Metadata
1 maintainer
Release files for runfile-ai 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| runfile_ai-0.4.0.tar.gz | 100.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| runfile_ai-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 176.4 kB
Release files / runfile_ai-0.4.0.tar.gz
| Download URL | runfile_ai-0.4.0.tar.gz |
|---|---|
| Size | 100.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
798efc0a3063ed9d3523a5bd8efcb65b85621127b486af88fbd4126abcdbe6be
|
|
BLAKE2b-256 checksum How to use checksums |
7a66a7e970cc2ddd5c18fcbe47b5ac0788fdc973237111386e9a5e5017a646a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency logRelease files / runfile_ai-0.4.0-py3-none-any.whl
| Download URL | runfile_ai-0.4.0-py3-none-any.whl |
|---|---|
| Size | 76.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
906b1434c2c8c365d7d2b77fb55fa752d13c39b674912cc6c74cc820e9909aa6
|
|
BLAKE2b-256 checksum How to use checksums |
4721b44dd1806ca4e594b269c681cc98df0ab49020fcc73b01d45db275839e69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency logSecurity for runfile-ai 0.4.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for runfile_ai-0.4.0.tar.gz
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 Oct 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
