capability_changed · 2026-09-18

Suna v0.13.24 — The pi agent harness, behind a per-project flag: New A second agent harness, behind a flag.

The official v0.13.24 — The pi agent harness, behind a per-project flag release documents a concrete capabilities change. This update explains what changed from dev-latest, who should reassess the product, and what to verify next.

What changed
The official v0.13.24 — The pi agent harness, behind a per-project flag release documents a concrete capabilities change. This update explains what changed from dev-latest, who should reassess the product, and what to verify next.
Who is affected
Evaluators, administrators, and workflow owners using Suna where capabilities requirements affect adoption or deployment.
What to do now
Review the official v0.13.24 — The pi agent harness, behind a per-project flag notes, test the affected capabilities workflow, and update the adoption decision if the result changes product fit.
What changed

The material change

Previously: {{agentName}} v0.13.11 — Billing wallet floor, scoped git push, and an agent-centric Customize documents this product change: Billing No account runs on an empty wallet.

Now: Suna v0.13.24 — The pi agent harness, behind a per-project flag documents this product change: New A second agent harness, behind a flag.

This update covers the v0.13.24 — The pi agent harness, behind a per-project flag release notes and does not infer behavior beyond the official release description.

Why it matters

What users should reconsider

The move from dev-latest to v0.13.24 — The pi agent harness, behind a per-project flag introduces a documented change that may alter operational compatibility.

The release has a versioned first-party source, so teams can verify the exact scope instead of relying on a generic monitoring excerpt.

Practical next step

Verify the affected workflow

  1. Review the official v0.13.24 — The pi agent harness, behind a per-project flag notes, test the affected capabilities workflow, and update the adoption decision if the result changes product fit.
  2. Open the official source and verify the current product state.
  3. Review the current Agent Profile and affected Decision before acting.

Source-Backed does not mean execution-verified and does not establish comparative rank.

Previous state

What was recorded before

{{agentName}} v0.13.11 — Billing wallet floor, scoped git push, and an agent-centric Customize documents this product change: Billing No account runs on an empty wallet.

Current Agent state

What is known now

Suna v0.13.24 — The pi agent harness, behind a per-project flag documents this product change: New A second agent harness, behind a flag. This update covers the v0.13.24 — The pi agent harness, behind a per-project flag release notes and does not infer behavior beyond the official release description.

Accepted Change accepted:d174fedc5698ed83e4857bba0f7590de · Agent Fact fact:d174fedc5698ed83e4857bba0f7590de · Last verified 2026-09-18
Official evidence

Suna official releases

Published by Kortix. Evidence state remains Source-Backed; this is not execution verification.

Open official source →