Skip to content

PASR v0.3.0

Choose a tag to compare

View all tags
@Apheironn Apheironn released this 04 Oct 09:14
· 11 commits to main since this release
v0.3.0
9cebfda
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

PASR 0.3.0: local, token-budgeted, source-traceable context for coding agents.

What ships

  • Rendered-context budget enforcement, coherent source fingerprints/line provenance, strict UTF-8/BOM/newline handling, and revision-pinned Git review inputs.
  • Default MCP catalog: find_files, find_symbols, find_evidence, find_usages, select_context. Optional tracing, receipts/packs and split search/read exposure remain explicit.
  • Shell-safe headless CI action; clean wheel/sdist CLI and real MCP stdio validation across Linux/Windows and Python 3.10/3.12.
  • A runnable isolated Codex demo and observed website transcript. The maintained driver completed with two model-selected PASR calls and checked source citations; its 364 selected tokens are not its 50,545 host input tokens.
  • Published evaluation records retain failed quality/cost gates. Five workstation-identifying records use labeled public derivatives; their frozen local originals were not altered.

Upgrade boundaries

  • Receipt/pack format 2 replaces format 1: regenerate old persisted selections/packs. Source cache format changes are not a model-quality claim.
  • Requests are independent: the server does not own a host question lifecycle, global tool-call budget, or global audit of everything an agent saw.
  • The opt-in search_code tool discovers/selects by query; use read_code(query, files) for known paths/ranges. Removed scope arguments are rejected rather than silently widening the request.
  • Ordinary select_context is capped at 1,500 rendered-context tokens, not total MCP/API tokens. Computed spans may be partial. Compact split tools do not persist receipts or append ledger entries.

Evidence and limits

This is not a claim of better general answer accuracy or lower total API cost than competent native grep/read. The untouched 40-task comparison's gate failed; subsequent reused-question results are exploratory. Local selection does not stop a client forwarding source to a cloud model, and default redaction is a no-op.

Real-client records: https://github.com/Apheironn/pasr/blob/main/eval/agent_bench/client_demo_20261004.json
Reproduction: https://github.com/Apheironn/pasr/blob/main/scripts/demo_client.py
Full changes: https://github.com/Apheironn/pasr/blob/v0.3.0/CHANGELOG.md

Distribution channels

The attached wheel/sdist were promoted unchanged from green CI and are now also published on PyPI with matching SHA-256 values. The manual publish-pypi workflow verified these exact files before Trusted Publishing. The matching MCP Registry entry is active.

Install from PyPI:

python -m pip install pasr-mcp==0.3.0

Or launch the pinned MCP server without a checkout:

uvx --from pasr-mcp==0.3.0 pasr-mcp --workspace /absolute/path/to/project

Install the GitHub wheel:

python -m pip install https://github.com/Apheironn/pasr/releases/download/v0.3.0/pasr_mcp-0.3.0-py3-none-any.whl

Verified revision and artifacts

Commit: 9cebfdaef67cc8332c1bc5a4db6b39887807fa60

CI: https://github.com/Apheironn/pasr/actions/runs/37191283736 — all six jobs passed.

SHA-256:

b43dbc2cc95aa57b3630263d1256e36158eedb0a76cb396c280377c2d45afdd8  pasr_mcp-0.3.0-py3-none-any.whl
22bba7dbe0df438249d2ebf607409109379ec4c5c5aecc25599a64a0c056ea4c  pasr_mcp-0.3.0.tar.gz

Post-publication verification

Both the public GitHub wheel URL and PyPI pasr-mcp==0.3.0 were installed into separate fresh Windows/Python 3.12 environments. The installed CLI and real default/split MCP stdio smoke passed, including receipt/budget checks and rejection of paths outside the workspace. GitHub and PyPI artifact SHA-256 values match the CI files listed above.

PyPI workflow 37191531085, attempt 3 succeeded after the maintainer configured the Trusted Publisher. The first two attempts failed with invalid-publisher; those failures are retained in the workflow history. The PyPI 0.3.0 metadata now returns the published wheel and sdist.

The documented pinned uvx command also passed a real MCP client smoke using a fresh uv cache and a workspace path containing spaces: all five default tools, symbol lookup and source-backed selection, with 24 context tokens under a 180-token budget.

MCP Registry

The official version endpoint returns io.github.Apheironn/pasr version 0.3.0, status active, PyPI pasr-mcp==0.3.0, stdio transport and the required --workspace argument. The unchanged manifest passed official publisher validation before publication on 2026-10-04. Registry metadata is not a claim of GUI-client compatibility or independent adoption.

Maintenance instructions: PyPI publishing and MCP Registry publishing.

Assets 5
Loading