r/PiCodingAgent

Pi high token usage?

Hey there I have installed pi since I heard a lot about that bcz of its low token usage and minimal design but I installed some packages [7 packages] (MCP adapter, context7, plan mode, todo, pi-hypa, context-mode, ask user question since every harness has these Ig) then installed some skills. Now even a single hi takes about 6-7k+ tokens. I did a college java project and it burnt tokens a lot. It burnt me around 100k+ tokens on deepseek's v4 flash model to make a database connection, creating database and table and a simple student management system where you can add, remove, view students in java.

I wanted to make pi token efficient with best possible results. If you say that I have installed too many packages then tell me how to replicate those features like other harnesses with low token usage.

reddit.com
u/Nunu_Chus — 11 hours ago
▲ 38 r/PiCodingAgent+32 crossposts

OpenSourcing TrueForge Agent harness : Expect feedback from community on the agent loop

Hey folks 👋

We just open sourced TrueForge, our vendor-neutral agent harness for building general-purpose agents.

It handles the runtime pieces that get painful quickly : context management, tool/MCP execution, subagents, sandboxing, approvals, persistent state, and more.

We also benchmarked the harness itself. With the same Opus 4.8 model, TrueForge delivered a similar solve rate at ~30% lower cost than Claude Managed Agents. Switching to an open model pushed that to ~75% lower cost on the same benchmark.

Would love feedback from people building agents.

⭐ Star the repo: https://github.com/truefoundry/trueforge

📖 Read the launch article: https://x.com/truefoundry/status/2090081376330715176

u/Upbeat_Pea8961 — 14 hours ago

Subagent extensions

Can you recommend me a simple yet configurable subagent extension? I'm currently testing `pi-subagents` but i find it slow and bloated. What are you guys using?

reddit.com
u/isus_copilul_minune — 20 hours ago

Could Pi benefit from an optional time-bound autonomous loop?

I’ve been looking at Hermes Agent’s "/goal" approach: give the agent a persistent goal, let it continue across turns, have a lightweight judge decide whether it’s done, and stop when the goal is achieved or the turn budget is exhausted.

It got me thinking about Pi:

Could this be implemented as an extension rather than a core feature?

Something like:

"/loop 30m "Fix the tests and get CI green""

The extension would manage:

  • a time/iteration budget
  • continuation decisions
  • completion checking
  • pause/stop
  • existing Pi session state

That feels quite aligned with Pi's philosophy: keep the core small, but make powerful agent behaviours possible through extensions.

Would a lightweight, time-bound autonomous loop be useful in Pi, or does this belong entirely outside the harness?

reddit.com
u/Certain_Net_3408 — 11 hours ago

Ricing pi

Hi folks,

I spent a ton of time making pi my own tailoring it for local llama.cpp server usage so much so, that I ran out of problems.

So my question for you folks is: do you rice / style your pi installations? If so, what's your favorite visual change?

Pictures much appreciated ☺️

reddit.com
u/DanielSReichenbach — 19 hours ago
▲ 19 r/PiCodingAgent+2 crossposts

Theme Picker on Herdr

Hi everyone, I’ve built a Herdr plugin to change the theme of my workspace in Herdr. I’m not sure if it’s useful, but it’s nice for a change of scenery when you’re bored of the old look.
You can add more theme pallete collor refference from Terminalcolors

This plugin is still in the testing phase, please do feel free to leave a rating and your feedback.

check on this : herdr-theme-picker

u/Qintomb — 22 hours ago

I built a /btw extension for Pi

One of my favorite features in Claude Code was /btw. After switching to Pi, it wasn't natively supported, and the third-community plugins didn't quite match what I expected, so I built my own.

https://github.com/L2ncE/pi-btw

https://preview.redd.it/r5n4tgud7akh1.png?width=2133&format=png&auto=webp&s=65ae998438a6d7eadb50281a98f0ae52f33621a1

  • Never enters the main session history or eats into its context window
  • The side agent can see the main session's messages and remembers your earlier side questions
  • Only four read-only tools (read / grep / find / ls) — it can browse the code, but has no write access
  • You can keep asking follow-ups right in the overlay

Stars appreciated ⭐️👏🏻

reddit.com
u/L2ncE — 1 day ago

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.

