Second Opinions — Getting More Than One AI's Take

ambientChat lets you ask models from all three frontier labs (OpenAI, Anthropic, Google). You can put more than one of them on the same question, and you don't need a special mode for it. There are two kinds of second opinion, and they answer different needs:

1. A review: switch model and ask. The new model reads the whole conversation, including the earlier answer, and knows which model wrote it. Use this when you want something checked, critiqued or improved: "Review GPT's draft and tell me what you'd change."
2. An independent answer: ask an expert on its own. The other model answers without seeing the earlier answer, so it can't be swayed by it. Use this when you want an objective view, such as a second diagnosis, a valuation or a yes/no call, where you don't want the second model simply agreeing with the first.

Both work from coding tools connected over MCP too (Claude Code, Claude Desktop and others). See Via MCP below.

A second opinion doesn't have to come from another vendor. Asking a fast, cheap model and then that vendor's most capable one shows you whether the extra cost buys a better answer to this particular question.

#What It Does

Switching model mid-conversation keeps the whole thread. Once a conversation has answers from more than one model, each earlier answer reaches the next model tagged with the model that wrote it, e.g. [GPT-5.6 Sol]. So when you say "review GPT's answer", Claude knows exactly which answer that is and gives its own judgement rather than deferring to it. Nothing fans out automatically: you drive one model at a time.

Asking an expert on its own uses a tool called query_expert. Your current model sends a question to a different model, gets that model's answer back, and shows it to you labeled with the expert's name. If you ask, it compares the answer with its own. The expert never sees your conversation, only the question your current model sends it. That is what makes it independent.

Why the difference matters. A model that has just read a confident answer tends to anchor on it. Asked for "a second opinion", it often polishes what's there rather than questioning the premise. In-thread review is great for catching mistakes and gaps. For a genuinely independent answer, the second model must not see the first one.

#How to Use It

#Get a review: switch model and ask (iOS and web)

1. Ask your question with whichever model is selected and read its answer
2. Tap (iOS) or click (web) the model button and pick a different model, from another lab or a different tier of the same one
3. Either ask for what you want, e.g. "Review GPT's draft and tell me what you'd change" or "Do you agree with Claude's recommendation?", or leave the text box empty and press ↻. With nothing typed, the send button turns into ↻, which puts your last question to the model now selected
4. Switch again for a third view, and so on. Each model sees the earlier answers and who wrote them

#Get an independent answer: ask an expert on its own

Just ask in plain words, and say that the expert shouldn't see the earlier answer:

• "Ask Gemini, independently, for its own answer to my question. Send only the question and the facts it needs, not your answer or your conclusion."
• "Get an independent second opinion from Opus 5.5 on this valuation, then compare it with yours and tell me where you differ."

Your current model writes the question for the expert, so this wording matters. Ask it to include the facts the expert needs (the item, the numbers, the document's key terms), and to leave out its own answer. Then, if you like, ask it to compare the two answers.

The cleanest independent answer of all: a new conversation. Tap + (iOS) or New conversation (web), pick the other model, and ask the same question. That model starts with your personal context (your items, documents and profile) but nothing from the earlier thread. Bring its answer back to the first conversation if you want the two compared.

#Via MCP (Claude Code, Claude Desktop, and other AI agents)

The same query_expert tool is available to any MCP client you've connected to ambientChat, including Claude Code:

• Pass a model parameter with any currently-visible model ID (the tool description lists the available models and their capabilities)
• The tool automatically includes your full ambientChat context with each query: inventory, locations, and any of your documents that match the question
• A large document is held back, not spent silently. Just as in the app (see Chat), a document big enough to crowd out the rest of your context is left out of the expert's answer and reported instead. The result's documents list names it with mode: "held_back" and the token cost of including it. Your agent can then ask you, or decide itself, and call again with include_documents: [id] to pay for it, or with exclude_documents to drop one that was included. Each call decides for itself; nothing is remembered between calls

This is useful mid-work, not just for ambientChat questions. Reviewing a design document and want a second read before committing to it? Stuck on code that isn't behaving? Ask Claude Code to get a second opinion from a different model, e.g. "ask Opus 5.5 to review this function for edge cases" or "get Gemini's take on this design doc". It calls query_expert without you leaving your editor.

Example from Claude Desktop: "Ask Gemini what's the current market value for a 2023 MacBook Pro M3." The primary model calls query_expert to route the question to Gemini. If the answer needs real-time pricing, the expert pulls it in through Perplexity-backed web search.

For the full tool reference, see MCP Tools — Complete Reference.

#Tips & Tricks

• Draft with one model, review with another. For example, GPT drafts a contract, you switch to Claude for "give a second opinion on the draft, no changes yet", then you ask one of them to apply the changes you agreed.
• For high-stakes calls, get the independent answer first. Making a big purchase, checking health or legal information, valuing something? Get an independent answer before the models see each other, then ask one to compare. Two answers that agree independently mean more than one that agreed after reading the other.
• Watch for rubber-stamping. If the last model in a long thread says "this is ready, no changes needed", that may be the anchoring described above. Ask an expert on its own, or a fresh conversation, before you rely on it.
• Compare tiers, not just vendors. A fast model against a Premium one from the same vendor tells you whether the extra cost buys a meaningfully better answer to this question.
• ↻ works any time. With an empty text box, the send button re-asks your last question to the model now selected, on the phone and the web.

#Known Limitations

• No automatic fan-out. Your question is never sent to several models at once. You switch models and ask, one deliberate step per model.
• No side-by-side comparison view. Answers arrive one at a time as separate turns in the same thread.
• Independence depends on the question sent. When you ask an expert on its own, your current model writes the question. If you don't ask it to leave its own answer out, it may include it. Saying "independently" and "not your answer" is what keeps the expert blind.
• No automatic "best answer". The app never picks a winner among the models you asked. Ask one model to compare the answers, but the judgement is yours.

#Version History