Skip to content

consort 0.6.0 — Gemini backend

Choose a tag to compare

View all tags
@siimvene siimvene released this 04 Sep 15:17
· 24 commits to main since this release
v0.6.0
3688bff
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Adds a first-class Gemini (Vertex AI) backend as a cross-vendor peer to Codex, chosen at will with CONSORT_BACKEND=codex|gemini. Both are non-Anthropic, so either satisfies the cross-vendor axis when the principal is Claude.

Added

  • scripts/consort-backend.sh — backend dispatcher (consort_impl_call / consort_backend / consort_impl_model / consort_impl_probe). codex-backend.sh and gemini-backend.sh are peer modules; the caller scripts source the dispatcher. Default (Codex) behavior unchanged.
  • scripts/gemini-backend.sh — reaches Gemini on Vertex AI via ADC (gcloud/WIF), no API key. Full parity with Codex: reviewer and implementer (workspace-write edits files). Two transports (CONSORT_GEMINI_TRANSPORT=cli|api): the gemini CLI (@google/gemini-cli) run in the workdir for repo-aware review and edits, and a stdlib generateContent companion as a diff-only, read-only CI fallback. Plus a liveness probe.
  • Config: CONSORT_GEMINI_MODEL (default gemini-3.1-pro-preview), CONSORT_GEMINI_LOCATION (global, or a region for data residency), CONSORT_GCP_PROJECT.

Changed

  • consort-review.sh, consort-consult.sh, consort-delegate.sh now honor CONSORT_BACKEND via the dispatcher.

Self-reviewed through consort's own Gemini backend (Codex was unavailable); the review's findings — a workspace-write blast-radius bug, an ARG_MAX risk, and backend/token hardening — were fixed before merge.

Assets 2
Loading