Repository navigation
Releases
rupi v0.2.2
Release v0.2.2
rupi v0.2.2 is the installation and first-task experience release, published on
2026-09-20.
Highlights
- Added checksum-verified
install.shfor Linux/macOS andinstall.ps1for Windows. - Added release archives for Linux x86_64, macOS Intel, macOS Apple Silicon, and Windows
x86_64, with SHA-256 sidecars. - Added a tag-driven GitHub Actions release workflow so future tagged releases publish
the archives used by the installers. - Added the Test Ledger live example: a small dependency-free Python project with an
independent subprocess acceptance oracle and a manual walkthrough covering safe
inspection, bounded edits, trace, and replay. - Kept source installation available through
cargo install --path . --lockedfor
platforms without a published archive.
Verification
The release branch was checked with:
cargo fmt --all --check
cargo check -p rupi-core --all-features
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
cargo doc --workspace --no-deps
mdbook build book
bash bench/startup.sh --json bench/results/startup-ci.json
The installer scripts were syntax-checked locally, the Windows installer was exercised
against a published release archive, and the Test Ledger unit and subprocess acceptance
suites passed independently.
Upgrade note
Existing rupi sessions and configuration remain compatible. The installers only place or
replace the rupi executable; they do not alter .rupi-state, project files, or shell
configuration unless PowerShell is invoked with -AddToPath.
rupi v0.2.1
rupi v0.2.1
rupi v0.2.1 is the first release under the rupi project identity. It is an independent
coding harness with selected Pi ecosystem compatibility; it is not a Pi rewrite or Rust port.
Highlights
- Renamed the repository, binary, Cargo packages, URLs, CI commands, state/config examples,
and public documentation torupi. - Refreshed the beginner path around the supplied llama.cpp server at
http://127.0.0.1:8000/v1, modelqwen3.8-flash-next, native reasoning, and a 262,144-token
context window. - Fixed the cancellable HTTP relay so strict local servers receive a valid HTTP request line.
- Added durable trace/replay examples and screenshots based on a real local-model read-only run.
- Archived resolved audit rounds and the stale handoff without deleting historical evidence.
- Kept
import-pias the documented Pi-session import command while acceptingimportas a
compatibility alias.
Compatibility
Existing sessions and configuration are not silently migrated. Update scripts to call rupi and
use .rupi-state; upstream compatibility paths such as .pi, .pi/skills, and Pi JSONL session
files remain unchanged.
Verification
The release branch passed:
cargo fmt --all --checkcargo check -p rupi-core --all-featurescargo clippy --workspace --all-targets -- -D warningscargo test --workspace(all workspace suites)cargo doc --workspace --no-depsmdbook build bookbash bench/startup.sh --json bench/results/startup-ci.jsonbash bench/render.shcargo package --workspace --allow-dirty
The supplied local Qwen endpoint also completed the provider example, a read-only rupi run
that invoked read, and read-only trace/replay inspection. No credentials, model files, or
session state are included in this release.
pi-rs v0.2.0 — Audited Durability and Recovery Release
Release v0.2.0
pi-rs v0.2.0 is the audited durability and recovery release, published on
2026-09-19. It packages the mainline after nine audit rounds and the Round 9
sign-off: no P0 or P1 findings remain from that cycle.
What changed since v0.1.0
Crash-safe sessions and recovery
- Session leases, legacy-store migration, checkpoint projections, and model-visible
message reconstruction now recover conservatively across interruption. - Externalized assistant/tool payloads restore through their durable references.
- Interrupted or decoded-but-unexecuted tool calls close their projection lifecycle;
uncertain mutating work remainsUnknownand is never blindly replayed. - Canonical trace, semantic session state, WAL intents, blobs, and checkpoint capsules
remain separate and inspectable.
Bounded transports and cancellation
- Provider and MCP relays use bounded, cancellable request paths.
- DNS resolution uses one process-wide worker plus one queued job, so a wedged platform
resolver cannot create unbounded detached threads. - HTTP/MCP interruption fails closed and preserves exact request identity and parentage.
Safety and portability
- Filesystem confinement, symlink checks, output limits, redaction, cancellation, and
Windows handle behavior received additional regression coverage through the audit cycle. - The runtime preserves explicit failure, refusal, and
Unknownstates instead of
turning missing evidence into a success or an observed failure.
Documentation and release metadata
- Workspace crates are versioned as
0.2.0. - The release provides an
x86_64-pc-windows-msvcbinary archive with a SHA-256
sidecar; other targets can use the Cargo source build. - Public guides now use the current configuration schema, CLI flags, event vocabulary,
storage layout, MCP activation flow, and provenance rules. - The release includes the Round 9 audit report and refreshed schema/compatibility
references.
Verification
The release branch runs the repository checks required by CI and the release checklist:
cargo fmt --all --check
cargo check -p pi-rs-core --all-features
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
cargo doc --workspace --no-deps
mdbook build book
bash bench/startup.sh --json bench/results/startup-ci.json
Observed on the release host (Windows, 2026-09-19):
- Startup: cold median
120.68 ms(fresh-inode mode), warm median6.71 ms. - Keystrokes: worst measured case
35.83 us; rendering: worst case3.42 us. - Restore: 1,000 turns with checkpoints in
3.06 ms.
Benchmark numbers are host-dependent. The repository documents budgets and keeps the
command output as the evidence rather than treating one machine's result as a promise.
Known boundaries
- Node/TypeScript extensions remain an explicit optional host and require Node 22.6+.
- MCP long-lived server push remains deferred; stdio and bounded Streamable HTTP POST
activation are supported. - Remote package/dependency installation, full custom Pi TUI widgets, telemetry, and
automatic reconstructed-rationale production remain outside this release. - Windows CI is supported by the workspace's portability tests, while the hosted CI
matrix still runs on Linux, macOS, and Windows according to the workflow configuration.
pi-rs v0.1.0 — Minimal, Pi-inspired Coding-Agent Runtime in Rust
Release v0.1.0
We are proud to announce the v0.1.0 release of pi-rs—a minimal, Pi-inspired coding-agent runtime implemented in Rust.
What is pi-rs v0.1.0?
pi-rs v0.1.0 delivers a standalone, high-performance runtime for autonomous pair programming and coding agent execution. Designed from the ground up to respect honest provenance, observable execution, and low-latency interaction, pi-rs establishes a robust foundation for modern AI workflows.
Core Capabilities Delivered
1. Minimal Core Runtime & Confinement
- One-Shot Runner (
pi-rs run): Execute durable coding agent turns with clear stream separation (stdoutfor assistant prose,stderrfor transcript and diagnostics). - Interactive TUI (
pi-rs interactive): High-efficiency terminal interface with multi-line editing, semantic statusline, and real-time streaming. - Safety Boundary: Strict workspace confinement root (
--cwd) and explicit refusal of unapproved mutating operations (write,edit,exec).
2. Observable Event Store & Replay
- Canonical Event Store: Append-only
trace.jsonlrecording typedAgentEventlifecycle events. - Deterministic Replay (
pi-rs replay): Re-render past sessions without re-running tools or sending network requests. - Event Inspection (
pi-rs trace): View structured, chronological logs of agent turns.
3. Honest Reasoning Provenance
- Explicit attribution for thinking streams:
[native reasoning]: authentic model thinking tokens.[provider summary]: provider-generated summaries of hidden reasoning.[declared]: explicitly declared rationale.[reconstructed]: post-hoc recovered explanations.
- Never conflates hidden chain-of-thought with exposed reasoning.
4. Resilient Fault Recovery
- Configurable primary and backup model providers.
- Lazy backup initialization (costs zero if unused).
- Capability pre-validation for tool calling, modalities, and context window limits.
5. Pi Ecosystem Compatibility
- Skills: Discover user and project skills with explicit
--projecttrust verification. - Prompts: Discover and expand parameter-substituted templates.
- Packages: Manifest discovery and local package installation.
- Session Migration: Bidirectional
importandexportbetweenpi-rsand Pi JSONL formats with transparent diagnostics for non-round-trippable attributes.
6. Model Context Protocol (MCP) Client
- Lazy stdio worker client architecture for external tool integration.
7. Verified Performance Baselines
- Warm startup: < 1 ms (measured 0.35 ms).
- Cold startup: < 250 ms (measured 0.80 ms).
- TUI keypress latency: < 16 ms (measured < 2 ms).