Skip to content

v2.6.4 — Profiles Replace What They Route

Choose a tag to compare

View all tags
@Alan-TheGentleman Alan-TheGentleman released this 14 Sep 11:25
· 156 commits to main since this release
v2.6.4
7df2f2f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v2.6.4 — Profiles Replace What They Route

gentle-pi v2.6.4 is a hotfix release: applying a profile now replaces the routing of every agent instead of merging over routes an earlier apply left behind, and /gentle:profiles shows the routing the runtime actually uses even when the canonical models.json is sparse. The package-local Gentle AI runtime stays at v2.9.0.

Provenance

  • Previous stable: v2.6.3 → e00b6b1a
  • Release target: v2.6.4 → 7df2f2fb702124e50a79ecfbad6516024136c58f
  • CI workflow: run 34837704978
  • Verification: package verification (verify) and Windows review (review-repository-windows) jobs both succeeded; the npm publication ran as run 34837719624.
  • Pinned Gentle AI: v2.9.0, provider contract 1.2.0

What's new

No new features are declared for v2.6.4.

Breaking changes

No breaking changes are declared for v2.6.4.

Upgrade now

pi install npm:gentle-pi@2.6.4

Restart Pi, then run:

gentle-ai sync

This release keeps Gentle AI pinned at v2.9.0; no runtime reinstall is required.

What was fixed

Applying a profile replaces routing instead of merging over it

The runtime resolves each agent's model from ~/.pi/agent/subagents.json and agent frontmatter, never from models.json. Applying a profile wrote the profile's sparse config to models.json and skipped every agent the profile did not name, so routes materialized by an earlier apply stayed in effect while the panel reported No routing entries. Applying a profile now materializes every discoverable agent the profile omits as inherit, exactly as /gentle:models does for an agent set to inherit, and the rollback after a failed apply re-materializes the previously active profile with the same replacement semantics (closes #1012).

/gentle:profiles reflects effective routing

The current-routing pane, the seeded current profile, and the update snapshot now read the effective routing: models.json when it has an entry, otherwise the model_profiles entry in subagents.json, otherwise the agent file's model: and thinking: frontmatter. Reading never writes, so an installation whose canonical store diverged from its materialized routing can inspect the truth and capture it into a profile with s.

Included work: #1013.

Numbers

2 non-merge commits, 1 merged pull request, and 1 unique GitHub PR author since v2.6.3.

Install

pi install npm:gentle-pi@2.6.4

Package: https://www.npmjs.com/package/gentle-pi

Full changelog: v2.6.3...v2.6.4

Assets 2
Loading