Ask your first question in Ask
Write a prompt that OpenFeather can actually answer, understand the streaming response, and follow up without repeating context.
A good first question is specific, names the source when it matters, and asks for something you can check. This guide shows how to write one and how to read what comes back.
Four things a strong prompt contains
- The subject — what you actually want to know or produce.
- The source — which connected account, project or workspace, when it is ambiguous.
- The time range — "this month", "last quarter", "since January" when recency matters.
- The shape of the answer — summary, comparison, list, draft, table or steps.
Example: "From my Google Drive spreadsheets, summarise revenue-related files from July to September and list anything that changed unexpectedly."
What the response looks like
Answers stream progressively. As they arrive you may see a live execution timeline showing which sources were consulted, then the finished answer with citations.
- Cited answer — the response with links to the sources it used.
- Sources — the specific documents, records or pages behind each claim.
- Structured blocks — tables, maps, image lists or comparison layouts when the answer needs them.
- Availability notices — when a capability is limited, degraded or provider-dependent.
Following up without repeating yourself
The conversation carries its own context, so follow-ups can be short:
- "Only the Q3 numbers."
- "Show me the two files that changed most."
- "Turn that into five LinkedIn posts."
- "What did you leave out?"
Open a new conversation when you want to change subject completely. Context from an unrelated earlier conversation can otherwise influence the answer.
When you get nothing useful
- Check the active workspace in the switcher.
- Check the account connected for the service you are asking about.
- Add an explicit date range.
- Ask OpenFeather to list the sources it used — that reveals whether retrieval ran at all.
If the sources list is empty for a private-data question, the request never reached a connected provider. See No data in an answer.
Common questions
How long should a prompt be?
One or two sentences is enough. Long prompts help only when they add constraints, not when they add restatement.
Why did my answer ignore my instruction?
If a requested capability is unavailable or unauthorised, OpenFeather states the limitation rather than inventing the result. Check the availability notice and the sources.