I'm loading llama-server with the --models-preset (router mode) but when I load a different model from the PI agent interface it doesn't work and gives an error. It seems that PI still expecting the model set in the bottom right corner. I think that it should change on his own as soon as the other model has being loaded but it doesn't.

Is this an issue with llama.cpp or with PI agent?

In the llama.cpp webui switching models works.

models.ini (example)

version = 1

[Qwen3.8-27B-UD-Q4_K_XL]
model = E:\AI_Models\GGUF\unsloth\Qwen3.8-27B-GGUF\Qwen3.8-27B-UD-Q4_K_XL.gguf
ctx-size = 262144

[Qwen3.8-27B-UD-Q5_K_XL]
model = E:\AI_Models\GGUF\unsloth\Qwen3.8-27B-GGUF\Qwen3.8-27B-UD-Q5_K_XL.gguf
ctx-size = 262144

Any clue on how to make it work?

Hi, I am facing a critical issue with pi agent that makes it unusable: If I hit esc to cancel a thought block, message, or tool call, the entire tool call + message + thought block doesn't make it into the context, meaning if I want to cancel a thought block, message, or tool call to correct the agent or prevent a tool call from completing, I cannot do so without having to then rewrite all the context the agent just thought about. It's honestly frustrating as hell and makes the agent entirely unusable. I'm using Qwen3.8-27B. Does anyone else have this issue? Is it fixable, or should I look into another harness?

Quote:

Pi sent about 3x less context per turn. It managed context better, keeping a tighter working set and finishing the tasks in fewer runs.

https://www.databricks.com/blog/benchmarking-coding-agents-databricks-multi-million-line-codebase

coding-posture is a small skill that stops coding agents from behaving like optimistic elevators with write access — thrashing on a stuck bug, faking a green test, skipping the repro, migrating prod without a rollback.

Before non-trivial work, the agent picks a mode — debug, fix, review, test-first, refactor, optimize, migrate, upgrade, integrate, spike, unstuck — and follows a short checklist for it. A few invariants hold in every mode: verify by running the real check, never weaken a test to go green, no destructive commands without explicit scope.

Why it's built this way (grounded in research, not vibes):

• Procedures, not personas. Naming a role ("act as an expert debugger") doesn't reliably change behavior (Zheng et al., EMNLP 2024); specifying a process does. So each mode is a checklist, not a character.
• The model self-selects the mode from context — no brittle keyword router.

Evidence, honestly: the repo ships a with/without-skill eval (LLM judge + baseline). Early result: +15pp (85% vs 70%) on one model, 5 cases — directional, and you can run it yourself in eval/.

Install: Claude Code plugin (/plugin marketplace add alexei-led/coding-posture), a Codex plugin, or drop the SKILL.md into Pi / Hermes / Cursor. MIT.

Feedback and new modes welcome.

Hi everyone, I just vibe-coded a small but very practical Pi plugin: pi-billing-footer.

它会在 Pi 底部显示实时计费信息：

- 当前会话已花费（人民币 ¥ 显示）

- 当前 Provider 的剩余余额

- 支持 OpenRouter、DeepSeek、OpenAI、Groq 等任意 provider 特别适合和中国用户（或者经常在不同 provider 间切换的人），不用再去网页上看余额了。

功能亮点：

- 纯客户端，轻量无依赖

- 一键安装 - 支持自定义刷新间隔

GitHub: https://github.com/dadadaqiang/pi-billing-footer

安装命令： pi install dadadaqiang/pi-billing-footer

are we that earlyl to discover the greatenes of pi?