Ask Antigravity (new conversation)

Previous value: -"Optional model slug to run this conversation on (agy's --model),\n   e.g. \"gemini-3.1-pro-high\" or \"claude-sonnet-4-6\". Omit to use the\n   model set in agy's settings.json (gemini-3.8-flash-high as of agy\n   1.1.25). Must be one of `agy models` — an unknown slug is\n   rejected up front (agy would otherwise silently ignore it and fall\n   back to the default). agy 1.1.5 replaced the old human labels\n   (\"Gemini 3.1 Pro (High)\") with these slugs, and the default has\n   since moved to the gemini-3.8-flash family; the old form is no\n   longer accepted. Note 1.1.25 also DROPPED the gemini-3.5-flash\n   family with no changelog entry, so a 3.5 slug you saw in older\n   docs is now rejected. See antigravity_status / `agy models` for\n   the valid slugs."New value: +"Optional model slug to run this conversation on (agy's --model),\n   e.g. \"claude-sonnet-5-5-high\" or \"gemini-3.8-flash-low\". Omit to use\n   the model set in agy's settings.json (gemini-3.8-flash-high as of\n   agy 1.3.5). Must be one of `agy models` — an unknown slug is\n   rejected up front. agy renames and drops models between releases,\n   often with no changelog entry, so a slug from older docs may be\n   gone; see antigravity_status / `agy models` for the valid ones."

Previous value: -"If true, run agy in PLAN mode (agy 1.1.12+): it investigates and\n  writes an implementation plan instead of touching anything. Verified\n  on 1.1.20 that a file write and a shell command are both refused and\n  diverted into a plan document under agy's own directory — even when\n  the prompt insists, and even though the bridge still passes\n  --dangerously-skip-permissions — while file READS answer normally.\n  Use it to point Antigravity at a repo you don't want it editing.\n  Two caveats. It is agent-enforced, not an OS sandbox: it constrains\n  agy's agent loop, so treat it as a strong default rather than a\n  boundary you'd rely on against a hostile prompt (Codex has the real\n  one — see codex_ask's sandbox, and its Windows caveat: as of codex\n  0.149.1 a sandboxed run there refuses every command and answers\n  anyway). And it is exclusive with the bridge's\n  slash-command shield, because agy silently disables plan mode when\n  that shield is on; a prompt whose first token is a slash command is\n  therefore rejected up front rather than run. Raises on agy older than\n  1.1.12, which ignores --mode in print mode, rather than silently\n  running your prompt unrestricted. Default false."New value: +"If true, run agy in PLAN mode (agy 1.1.12+): it investigates and\n  writes an implementation plan instead of touching anything. Verified\n  on 1.1.20 that a file write and a shell command are both refused and\n  diverted into a plan document under agy's own directory — even when\n  the prompt insists, and even though the bridge still passes\n  --dangerously-skip-permissions — while file READS answer normally.\n  Use it to point Antigravity at a repo you don't want it editing.\n  Two caveats. It is agent-enforced, not an OS sandbox: it constrains\n  agy's agent loop, so treat it as a strong default rather than a\n  boundary you'd rely on against a hostile prompt (Codex has the real\n  one — see codex_ask's sandbox, and its Windows caveat: as of codex\n  0.162.1 a sandboxed run there refuses every command and answers\n  anyway). And it is exclusive with the bridge's\n  slash-command shield, because agy silently disables plan mode when\n  that shield is on; a prompt whose first token is a slash command is\n  therefore rejected up front rather than run. Raises on agy older than\n  1.1.12, which ignores --mode in print mode, rather than silently\n  running your prompt unrestricted. Default false."

Previous value: -"Optional model slug to run this conversation on (agy's --model),\n   e.g. \"gemini-3.1-pro-high\" or \"claude-sonnet-4-6\". Omit to use the\n   model set in agy's settings.json (gemini-3.7-flash-high by\n   default). Must be one of `agy models` — an unknown slug is\n   rejected up front (agy would otherwise silently ignore it and fall\n   back to the default). agy 1.1.5 replaced the old human labels\n   (\"Gemini 3.1 Pro (High)\") with these slugs, and the default has\n   since moved to the gemini-3.7-flash family; the old form is no\n   longer accepted. See antigravity_status / `agy models` for the\n   valid slugs."New value: +"Optional model slug to run this conversation on (agy's --model),\n   e.g. \"gemini-3.1-pro-high\" or \"claude-sonnet-4-6\". Omit to use the\n   model set in agy's settings.json (gemini-3.8-flash-high as of agy\n   1.1.25). Must be one of `agy models` — an unknown slug is\n   rejected up front (agy would otherwise silently ignore it and fall\n   back to the default). agy 1.1.5 replaced the old human labels\n   (\"Gemini 3.1 Pro (High)\") with these slugs, and the default has\n   since moved to the gemini-3.8-flash family; the old form is no\n   longer accepted. Note 1.1.25 also DROPPED the gemini-3.5-flash\n   family with no changelog entry, so a 3.5 slug you saw in older\n   docs is now rejected. See antigravity_status / `agy models` for\n   the valid slugs."

