Back to selected work

Developer tooling · 2026

Forge for Pi

Same four tools. Better engineering underneath.

Forge adds host-side safeguards, context efficiency and observability around Pi without adding tools, skills, commands, prompt text or model-facing messages.

Version
Forge for Pi v1.0.2
Target
Pi coding agent · verified on 0.84.4
Model-facing tools
read · bash · edit · write
License
MIT
Forge for Pi workflow shown on a MacBook in an editorial technical photograph.

Core principle

Improve the environment, not the interface seen by the model.

Plain Pi keeps its normal four-tool surface. Forge either replaces host-side implementations of existing tool slots or observes lifecycle events. If Forge is disabled, plain pi remains vanilla.

read
bash
edit
write

Components

Six layers, all host-side.

Smart Read

Returns a compact structural view for eligible large source files while exact ranges remain available through the normal read tool.

Safe Snapshot Edit

Adds scoped snapshots, seen-range validation, stale protection, a no-op guard and atomic edits without introducing a new tool.

Reactive Diagnostics

Appends newly introduced local diagnostics after writes, with the first release focused primarily on Python and Ruff.

Context Intelligence

Conservatively packs large prior tool evidence host-side when doing so materially saves context.

Task Progress Monitor

Shows the observed lifecycle state Understand → Work → Finalize plus measured average output speed when Pi exposes final token usage.

Optional Telemetry

Writes local metadata-only measurements only when tracing is explicitly enabled.

Host-side workflow

The model keeps working as if Forge were not there.

Forge stays behind Pi’s normal interface. The model still calls read, bash, edit and write; Forge strengthens selected host behaviors and renders local status without injecting hidden instructions into model context.

Forge for Pi used inside a coding workflow.

Measured benchmarks

Evidence where it exists. No global performance claims.

Forge reports only measurements recorded in the public benchmark and validation files. Results belong to their specific test scope and are not presented as universal improvements.

−25.90%
Smart Read input tokens

Specific Smart Read benchmark only.

−39.14%
Smart Read returned bytes

Specific Smart Read benchmark only.

2 / 2
Real stale edits blocked

Snapshot Edit stale-protection evaluation.

0
Model-facing token overhead

Task Progress Monitor.

Snapshot Edit measured about +1.0% token overhead versus vanilla in its benchmark and avoided one false stale result. Reactive Diagnostics detected and corrected 1/1 introduced Python error with 0 false positives in the available tests.

Architecture

One extension entrypoint. No new model-facing surface.

The extension activates only when FORGE_FOR_PI=1. Components either replace an existing host implementation or observe lifecycle events; the component guard prevents duplicate registration.

Pi model
  │
  ├─ read
  ├─ bash
  ├─ edit
  └─ write
      │
      ▼
Forge host layer
  ├─ Smart Read
  ├─ Safe Snapshot Edit
  ├─ Reactive Diagnostics
  ├─ Context Intelligence
  ├─ Task Progress Monitor
  └─ Optional local telemetry

No new tools · No hidden prompt · No model-facing messages
Forge for Pi host-side workflow shown in a terminal environment.

Task Progress Monitor

Observed lifecycle state, without fake precision.

The one-row TUI intentionally avoids completion percentages, ETA, hidden checks or recovery counters. Reads and inspection stay in Understand; a direct edit or write moves the row to Work. Final average tok/s is shown only when Pi exposes finalized output-token usage.

UnderstandWorkFinalize

Installation

Opt-in, reversible and local to the user.

The installer copies the extension into Pi’s user extension directory, creates Forge-managed launchers in ~/.local/bin and leaves unrelated Pi configuration untouched.

Download v1.0.2
  1. Download forge-for-pi-v1.0.2.tar.gz.
  2. Extract the archive and run ./scripts/install.sh.
  3. Run ./scripts/verify-install.sh.
  4. Launch with Forge; use Forgetrace only for optional local telemetry.

Optional trace

Telemetry is off by default.

FORGE_FOR_PI_TRACE=1 enables local metadata-only measurements. Forge does not collect tool content, CPU/RAM data or process lists in this release.

Design safeguards

Fail open. Stay reversible. Do not hide prompting.

Unsupported files, unavailable diagnostics and host-processing errors preserve native Pi behavior. Forge adds no skill, system prompt, prompt template or model-facing message.

License

Open source under MIT.

Forge for Pi is released under the MIT License. It is an independent project and is not affiliated with or endorsed by Pi’s maintainers.

A better environment around the same four tools.

Forge for Pi v1.0.2 is available as a public release and remains intentionally opt-in.