Route Claude's Mechanical Work to a Cheap Side Model

// related

• #0001

  #0001Agents & toolsGoogle AI Forum1 hour ago

  `Antigravity CLI` lacks sandbox and custom Docker image support

  40radar

  Antigravity CLICoding agent CLI — command-line tool for Google Antigravity

  A concrete parity gap versus Gemini CLI: no custom image or sandbox flow. Fine for light tasks, weak for reproducible agent runs.

  • —Gemini CLI supports custom Docker images and sandboxed execution; Antigravity CLI currently lacks that workflow control.
  • —The report is only 1 post with no maintainer answer, so treat it as a compatibility warning, not a roadmap signal.
  • —Agent runs that touch installs, DB clients, or native deps need pinned containers. Without that, CI-like reproducibility gets messy fast.

  Source: discuss.ai.google.dev/t/antigravity-cli-doesnt-support-sRead original →
• #0002

  #0002Agents & toolsCline Releases2 hours ago

  `Cline CLI` `v3.0.9` speeds up plugin startup and config toggles

  50radar

  ClineCoding agent CLI — plugin-based automation support

  Plugin-heavy CLI sessions start faster. Optimistic TUI updates and cached tool descriptors reduce friction, worth updating if Cline CLI is in daily use.

  • —Sandboxed plugins now load concurrently, with tool descriptors cached per plugin, provider, and model. Startup latency should drop most in plugin-heavy setups.
  • —Plugin and tool config toggles update the TUI optimistically and persist without full config reloads. Less waiting while switching tools on and off.
  • —The @ mention file picker restores fuzzy ranking, so relevant files surface first again. Small fix, but it cuts prompt setup friction.
  • —Cancelled tasks no longer tear down the interactive session, and abort cleanup failures no longer crash the runtime host.

  Source: github.com/cline/cline/releases/tag/cli-v3.0.9Read original →
• #0003

  #0003Agents & toolsGoogle AI Forum2 hours ago

  `Antigravity` `v2.0.0` Linux build hit by serious usability bugs

  50radar

  AntigravityAI coding agent IDE — Google-built developer agent tool

  The Linux upgrade path is risky: broken window chrome, messy workspace indexing, hidden IDE entry, and leaked processes. Hold upgrades on active projects.

  • —Closing with the window X leaves background processes alive, locking ports and directories; File -> Quit is the only clean exit path mentioned.
  • —Workspace indexing creates duplicate virtual folders like Diary 9 and Diary 10, scattering chat history across fake project paths.
  • —The standalone Agent window has no clear route into the code editor, weakening the unified agent-plus-IDE workflow.
  • —A third-party patcher exists for native window borders, but needing internal-file patches is not acceptable for a daily coding tool.

  Source: discuss.ai.google.dev/t/critical-usability-and-process-lRead original →