Previous value: -"Optional model slug to run this conversation on (agy's --model),\n   e.g. \"gemini-3.1-pro-high\" or \"claude-sonnet-4-6\". Omit to use the\n   model set in agy's settings.json (gemini-3.6-flash-high by\n   default). Must be one of `agy models` — an unknown slug is\n   rejected up front (agy would otherwise silently ignore it and fall\n   back to the default). agy 1.1.5 replaced the old human labels\n   (\"Gemini 3.1 Pro (High)\") with these slugs and 1.1.6 added the\n   gemini-3.6-flash family; the old form is no longer accepted. See\n   antigravity_status / `agy models` for the valid slugs."New value: +"Optional model slug to run this conversation on (agy's --model),\n   e.g. \"gemini-3.1-pro-high\" or \"claude-sonnet-4-6\". Omit to use the\n   model set in agy's settings.json (gemini-3.7-flash-high by\n   default). Must be one of `agy models` — an unknown slug is\n   rejected up front (agy would otherwise silently ignore it and fall\n   back to the default). agy 1.1.5 replaced the old human labels\n   (\"Gemini 3.1 Pro (High)\") with these slugs, and the default has\n   since moved to the gemini-3.7-flash family; the old form is no\n   longer accepted. See antigravity_status / `agy models` for the\n   valid slugs."

Added value: +{
+  "default": false,
+  "description": "If true, run agy in PLAN mode (agy 1.1.12+): it investigates and\n  writes an implementation plan instead of touching anything. Verified\n  on 1.1.20 that a file write and a shell command are both refused and\n  diverted into a plan document under agy's own directory — even when\n  the prompt insists, and even though the bridge still passes\n  --dangerously-skip-permissions — while file READS answer normally.\n  Use it to point Antigravity at a repo you don't want it editing.\n  Two caveats. It is agent-enforced, not an OS sandbox: it constrains\n  agy's agent loop, so treat it as a strong default rather than a\n  boundary you'd rely on against a hostile prompt (Codex has the real\n  one — see codex_ask's sandbox, and its Windows caveat: as of codex\n  0.149.1 a sandboxed run there refuses every command and answers\n  anyway). And it is exclusive with the bridge's\n  slash-command shield, because agy silently disables plan mode when\n  that shield is on; a prompt whose first token is a slash command is\n  therefore rejected up front rather than run. Raises on agy older than\n  1.1.12, which ignores --mode in print mode, rather than silently\n  running your prompt unrestricted. Default false.",
+  "type": "boolean"
+}

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional JSON Schema (an object, or its JSON text). When given, agy\n    is asked to produce output matching it (agy 1.1.8's --json-schema)\n    and this tool returns the VALIDATED OBJECT as JSON text instead of\n    prose — json.loads it. What comes back is agy's own\n    `structured_output`, which carries exactly the declared fields;\n    agy's prose `response` on the same run also picks up its internal\n    toolAction/toolSummary keys and can be prefixed with a sentence, so\n    the two are NOT interchangeable. If agy produces no structured\n    output the call RAISES rather than handing back prose you would\n    have to parse anyway. Needs agy 1.1.8+.\n\n    IMPORTANT — write the prompt so the ANSWER is in the turn, and let\n    the schema only shape it. agy fills the schema in a finishing pass\n    that does not re-reason about the content, so a field the turn never\n    established gets guessed from the schema itself. Measured on 1.1.20\n    with \"this broke my build and wasted my whole afternoon\": with\n    enum [\"positive\",\"negative\"] it answered \"positive\" 3 times out of 4,\n    and simply REVERSING the enum to [\"negative\",\"positive\"] flipped it\n    to \"negative\" 2 out of 2 — it was following field order, not the\n    sentence. Adding a `reason` field did not help; the reason came back\n    \"Completed sentiment classification task.\" Asking the prompt to state\n    the verdict and why, and keeping the same biased enum, was correct\n    3 out of 3. So: extraction of what the model has already worked out\n    is reliable; a judgment delegated to the schema is not."
+}

Previous value: -"Optional model label to run this conversation on (agy's --model),\n   e.g. \"Gemini 3.1 Pro (High)\" or \"Claude Sonnet 4.6 (Thinking)\".\n   Omit to use the model set in agy's settings.json (Gemini 3.5 Flash\n   (High) by default). Must be one of `agy models` — an unknown label\n   is rejected up front (agy would otherwise silently ignore it and\n   fall back to the default). See antigravity_status / `agy models`\n   for the valid labels."New value: +"Optional model slug to run this conversation on (agy's --model),\n   e.g. \"gemini-3.1-pro-high\" or \"claude-sonnet-4-6\". Omit to use the\n   model set in agy's settings.json (gemini-3.6-flash-high by\n   default). Must be one of `agy models` — an unknown slug is\n   rejected up front (agy would otherwise silently ignore it and fall\n   back to the default). agy 1.1.5 replaced the old human labels\n   (\"Gemini 3.1 Pro (High)\") with these slugs and 1.1.6 added the\n   gemini-3.6-flash family; the old form is no longer accepted. See\n   antigravity_status / `agy models` for the valid slugs."

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional model label to run this conversation on (agy's --model),\n   e.g. \"Gemini 3.1 Pro (High)\" or \"Claude Sonnet 4.6 (Thinking)\".\n   Omit to use the model set in agy's settings.json (Gemini 3.5 Flash\n   (High) by default). Must be one of `agy models` — an unknown label\n   is rejected up front (agy would otherwise silently ignore it and\n   fall back to the default). See antigravity_status / `agy models`\n   for the valid labels."
+}