reddit.com
u/Ok_Cartographer5609 — 1 day ago
▲ 34 r/PiCodingAgent+3 crossposts

piodide ~ pi + pyodide + ghostty in the browser with WASM

https://daugasauron.github.io/piodide/

https://github.com/daugasauron/piodide

I just had this idea that you could just replace the bash tool in pi with python that runs on WASM, then you could run the whole thing in the browser.

Tried it and it's quite fascinating how good it is as a concept.

Everything is complete slop.

I tried GLM (code), OpenAI and moonshot providers.

daugasauron.github.io
u/PersonalityWild1379 — 1 day ago

Pi with openAI Plus plan, what is your experience

Is anyone using this setup and what has your rate limit been like for software development?

openai hyped up their GPT 5.6 luna having longer usage, is this true using Pi?

I was using Pi + DeepSeek v4 flash API plan, then decided to switch to openAI API plan and got rate limited after a few seconds.

So wondering if the same happens if you use Pi with one of their sub plans?

reddit.com

How would you implement Pi-style extensions in a Go agent?

Pi's coding-agent extensions are TypeScript modules with an in-process API:

registerTool, registerCommand, lifecycle hooks, and some TUI UI, then

hot-reload. Same language as the host.

If the host is Go (single binary), how would you get close to that?

Options I'm weighing: embed Lua/Starlark/JS, Wasm plugins, a sidecar

extension host over RPC, or accept that hooks+MCP is the ceiling.

If you've built plugin systems for Go CLIs/agents/editors: what would you

actually ship, and what would you refuse to build?

reddit.com
u/agentwyz — 1 day ago

Future of open source harness like Pi, in the war of closed ecosystems

I love Pi, period.

Problem: after the recent DS pricing changes and fall of opencode -> i have to sub GPT plus -> sooner or later, im afraid that OpenAI will follow Anthropic to block other than Codex for sub plans.

This left the title question: Does opensource harness like Pi safe for the future? Enjoying sub plan with more generous tokens from providers, or we have to rely on local llms? or we have to accept higher API pay-as-you-go pricing?

thanks!

reddit.com
u/Ok_Veterinarian_6364 — 2 days ago
▲ 108 r/PiCodingAgent+1 crossposts

Made a Pi plugin to turn AI-garbage writing into simple human language.

As title says.

I was sick of the way AI talks. Needlessly long sentences, weird words that nobody fucking uses (load-bearing, wtf).

Saw somebody make a similar plugin for claude-code, so I made a similar thing for Pi.

Edit, forgot to add the link lol: https://github.com/wtfzambo/speak-like-you-eat


FAQ: why no use i-have-adhd or caveman?

I do use them, there's 2 problems:

  1. sometimes is not as effective, especially in long contexts
  2. AI tends to forget after a while
u/wtfzambo — 2 days ago

Rate my tool/skill list? Missing anything?

npm packages

 - pi-lean-ctx — star of show. context economy: 13-token re-reads, indexed search. big win.

 - u/ff-labs/pi-fff — frecency search complements lean-ctx. fast first lookups.

 - pi-caveman — ~75% output cut. fun + real savings.

 - pi-subagents — workhorse. single + scripted multi-agent. backbone.

 - u/juicesharp/rpiv-web-tools — solid web layer. still need /web-tools key setup.

 - u/juanbenjumea/pi-dynamic-footer — live observability (TPS, context gauge, cost). better than powerline for metrics.

 - u/almegal/pi-file-browser — visual browse beats ls for structure.

 - u/narumitw/pi-goal — single-objective autonomy. pairs with subagents.

 - pi-autoresearch — experiment loop. pairs with karpathy skill well.

 - pi-session-recall — memory across sessions. low risk, read-only.

 - u/micka33/pi-karpathy-skill — always-on behavioral guardrails. cheap insurance.

 local extensions

 - handoff.ts — best one. lossless session handoff beats compaction.

 - plan-mode — read-only analysis mode. real safety value.

 - notify.ts — done-notification. practical.

 - summarize.ts — markdown summarize. handy.

 - model-status.ts — demo-grade. dynamic footer now shows model anyway. candidate to delete.

 - todo.ts — demo todo tool. likely redundant w/ built-in todo. candidate to delete.

 - snake.ts / space-invaders.ts — toys. zero cost. keep for joy.

