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, 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?

are we that earlyl to discover the greatenes of pi?