▶ Watch ↗AI Engineer Europe 20261:57:03
Build Your Own Deep Research Agent + Technical Writer
Read the full talk →Key ideas
Scroll to read ↓Combine exploratory research, file-based handoffs, structured editorial feedback, and a calibrated judge to turn a human brief into technical content you can inspect and improve.
- Why a fluent post still needs research and editing0:32 ↗
- Choose how much autonomy the task needs6:09 ↗
- Keep coupled decisions in one agent13:15 ↗
- Treat context as a budget16:15 ↗
- Research broadly enough, then hand off a focused artifact20:22 ↗
- Start with a human guideline and reusable services28:26 ↗
- Separate the reasoning harness from the MCP server34:41 ↗
- Make each research call inspectable40:06 ↗
- Turn a video into a durable research artifact44:35 ↗
- Connect the server and test one capability49:15 ↗
- Use skills to load the research procedure56:14 ↗
- Inspect the searches as well as the final report1:07:26 ↗
- Build the writer’s context deliberately1:10:57 ↗
- Teach the voice with representative examples1:19:10 ↗
- Review in a separate context and return actionable feedback1:21:37 ↗
- Run locally, then decide how to distribute the capability1:28:13 ↗
- Follow the work through threads and traces1:33:06 ↗
- Build evaluation data from the real writer1:37:00 ↗
- Calibrate the judge against expert labels1:42:12 ↗
- Read perfect scores in the context of their dataset1:46:37 ↗
- New traces expose what the small evaluation missed1:53:05 ↗
- Run the complete path from guideline to post1:55:00 ↗
