Free to read · no account needed

16 min · agents

Research agent pattern (safe defaults)

Goal: run a research-style agent that plans, gathers, and stops for your review before any big conclusion.

Best for: competitor scans, “what changed?”, meeting prep—without trusting invented links.

A research agent is not “search forever.” It is a bounded loop: clarify → plan sources → collect with citations → contradict itself → you decide.

Safe default for beginners: browsing/search allowed; sending and file-deletes never; every claim needs a link you can open.

Why beginners skip this

A research agent that concludes without your review ships confident fiction. Safe defaults plan, gather, then stop—claims need sources you opened.

Habit this week (Asia/Shanghai): run one research-style pass with a claim→evidence table; no claim ships without a link you opened—date the table.

Step 1 — Clarify and bound the question

Force a one-sentence question, time range, and audience. Ban a full report until the plan is approved.

You are a research agent (plan only).
Question: [q]
Return: clarified question · 5 sub-questions · source types to prefer · what would falsify a hasty answer · 3 clarifying questions for me
No browsing yet.
Example

Filled prompt

Brief: "What changed in EU cookie rules affecting our SaaS checkout in 2026?"
Done for agent: link pack + Unknowns list—NOT a final legal answer.
Stop after gather. I will open primaries and write the conclusion offline.
Ban auto-publish.

What good output looks like

  • Clarified question names team size and quarter
  • Falsifier is concrete
  • Asks clarifying questions before search
  • Pass/fail dated (Asia/Shanghai) sits next to the artifact

Step 2 — Collect with citation rules

After you approve the plan: allow search. Require link + publisher + date. Cap sources (e.g. 8).

Execute research for the clarified question.
Rules: every factual bullet needs link + publisher + date. Max 8 sources. Separate reported vs confirmed.
Output: 1-page brief + contradictions + 3 Monday actions.
As-of: 2026-10-17
Example

Filled prompt

Brief: "Summarize three open-source license options for our CLI tool."
Done for agent: link pack to SPDX/official license pages + Unknowns—NOT a pick-for-us verdict.
I choose offline after opening links.

What good output looks like

  • Bullets have openable links
  • Unknowns listed
  • Monday actions are human tasks, not “keep researching forever”

Step 3 — Stress-test before you trust it

Ask the agent to attack its own brief. You open the top links.

Attack this brief: 5 weakest claims and what evidence would change them.
Steel-man the opposite recommendation in 6 bullets.
Do not defend the original brief.
Example

Filled prompt

Scene: real work this week (live artifact open).
Attack the Notion vs Claude brief. 5 weakest claims + opposite recommendation. No defending.
Constraints: no invented facts; stop before send/delete; label Unknowns.

What good output looks like

  • Done boxes for “run a research-style agent that plans, gathers, an” are explicit and checkable
  • Allow-list tools only; never-do lines honored
  • Stops before send/delete without human gate
  • Pass/fail: Plan→Act one→Check visible for agents-research-agent-pattern

Keep it real

Run this guide’s Practice now on work you will actually ship this week—not a fictional scenario. Dated notes beat perfect theory.

Ship the practice

Close the tab only after Practice now is done on a real artifact.

Do not bookmark-only

Finish Practice now, then tick this guide on your path. Titles unread are not skills.

Close the loop

After Practice now, write one line: what you will refuse next time. That line is the habit.

Check the unknown path

What should the model do when a field is missing—null, TBD, or ask you? Write it once in Boundaries.

Red flag

Claims without opened links; treating forum heat as primary; shipping without a counter-question—do not externalize.

Save this card

Card: plan → gather → stop for review · claim→evidence with links you opened · no unopened citations.

1. What I shipped: ___ 2. What I refused: ___ 3. What I will never-do again: ___ (date: Asia/Shanghai)

  • [ ] Tools/writes paused
  • [ ] Refuse-line dated
  • [ ] Artifact path saved
  • [ ] Next link chosen (or stop)

Before you start

Write Done (checkboxes) and the human gate on paper before any run for “run a research-style agent that plans,.” Allow-list tools; leave send/delete off. Guide: agents-research-agent-pattern. If you only have a blank practice box, stop and fetch the real job first.

  • Goal in one line: ___
  • Allowed tools: ___
  • Forbidden: ___
  • Human approve needed for: ___

How to use this week

This week: run one research-style agent with a written claim→evidence table. No claim ships without a source you opened. Date the table on a live artifact—not a blank demo. Write one refuse-line and date the note (Asia/Shanghai). If you only skimmed agents-research-agent-pattern, put 25 minutes on the calendar and redo once.

Close the week by quoting aloud the refuse line you actually used once. If you cannot, rerun Practice now and date the pass/fail (Asia/Shanghai).

Pitfalls

PitfallFix
Unlimited browsing with no source capCap sources and time
Trusting typed URLsClick them
Agent “decides” for the companyIt briefs; humans decide
Example

Filled prompt

Temptation: skip the habit for agents-research-agent-pattern to “save five minutes.”
Job still: run a research-style agent that plans,
Do the smallest correct pass: Done visible · one checkable artifact · Unknowns labeled [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: the artifact + the refuse-line you said aloud.

What good output looks like

  • Names the shortcut you refused (specific to agents-research-agent-pattern)
  • Still delivers a checkable artifact for “run a research-style agent that plans,”
  • Unknowns labeled; draft-only respected
  • Pass/fail: refuse-line written and dated (agents-research-agent-pattern #4)

Practice now

Live card: run one agent checklist item on a real job for “Research agent pattern (safe defaults)”—artifact path on Save (Asia/Shanghai).

Today: produce a one-page claim→evidence table from a research-style run; every claim needs a link you opened. Add one counter-question. Date it (Asia/Shanghai).

Today card (copy) — agents-research-agent-pattern: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___

  • [ ] Artifact path written
  • [ ] Refuse example would say "yes"
  • [ ] Dated Asia/Shanghai

One sentence takeaway

Research agents plan, gather, then stop—claims need sources you opened. This week: one dated claim→evidence table (Asia/Shanghai).

Next

Claim–evidence matrix · Writing pipeline agent · Plan → act → check · Human-in-the-loop checkpoints · Verify before you share

Pair with today: open the first Next link (research-claim-evidence-matrix) only after you dated a refuse-line for this guide (Asia/Shanghai).

← Back to home · Learn · Tools · Compare · Start