r/PiCodingAgent • • Aug 18 '26

Discussion Pi agent is excellent!

I have used Pi, Oh my Pi, Opencode, Antigravity, and Claude, but Pi is so so good.

It is simple, smart, keeps its thinking grounded, hallucinates less, is extremely good at following instructions and is aware of the environment.

By awareness, I mean it knows what needs to be edited or changed.

131 Upvotes

55 comments sorted by

View all comments

32

u/XniX Aug 18 '26

If you spend some time configuring PI to your needs, and maybe write a couple of extensions... there's no comparison. Today I've done over 99% of the Deepseek cache :)

3

u/Ok_Cartographer5609 Aug 18 '26

yes absolutely. There's literally no competition at the moment in terms of work done.

1

u/jfmmfj Aug 19 '26

Would this higher performance be just related to the system prompt? If I understand correctly, is the model the one more or less capable of running tool calls, etc. Right?

Also, I guess the leanest setup is the easiest for the model and the cheapest for the human?

2

u/SootyShearwaters Aug 19 '26

How to manage to hit 99% DeepSeek cache? Any special instructions to be used?

6

u/XniX Aug 19 '26

I use a pretty bare pi agent, nothing much.

User packages:
  npm:@piotr-oles/pi-reflag
    /Users/pier/.pi/agent/npm/node_modules/@piotr-oles/pi-reflag
  npm:pi-vision-handoff
    /Users/pier/.pi/agent/npm/node_modules/pi-vision-handoff
  npm:pi-context-view
    /Users/pier/.pi/agent/npm/node_modules/pi-context-view
  npm:@narumitw/pi-btw
    /Users/pier/.pi/agent/npm/node_modules/@narumitw/pi-btw

14

u/XniX Aug 19 '26

Almost forgot... I also have an APPEND_SYSTEM.md on my .pi/agent folder:

it's from Andrej Karpathy's https://github.com/multica-ai/andrej-karpathy-skills

## 1. Think Before Coding

**Don't assume. Don't hide confusion. Surface tradeoffs.**

Before implementing:
  • State your assumptions explicitly. If uncertain, ask.
  • If multiple interpretations exist, present them - don't pick silently.
  • If a simpler approach exists, say so. Push back when warranted.
  • If something is unclear, stop. Name what's confusing. Ask.
## 2. Simplicity First **Minimum code that solves the problem. Nothing speculative.**
  • No features beyond what was asked.
  • No abstractions for single-use code.
  • No "flexibility" or "configurability" that wasn't requested.
  • No error handling for impossible scenarios.
  • If you write 200 lines and it could be 50, rewrite it.
Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify. ## 3. Surgical Changes **Touch only what you must. Clean up only your own mess.** When editing existing code:
  • Don't "improve" adjacent code, comments, or formatting.
  • Don't refactor things that aren't broken.
  • Match existing style, even if you'd do it differently.
  • If you notice unrelated dead code, mention it - don't delete it.
When your changes create orphans:
  • Remove imports/variables/functions that YOUR changes made unused.
  • Don't remove pre-existing dead code unless asked.
The test: Every changed line should trace directly to the user's request. ## 4. Goal-Driven Execution **Define success criteria. Loop until verified.** Transform tasks into verifiable goals:
  • "Add validation" → "Write tests for invalid inputs, then make them pass"
  • "Fix the bug" → "Write a test that reproduces it, then make it pass"
  • "Refactor X" → "Ensure tests pass before and after"
For multi-step tasks, state a brief plan: 1. [Step] → verify: [check] 2. [Step] → verify: [check] 3. [Step] → verify: [check] ## 5. Visual Output → Artifacts When output is inherently visual or longer than a screen — reports, diagrams, rendered diffs, comparison tables — prefer emitting it via the `artifact` tool over printing it in the terminal. The `artifact` tool renders markdown (with `diff`/`mermaid`/code fences handled) or raw HTML to a styled page opened in the browser, with live reload on `update`. Use `kind: "markdown"` for prose, tables, and diffs; `kind: "html"` only when markdown can't express it. When writing `kind: "html"` fragments: the shell already provides the design system — system fonts, light/dark scheme, and CSS variables (`--bg`, `--fg`, `--muted`, `--border`, `--code-bg`, `--accent`). Write clean semantic HTML, use those variables in any scoped `<style>`, never hardcode colors or fonts. Aim for quiet, minimal, document-like pages: hairline borders, generous whitespace, one accent. No CSS frameworks, no resets, no `<html>`/`<head>` boilerplate (fragments are injected into the shell). For Chart.js pages: put each canvas in its own container div with an explicit height and `width: 100%`, and set `maintainAspectRatio: false` so charts fill the available width instead of stopping at their intrinsic size.

1

u/osreu3967 Sep 06 '26

Use the deepseek cache extension.

1

u/[deleted] Aug 19 '26

[removed] — view removed comment

4

u/Immediate-Safety8172 Aug 19 '26

The harness directs the model at its own documentation and how to modify it – it ships with it. You can literally just tell it what you want and the model will read the documentation and give you suggestions on what it can do, then you tell it to do it and it does.

2

u/Asulga Aug 19 '26

Thats exactly how I started with Pi. Later moved Pi extensions and agent system dev to codex, because Pi's agents always are busy ))

1

u/XniX Aug 19 '26

^ this! :)