`Antigravity Ultra` users hit persistent `MODEL_CAPACITY_EXHAUSTED` on Claude Opus thinking

// related

• #0001

  #0001Agents & toolsGoogle AI Forum3 hours ago

  `Gemini Code Assist` Individual IDE/CLI Access May End June 18

  80radar

  Gemini Code AssistAI coding assistant — Gemini in IDE extensions and CLI

  Individual Pro, Ultra, and free access stops on June 18, 2026. VS Code users should line up alternate auth or tools before agent workflows break.

  • —The notice names Gemini CLI and Gemini Code Assist IDE extensions. Individual Pro, Ultra, and free accounts are the affected paths.
  • —The cutoff date is June 18, 2026. Any VS Code workflow wired to personal Gemini access needs a fallback before then.
  • —The forum post does not confirm whether an Antigravity-specific VS Code extension continues. Treat it as unresolved until Google posts a clearer migration path.

  Source: discuss.ai.google.dev/t/will-there-no-longer-be-a-geminiRead original →
• #0002

  #0002Agents & toolsHacker News · Show HN AI3 hours ago

  `AISlop`, a CLI that catches AI-generated code smells

  60radar

  AISlopAI code-quality CLI — local code-smell scanning

  Scans for patterns tests often miss: empty catches, dead code, duplicate helpers, and useless comments. Local-only hook integration makes it worth trying in agent-heavy repos.

  • —npx aislop scan runs locally, so source code is not uploaded. That lowers the barrier for private app repos.
  • —Targets AI-agent residue rather than syntax errors: empty catch, dead code, duplicated helpers, and low-value comments.
  • —Hook-based use after each tool call fits Claude Code, Codex, and opencode workflows where small slop accumulates fast.

  Source: github.com/scanaislop/aislopRead original →
• #0003

  #0003Agents & toolsGeekNews14 hours ago

  `Claude Code` Adds Dynamic Workflows for Parallel Subagents

  90radar

  Claude CodeCoding agent CLI — runs agentic dev tasks from the terminal

  Large engineering jobs can now be split across many subagents in one session. This turns agent work from linear prompting into scripted orchestration worth testing on repo-scale tasks.

  • —A single session can dynamically write orchestration scripts, launch dozens to hundreds of parallel subagents, and collect results before delivery.
  • —The feature targets work too large or complex for one agent, so it fits migrations, wide refactors, audits, and test expansion.
  • —The bottleneck shifts to task decomposition. Vague goals will create noisy parallel work, while clear file/module boundaries should pay off.

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