Better generated branch names with `jj`

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.

[ KEY POINTS ]

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.

Originalnews.hada.io/topic?id=29710Read original →

// related

#0001
#0001Agents & tools opencode_releases3 hours ago
`opencode` `v1.15.6` adds TUI diff review and shell mode
70radar
opencodeOpen-source coding agent CLI — TUI-first workflow
Change review now happens inside the TUI, and run prompts can drop into shell mode. This is a practical upgrade for terminal-first agent workflows.
- The TUI adds a diff viewer with auto-focus on the first file and collapsed single-child directories, cutting review friction before accepting edits.
- Run now gets shell mode and replaces subagent tabs with an on-demand picker, making agent sessions less crowded during longer tasks.
- Plugin failures are better isolated: file load errors and missing tool args no longer break the rest of plugin loading.
- v2 HTTP API now exposes structured public error schemas and preserves endpoint error responses in the OpenAPI spec.
Source: github.com/anomalyco/opencode/releases/tag/v1.15.6Read original →
FIG-0011:1
70radar
FIG-0011:1
#0002
#0002Agents & tools Google 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 →
FIG-0021:1
60radar
FIG-0021:1
#0003
#0003Agents & tools GeekNews4 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 →
FIG-0031:1
80radar
FIG-0031:1

Better generated branch names with `jj`

// related

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

`Antigravity 2.0` upgrade breaks IDE workflow for existing users

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