Home › How-to guides › Automate research and monitoring
How to automate research and monitoring with an AI agent
I looked through 201 real cases about research and monitoring and pulled out what people actually did, the prompts they used and the places it went sideways. No theory, no invented success stories.
What people actually do
- 50 AI agents in Minecraft built a government, a ration ledger and a no-blame inquiry about a chicken
- Pensive offers personalized AI teaching assistants for higher ed with Claude
- From weeks to a day: Everstar on Microsoft Foundry with Claude
- Biomni accelerates biomedical discoveries by 100x with Claude
- Speed up multifamily deal research and property summaries
- Terra Firma uses Harvey and a PwC UK tax model to cut tax research from days to seconds
- Reed Smith has 700 Harvey users a day and firmwide associate AI certification
- ICL Group used Harvey to complete a cross-border restructuring in-house and estimates 30–40% more lawyer efficiency
Browse all 2754 cases to see the rest.
Prompts to start from
These are the reusable prompts from real cases. Swap in your own details, run it once on something low-stakes, and read what the agent did before you trust it.
50 AI agents in Minecraft built a government, a ration ledger and a no-blame inquiry about a chicken
I'm designing a workflow with several AI agents. Review it for the failure modes seen in agent colonies. Check for a single hub that everyone messages, so it becomes a bottleneck; for agents spending effort on process, such as approvals, roles and permission requests, rather than the task; for handoffs where one agent passes something and another picks it up by mistake; and for agents becoming overcautious after failures. For each risk, propose a concrete fix, such as a named handoff location, a written protocol, a message budget or a deadline. Keep the plan as simple as it can be.
I want an agent to take on this workflow, show its working, and wait for approval on anything that changes a system or contacts someone. The tool in the source case was Claude.
Tools that show up most
Harvey (52), Custom agent (26), Microsoft 365 Copilot (21), Copilot Studio (20), Claude Code (16), Claude (9).
Guardrails
Start small: run it once on a low-stakes example, read what the agent did, and only then let it run on real work.
Where it went wrong, or nearly did
- Try Devin on research tasks (mostly failed): Devin got stuck parsing HTML on a scraping task.
More mess: the AI agent fails page. Related: the prompt library.