Use Instruct-2507 for everyday instructions, Thinking-2507 for reasoning-focused work, Coder for code, or the original when you need switchable thinking. An explicit model tag and a short context window make the first local check easier to interpret.
Start new Vertex AI projects on gemini-nano-banana-2.1 with enterprise=True and location global. Nano Banana 2 stays supported there until May 2027 or later.
Stop new tool execution, preserve verified results, and reconcile any uncertain write before resuming. A turn limit contains a loop; progress checks and operation records make recovery safer.
Start with the final outbound request. Use the instruction field and message positions supported by that exact endpoint, preserve tool-call pairs, and verify the full task after the role error clears.
Move the whole function-calling loop: validate the model’s arguments, run the authorized handler, return the result with its original call_id, and continue until the user gets a final answer. The JavaScript example preserves typed state and handles failed or unfinished responses.
Start with GitHub for remote PR and issue context, Context7 for version-specific docs, Playwright for browser exploration, or Sentry for recurring incident work. Add the one capability your existing tools lack, and check a relevant returned result before adding another server.
Start with /context for session drift, check loaded instructions before editing memory, and verify Context7 authentication and returned docs before adding another server.
To use DeepSeek in Claude Code, choose OpenRouter's gateway or DeepSeek's Anthropic-compatible endpoint. Each needs its own key and model names; a successful reply alone does not confirm the model or coding-tool compatibility.
For an Opus 4.7 `top_p deprecated` error, omit sampling fields from the final request your client sends. Native Messages and Bedrock Converse put those fields in different places; keep the same model and task when checking the fix.
Start with direct Claude API tools if your application owns execution. Build MCP when several clients need the same bounded interface. In either route, trusted code must authorize the operation and return evidence of what actually happened.
Codex /goal keeps one objective attached to a chat so work can continue across turns. Set a clear finish line, use the documented lifecycle controls, and accept completion only when the requested evidence is present.
A Nano Banana Pro 503 can include Deadline expired wording. Check the responding service and error code first, retry with a clear limit, and count recovery only when the same image request produces a usable result.
Use Files and Interactions for recordings, or the Live API for raw PCM captions. Vocabulary biasing and recorded speaker or word annotations require separate configurations.
The official Batch API cuts Gemini 3 Pro Image output prices to $0.067 for 1K/2K and $0.12 for 4K, before input and thinking charges. Use it for nonurgent work, budget for all billed tokens, and match downloaded images to their request keys.
Block the next unaffordable model request before dispatch: reserve its maximum cost against the shared run budget, reconcile the billable result, and keep budget stops terminal across retries and helpers.
Limited retention can fit an approved workload. ZDR requires evidence for the exact account, model, endpoint, features, and data path—and a gate that rejects unapproved changes.
For a confirmed Nano Banana 2 503 response, retry with jitter within an attempt and time budget. Keep the image workflow intact, verify image output, and defer work when recovery cannot fit the deadline.
Call gemini-3-pro-image through Google Interactions, save image bytes from the full response, and compile your own JSON or YAML job settings. PDFs need a document-capable model before Pro receives the verified facts and page images.
If Pro returns a restriction message or no image, first recover the correct Pro route: More → Redo with Pro in Gemini, the Pro menu in eligible AI Mode accounts, or gemini-3-pro-image in the API. Then check the actual response before calling the failure a policy block.
For "Unsupported file URI type," check the exact image value your app sent and the endpoint that rejected it. Native Gemini can accept supported HTTPS URLs; local paths, unresolved templates and base64 data URLs need a different payload. Verify the repair by getting an edited image from the same Pro request.
For APIConnectionError, capture the underlying exception and test DNS, TLS, proxy settings, and the exact endpoint from the failing runtime. An HTTP response narrows the problem; recovery still requires a successful request through the original application.
For transcripts, start with transcription. For a spoken assistant, compare Realtime—including mini—with the whole STT–LLM–TTS stack. A ten-minute call is not ten minutes of user audio plus ten minutes of assistant audio.
Use text.format when your application needs the model's final typed answer. Use function calling when the answer requires application data or an action. Combine them when a real tool result must become a schema-controlled object; then check both the schema and the business result.
A Cyber Abuse email is a warning or a deactivation. If you are locked out, send one complete appeal, request your data, and stop the next charge where you pay.