pi-optimizer

A Pi extension that keeps your coding agent's context focused on the task.

In a long session, the model's context fills up with tool output that has stopped being useful: files read more than once, search results padded with surrounding lines, and failed commands. That clutter costs tokens and can pull the model's attention away from the code that matters. pi-optimizer cleans it up automatically and helps the agent read only the code it needs.

It is also built into surgent.

Install

pi install npm:pi-optimizer
pi list

Then start or restart Pi in your project. Everything below works automatically; there is nothing to configure.

The first time you start Pi in a Git repository with supported code, pi-optimizer asks to download code parsers for the languages it finds. Your answer is remembered for that repository.

Using surgent? pi-optimizer is already included. Do not install it separately, or the same tools will be registered twice.

How it saves context

Your session history is never rewritten. pi-optimizer formats tool output more compactly as it is produced, and trims what the model sees on later requests.

Read code by structure, not by file

Agents often read a whole file to find one function. pi-optimizer gives the agent an outline first: the functions, classes, and methods in a file or folder, with the lines where each one lives.

src/web-tools/web-fetch/helpers.ts
  [deps] imports~1
  [public func] toCanonicalUrl L10-L17
  [public func] getValidatedUrl L52-L66

From the outline, the agent can fetch just the function it needs, or only its signature, instead of the whole file. Folder outlines skip files excluded by your .gitignore.

The agent uses this through the code_map and inspect tools. Supported languages are TypeScript, JavaScript, Python, Go, Java, and Rust.

Compact command output

When a command prints a run of lines that differ by a single value, those lines are merged into one. This output:

request /health returned 204
request /health returned 404
request /health returned 500

reaches the model as:

request /health returned {204, 404, 500}

Nothing is lost: the merged line keeps every value in order, and output is merged only when that makes it shorter.

Grouped search results

Search results are grouped under each file instead of repeating the file path on every matching line. These results:

src/server.ts:12: const port = readPort();
src/server.ts:40: server.listen(port);
src/config.ts:8: export function readPort() {

reach the model as:

src/server.ts
12: const port = readPort();
40: server.listen(port);
src/config.ts
8: export function readPort() {

Clean up after each turn

Once the model has seen a result and moved on, some of it stops being useful. After each completed turn, pi-optimizer tidies up results from earlier turns:

• Failed tool calls are removed, together with the call that produced them. Failed shell commands are kept, because their errors are often still relevant.
• File searches and directory listings that found nothing are removed.
• Search results keep their matching lines but drop the surrounding context lines.

Results from the turn that just ended are always left intact. Cleaning up only one turn behind lets your model provider keep reusing its cached copy of the rest of the conversation, which keeps requests faster and cheaper.

Skip outdated file contents when you resume

When a session starts or resumes, pi-optimizer looks back through the conversation, up to the last compaction, for file contents that have gone stale:

• If a file was later rewritten or read again in full, earlier reads, edits, and writes of that file are hidden from the model.
• If the agent looked up the same function more than once, only the latest lookup is kept.

This check runs when the session starts. Changes made during the session are picked up the next time you resume it.

Requirements

• Node.js 22.19 or newer
• Pi
• npm, to download code parsers

License

MIT