reddit.com
u/ideamaker321 — 1 day ago
▲ 12 r/PiCodingAgent+1 crossposts

Update Recent changes that making Picot more useful as a coding-agent workspace

I’ve been hacking on Picot, a desktop app for using Pi coding agents.

https://github.com/shixin-guo/picot

When I first built it, it was mostly just a nicer way to chat with an agent inside a project. Useful, but still pretty rough.

Over the last month I’ve been adding the things I kept wishing existed while actually using it:

  • Skills page, so I can browse/install/enable skills from the app
  • a cleaner settings page for models and providers
  • thinking-level controls
  • Terminal panel
  • Git panel for checking workspace changes
  • better file support, including file icons, previews, resizable panels, and files mentions by @
  • better session history, titles, and remembered state
  • a clearer live status indicator so I can tell when the agent is still working
  • general UI cleanup so it feels less like a prototype

The main difference from a month ago is that Picot no longer feels like just “chat with an agent.” It’s starting to feel more like a small desktop workspace for agent-heavy coding: sessions, files, Git, skills, settings, and status all in one place.

I still use the terminal a lot, so I’m not trying to replace it completely. But when I have multiple projects or long-running agent sessions, having a visual place to keep track of everything has been surprisingly nice.

u/PerspectiveDowntown — 1 day ago

A few Pi extensions built from everyday use cases

I have been using Pi regularly and ended up building a few small extensions for things I wanted in my own workflow.

Mind Queue : Save a thought without interrupting the session.
https://github.com/sanif/pi-mind-queue

Turnstamp : Shows when an agent response finished and how long it took
https://github.com/sanif/pi-turnstamp

Chat Summary : Keeps a short rolling conversation summary
https://github.com/sanif/pi-chat-summary

Chat Suggest : Suggests a useful next message in the prompt editor
https://github.com/sanif/pi-chat-suggest

Chat Summary and Chat Suggest were inspired by features I liked in Claude Code. The others came from small annoyances I kept running into.

They’ve been useful for me, so I cleaned them up and published them. Feel free to try them or share feedback.

u/encodedhuman — 2 days ago
▲ 29 r/PiCodingAgent+1 crossposts

New agentic benchmark: Session-Bench compares what 10 coding harnesses preserve after the work is done

SWE-bench measures whether an agent completed the task. Session-Bench measures what the harness preserved afterward.

Every coding run leaves behind a session record: prompts, decisions, tool calls, command output, costs, failed approaches, reasoning summaries, and subagent work. After hundreds of sessions, that record becomes part of the project's history.

But coding harnesses preserve it in radically different ways.

I built Session-Bench after encountering these differences while developing a local session browser. It compares 10 CLI session formats across 19 practical gates covering completeness, readability, stability, openness, and tooling.

Some findings:

- The same small probe produced a 1.5 KB session in Pi and roughly 101 KB in Kimi Code.

- Only Pi, OpenClaw, and Kimi Code stamped a true session-format or protocol version.

- Some harnesses preserve readable reasoning or summaries. Others store sealed reasoning, signatures, or no rationale.

- Some record estimated dollar cost; others preserve only token counts.

- Several formats are readable today but offer no stable contract for tools that need to read them tomorrow.

Pi currently scores 18/19, OpenClaw 17/18, and Claude Code and Codex tie at 12/18.

This is not a coding-quality ranking or a recommendation to choose one harness over another. It is a report card for an overlooked part of coding-agent infrastructure: whether the resulting work history remains useful, inspectable, and portable.

The benchmark has limitations. It covers CLI session stores, not complete desktop or IDE behavior. Observation windows vary, and some measurements could not be completed. The raw probe artifacts are not publicly archived yet, so v0.3 is documented and mechanically scored but not fully independently reproducible. Copilot's documentation verdict is also marked as disputed.

I created and maintain the benchmark. I'd especially like feedback on the standard itself: what should a responsible coding-agent work record preserve, and which of the 19 gates would you change?

https://jazzyalex.github.io/agent-sessions/bench/?campaign=reddit&ref=r-chatgptcoding-discussion-v03

Moderator note: This standalone informational/discussion post was approved in advance by the r/ChatGPTCoding moderation team.

u/jazzy8alex — 2 days ago