Skip to content

v2.4.0 — Gemini-CLI host removal (paired with toolkit v0.9.0)

Choose a tag to compare

View all tags
@alexherrero alexherrero released this 18 May 00:04
· 378 commits to main since this release
v2.4.0
fea2747

Minor — host-scope reduction paired with agent-toolkit v0.9.0. Drops standalone Gemini CLI as a supported host across the personal-dev-env. Keeps Claude Code + Antigravity (Gemini-in-Antigravity is a different surface — IDE-level integration, not standalone CLI).

Why this shape

Harness-side changes for this release pair are doc-only. The harness hasn't owned customizations since the v2.0.0 split (when dependabot-fixer + ship-release migrated to agent-toolkit); the customization sweep happens entirely on the toolkit side. The harness's role in plan #15 is acknowledging the host-scope reduction in its docs + framing the paired release.

Decision rationale lives in toolkit-side ADR 0006 — no new harness-side ADR (the host-scope decision is a toolkit-side concern; harness inherits via its dependency on toolkit customizations).

What's new (harness side)

Added

  • wiki/reference/Completed-Features.md v2.4.0 overview row + full narrative section (Commit range / What shipped / Why this shape / Doesn't do / Tracked as / Related — mirrors v2.3.x format).

Changed

  • Adapter wrappers untouched — canonical-reference inheritance: adapters point at harness/phases/ specs which are themselves untouched.
  • No changes to harness phase specs (no host-related conditionals — phases don't reference specific hosts by name; host scope is decided by toolkit-side manifests).

Internal

  • Paired-release-as-documentation pattern: when the substantive change lives entirely on one side of the toolkit/harness split, the other side still ships a paired release with framing-only content. This keeps the two repos' version cadences readable for operators tracking changes. v2.4.0 is the documentation-acknowledgement counterpart to v0.9.0.
  • First post-#15 install on harness side: operators who run bash agent-toolkit/install.sh against an agentic-harness install will see the legacy-cleanup prompt fire if .agents/skills/ exists from a prior install. The harness's --update path (separate from toolkit's --update) is unaffected — harness doesn't manage .agents/.

Migration

No harness-side migration required. The legacy-cleanup-with-confirmation operator UX is handled by agent-toolkit/install.sh v0.9.0+ — see toolkit v0.9.0 release notes + ADR 0006.

Full changelog

CHANGELOG.md

Assets 2
Loading