Skip to main content

PurrA

English | 简体中文

PurrA is an Agent runtime for Python and TypeScript. It coordinates model calls, tool execution, planning, context, and recoverable Runs inside your application. The application supplies its models, tools, data sources, and access rules.

1.0 release line

This source targets 1.0.3. Install matching Core and integration versions; see the changelog for Python execution and public-presentation outcomes and their scope. The durable approval contract describes the work in progress. Both SDKs have deterministic approval recovery tests for Reactive, Planned and Auto Root Runs, plus host-authorized MCP writes with durable receipts. Read-only approval observations are available. Extended recovery and real service/downstream acceptance remain unfinished. Existing capabilities and 1.x compatibility are documented in the 1.0 support guide.

See the upgrade notes and public compatibility before upgrading.

Install

Python 3.11+:

pip install purra

Node.js 22+ (ESM):

npm install purra

Core has no runtime dependencies. Model SDKs, storage, and memory integrations are available as optional packages.

Python quickstart

Provide a model gateway, a ModelRequest with the selected model's capability snapshot, and its context-window size. The gateway can come from an optional adapter or implement PurrA's ModelGateway port.

from purra.api import AgentCore, AgentPreset, InMemoryAgentAdapters
from purra.contracts import (
    AgentMessage, AgentRunRequest, DomainContext, ModelRequest, RuntimeLimits,
)
from purra.tools import InMemoryToolCatalog

async def ask(gateway, model: ModelRequest, context_window: int):
    storage = InMemoryAgentAdapters()
    core = AgentCore(
        model_gateway=gateway,
        preset=AgentPreset(
            id="assistant",
            revision="1",
            tool_catalog=InMemoryToolCatalog(()),
            runtime_limits=RuntimeLimits(max_run_generation_tokens=8192),
        ),
        run_repository=storage.runs,
        output_repository=storage.outputs,
        output_publisher=storage.publisher,
    )
    try:
        run = await core.submit(AgentRunRequest(
            messages=(AgentMessage(role="user", content="Hello"),),
            model=model,
            domain_context=DomainContext(namespace="example"),
            context_window=context_window,
        ))
        result = await run.wait()
        return result.final_response
    finally:
        await core.close()

This example stores Runs in memory. Use a persistent repository to retain them after restart. For a complete example that runs without API credentials, see local examples. For JavaScript and TypeScript, see the TypeScript guide.

Runtime capabilities

  • Runs: submit work, subscribe to committed events, cancel execution, and replay output.
  • Tools: validate arguments, enforce access and effect policies, and record results.
  • Planning: select Auto, Reactive, or Planned execution when a planner is configured.
  • Context: allocate input budgets, retrieve external data, and compress conversation history.
  • Agent trees and long tasks: delegate work and persist execution progress through repository ports.

The application chooses models and their limits, authorizes data access and tool side effects, and manages persistent storage. Retrieval sources and tool results are treated as data rather than instructions.

Budgets and recovery

ModelRequest.max_generation_tokens is an optional user ceiling for one Provider call and includes every generated token the Provider counts, including reasoning when the profile declares inclusive accounting. RuntimeLimits.max_run_generation_tokens bounds that quantity cumulatively for a Run. None means no finite cumulative ceiling. A finite budget requires reported model usage. A workflow's optional result_capacity_target_tokens is only a context-sizing and diagnostic target; it does not reduce the Provider allowance or guarantee visible output.

Recovery continues from committed checkpoints. The application must restore the same model and tool configuration and reconcile interrupted external writes before retrying them. Persistent storage alone does not make those writes replayable.

Documentation

License

MIT

Host policy composition and limits: guide.

Metadata

Release files for purra 1.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for purra 1.0.3
File Size Uploaded Provenance Actions
purra-1.0.3.tar.gz 616.0 kB With provenance Details for purra-1.0.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for purra 1.0.3
File Interpreter ABI Platform Actions
purra-1.0.3-py3-none-any.whl Python 3 none any Details for purra-1.0.3-py3-none-any.whl

Total release size: 1.1 MB

Release files / purra-1.0.3.tar.gz

Download URL purra-1.0.3.tar.gz
Size 616.0 kB
Tags Source
SHA-256 checksum
How to use checksums
a0407b1c028c4d133c0dff8606b89cc31d17c724af906b710b27f7ca6a1abd1a
BLAKE2b-256 checksum
How to use checksums
2031e838bcbace122fb597fc0d9e917c5ccd8281eb351422df861571ab45da4e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 21, 2026.

Transparency log

Release files / purra-1.0.3-py3-none-any.whl

Download URL purra-1.0.3-py3-none-any.whl
Size 460.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
74ac7ccda9afb1cda31ae86d539417030d9c79f249e25cee0ce3018c7286ff30
BLAKE2b-256 checksum
How to use checksums
bd19b1db90c8bda37d65602b8dfcd3f7f215daa4ccbc1b5e9cf74dfdbc2c98c7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 21, 2026.

Transparency log

Security for purra 1.0.3

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.

Select from 2 files

Attestation for purra-1.0.3.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 21, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page