Antigravity 1.1.24

When you define agents (assistants that perform specific tasks) with identical names across multiple configuration sources or plugins, opening the /agents picker no longer shows distracting duplicates. Previously during discovery, finding an agent with the same name across different sources or plugins listed every instance in the picker; the menu now automatically deduplicates entries, keeping your selection list clean.

Launching the command line from a working directory that has been deleted or is inaccessible will no longer cause tool initialization or agent startup to crash. Previously, parameter schemas held in memory lost relative references when the directory was invalid; switching fully to absolute URI schemes ensures all tools and agents initialize reliably regardless of directory state.

When running automation scripts in headless mode (background execution without a visual interface) with piped standard output or standard error, invocations no longer hang on exit. Previously, spawned child processes kept the caller's pipes open and prevented the main process from shutting down cleanly; setting FD_CLOEXEC on preserved streams now ensures all pipe resources are fully released on exit.

When manually editing tool configurations, you no longer need to worry about quick notes or extra commas breaking your setup. Previously, adding single-line comments //, multi-line comments /* */, or trailing commas in mcp_config.json caused MCP (protocol connecting AI to external tools) configuration parsing to fail; the parser is now more forgiving and reads configurations containing comments and trailing commas smoothly.

When clearing old conversations, your local disk space is now kept completely tidy. Previously, deleting a conversation removed the main chat but often left associated annotation files in local storage, gradually accumulating useless orphaned files over time; the deletion logic has been updated to automatically prune matching annotations alongside the conversation.

While AI is actively working through a major project, you can now safely ask quick side questions without derailment. When running a long-term goal with /goal, asking a side question with /btw (by the way, a command for asking auxiliary questions) previously led to treating the tangent as part of the active goal, forcing unwanted progression and unintended tool calls; their execution states are now decoupled so side questions resolve your query without interrupting the main task.