Pin models and tune reasoning effort per task
Antigravity 1.1.5 adds stable model slugs, /effort and --effort controls, a redesigned /model picker with effort gauges, and per-agent model frontmatter. Use them to pin reproducible model choices and trade latency for depth on the fly instead of accepting defaults.Why this loop
1.1.5 makes model identity and reasoning depth explicit instead of session defaults. Stable user-facing slugs now appear in /model and are accepted by --model, so a choice can be pinned across launches. /effort shows and changes the current reasoning effort via a Left/Right timeline-gauge or /effort <level>; --effort selects a reasoning-effort variant at CLI start. /model groups by base model, uses the same gauge, and shows an effort badge on the status line for multi-variant models. Custom agent frontmatter gains model (e.g. flash or pro) for subagents, defaulting to inherit. Pin slug plus effort per task rather than re-accepting defaults.
Proposed actions
- Launch the CLI with a pinned slug and effort variant: --model <stable-slug-from-/model> --effort <level>, then confirm the status-line effort badge matches that variant.
- In the session run /effort to view the current reasoning effort; change it with Left/Right on the timeline gauge or /effort <level> before continuing so this task trades latency for depth without restart.
- Open /model, pick the grouped base model, set effort on the timeline gauge (Left/Right), and copy the stable user-facing slug shown so the next launch can pass that exact slug to --model.
- On a custom subagent, set frontmatter model: pro or model: flash (not inherit) so that agent runs at the chosen tier when invoked rather than following the parent.
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costGoogle Antigravity / agent task
DevAgentRadar → Google Antigravity
Goal: turn this release signal into a safe pilot plan for my stack.
Context
Assistant: Google Antigravity Proposal: Pin models and tune reasoning effort per task Summary: Antigravity 1.1.5 adds stable model slugs, /effort and --effort controls, a redesigned /model picker with effort gauges, and per-agent model frontmatter. Use them to pin reproducible model choices and trade latency for depth on the fly instead of accepting defaults. Primary source: https://github.com/google-antigravity/antigravity-cli/releases/tag/1.1.5
Why it matters
1.1.5 makes model identity and reasoning depth explicit instead of session defaults. Stable user-facing slugs now appear in /model and are accepted by --model, so a choice can be pinned across launches. /effort shows and changes the current reasoning effort via a Left/Right timeline-gauge or /effort <level>; --effort selects a reasoning-effort variant at CLI start. /model groups by base model, uses the same gauge, and shows an effort badge on the status line for multi-variant models. Custom agent frontmatter gains model (e.g. flash or pro) for subagents, defaulting to inherit. Pin slug plus effort per task rather than re-accepting defaults.
Suggested actions
- Launch the CLI with a pinned slug and effort variant: --model <stable-slug-from-/model> --effort <level>, then confirm the status-line effort badge matches that variant.
- In the session run /effort to view the current reasoning effort; change it with Left/Right on the timeline gauge or /effort <level> before continuing so this task trades latency for depth without restart.
- Open /model, pick the grouped base model, set effort on the timeline gauge (Left/Right), and copy the stable user-facing slug shown so the next launch can pass that exact slug to --model.
- On a custom subagent, set frontmatter model: pro or model: flash (not inherit) so that agent runs at the chosen tier when invoked rather than following the parent.
Config surfaces this release may change
- subagent definitions — check your repo before applying
- MCP servers — check your repo before applying
- permission rules — check your repo before applying
After you finish
Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.
Tell the human: open https://devagentradar.com/proposals/google-antigravity-1-1-5-pin-models-and-tune-reasoning-effort-per-task and mark Applied, Skipped, or Failed. Proposal id: 1b564787-eba4-4830-9489-cdf5a1d7ead7
Please:
- Map the change to concrete pilot steps
- Flag security / permission implications
- Keep the pilot reversible
Your loop
This browser · no sign-in · not shared as “you”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.