Research and write a brief

What you enable first

• Open Home → Integrations and enable a search tool such as Brave Search so the agent can find sources.
• Or let the runtime search for itself. The Claude integration has a web search option in the Network tab, off by default. Codex is limited to its cached web search, because live provider browsing stays denied.
• When snippets are not enough and it must read pages in full, enable a web fetch tool or a network integration for those domains.
• For a private source, add its domain as its own network integration, and only when the brief genuinely depends on it.

The prompt to send

Start a Chat and send one request that carries the whole job. Sourcing rules, the output file, and what belongs in memory all live in the prompt, so you are not steering the agent turn by turn.

Research managed Postgres providers so I can decide which one to run our
production database on.

Compare official pricing at our scale, backup and recovery guarantees,
region availability, and what happens during a version upgrade.
Use primary sources, link every claim, and give the date you retrieved it.
Separate verified facts from your own inference, and say where evidence is thin.
Save the brief to research/managed-postgres-brief.md in agent-home.
Add only the settled conclusions and reusable source notes to memory,
not a transcript.

What you check afterwards

• Read the saved file in agent-home rather than the chat transcript; that artifact is what survives the thread.
• Spot-check two or three citations and their dates against the linked sources.
• Open Network audit to see which domains were reached and which requests were denied.

The section on backup guarantees rests on one vendor page. Find an independent
primary source, correct anything it contradicts, and update the brief in place
with a short changelog at the bottom.