Skip to content

Node-based terminal manager for AI coding agents — tmux-backed terminals and parallel agent sessions as draggable nodes on an infinite pan/zoom canvas. macOS, Linux, and a browser Server Edition.

docs(gemini): record the personal-account retirement and the node banner

reviewf03c6540d52f
diff --git a/CLAUDE.md b/CLAUDE.md
index 21f9aede2..3b4c0d029 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -1901,6 +1901,15 @@ else, and its context links must keep classifying across restarts).
because `/quit --delete` exits *and permanently deletes* the session history, i.e. exactly what the
restart exists to resume (pinned by its own test).
Full picture, measurements, gaps and a device checklist: **`docs/gemini-agent.md`**.
+- **Gemini CLI refuses personal Google accounts since 2026-06-18** (free / AI Pro / AI Ultra moved to
+ Antigravity CLI — the `antigravity` agent above; Code Assist Standard/Enterprise, Vertex AI and paid
+ API keys still work, so `gemini` stays a builtin). The refusal happens before any session, so no
+ hook reports it: a gemini-harness node reads its own pane for the CLI's sentence
+ (`renderer/terminal/gemini-retired.ts`, letters-and-digits match because the TUI wraps it in a
+ box) and raises a slim banner — "Open Antigravity" (`nodeterm:open-agent`, an agy node beside it,
+ in its frame) + Google's migration guide. It types and relaunches NOTHING, which is why a phrase
+ match is enough here where `resume-fallback.ts` needs three refusals. `AgentConfig.notice` carries
+ the one-line caveat to the menus/Dock tooltips; it is never read to decide behaviour.
- **Claude session context capacity (#818)** — the managed hook reports only
`CLAUDE_CODE_MAX_CONTEXT_TOKENS` from the effective Claude process environment (including
`--settings` env), never the GUI/server process environment. HookServer validates decimal safe
diff --git a/docs/gemini-agent.md b/docs/gemini-agent.md
index 0b5f723e3..753fa2208 100644
--- a/docs/gemini-agent.md
+++ b/docs/gemini-agent.md
@@ -17,6 +17,22 @@ parsing output.
> `~/.gemini/tmp/nodeterm/chats/session-2026-08-09T10-48-fd01438b.jsonl` on this host). The few
> genuinely open items are marked *unverified* and collected in §7–§8.
+> **Personal Google accounts can no longer use Gemini CLI (since 2026-06-18).** Google moved the
+> terminal experience to **Antigravity CLI** (`agy`, closed source; nodeterm's `antigravity` agent —
+> `docs/antigravity-agent.md`) and Gemini CLI now refuses the free tier, Google AI Pro and Google AI
+> Ultra (announcement: google-gemini/gemini-cli discussion #27274). Gemini Code Assist
+> Standard/Enterprise licences, Vertex AI and paid Gemini API keys are unaffected, so the `gemini`
+> agent stays — existing nodes must still load, and those users still run it. What a refused user
+> sees is the browser saying "Authentication succeeded" and then the CLI's sign-in screen again,
+> with `This client is no longer supported for Gemini Code Assist for individuals. To continue using
+> Gemini, please migrate to the Antigravity suite of products` (captured from a user's screen,
+> 2026-09-28). Reinstalling or deleting `~/.gemini` does not help. nodeterm names it in two places:
+> `AgentConfig.notice` (the tooltip wherever gemini is offered) and a slim node banner raised when a
+> gemini-harness pane prints that sentence (`renderer/terminal/gemini-retired.ts`) — the one place
+> this agent reads its output, because the refusal comes before any session and so before any hook.
+> The banner types nothing; it offers an Antigravity node beside this one and Google's migration
+> guide.
+
---
## 1. What gemini is, capability by capability