`opencode` `v1.15.6` adds TUI diff review and shell mode

// related

• #0001

  #0001Agents & toolsGoogle AI Forum3 hours ago

  `Antigravity 2.0` upgrade breaks IDE workflow for existing users

  60radar

  AntigravityCoding agent IDE — Google’s agent-first dev tool

  A forced product split turned one workflow into IDE, agent-only app, and CLI. Co-install bugs, session hijacking, blank marketplaces, and faster credit burn make this upgrade risky.

  • —The old app was split into Antigravity IDE, agent-first Antigravity, and Antigravity CLI; users were pushed into the agent-only path instead of the matching IDE upgrade.
  • —Antigravity 2.0 and Antigravity IDE 2.0 reportedly cannot coexist, creating a packaging failure that blocks normal migration.
  • —Session hijacking prevents the IDE from opening after install, while Gemini support gives 1.x-era fixes and can burn credits before solving anything.
  • —Marketplace loading can fail after install because requests trigger rate limits, leaving extensions blank or throwing unknown errors.

  Source: discuss.ai.google.dev/t/my-antigravity-is-broken-the-2-0Read original →
• #0002

  #0002Agents & toolsGeekNews3 hours ago

  `Gemini CLI` will stop working on June 18, 2026

  80radar

  Gemini CLITerminal AI CLI — runs Gemini from the command line

  Google is folding terminal AI workflows into Antigravity CLI. A popular CLI with 100k+ GitHub stars now has a hard migration deadline, so scripts and habits need cleanup soon.

  • —Gemini CLI grew to millions of users, 100k+ GitHub stars, and 6,000+ merged PRs; this is not a small side-tool shutdown.
  • —Google is consolidating capability into Antigravity CLI, pointing its agent tooling toward multi-agent workflows rather than a standalone Gemini terminal client.
  • —The deadline is June 18, 2026. Any local aliases, CI helpers, docs, or onboarding snippets using Gemini CLI should be replaced before then.

  Source: news.hada.io/topic?id=29711Read original →
• #0003

  #0003Agents & toolsGeekNews3 hours ago

  Better generated branch names with `jj`

  40radar

  jjGit-compatible VCS — change-based workflow with anonymous branches

  Default push branch names are change-ID centric and awkward in CLI flows. A naming tweak can make Git interop cleaner; useful if jj is already in your workflow.

  • —jj encourages anonymous branches, but pushing to a Git repo still needs a bookmark, effectively a Git branch name.
  • —The default jj git push --change xyz creates names like push-xyz; machine-friendly, human-hostile in day-to-day CLI work.
  • —Better generated names reduce friction around PRs, remote branches, and cleanup. Low impact unless your Git workflow already runs through jj.

  Source: news.hada.io/topic?id=29710Read original →