Project Fetch Workflow Trust Grows When Agents Reveal Every Step
- Sophie Larsen

- Jun 22
- 3 min read
Project Fetch from Anthropic tested how office agents gain trust when they expose every step they take. Teams accepted autonomous work faster once they could review intermediate actions instead of waiting for the final result.
The experiment focused on Claude Opus 4.7 completing tasks with full visible trails. Speed reached roughly twenty times faster than human teams, but only when inspectors could pause and check each stage.
This finding matters for any product team or knowledge worker using agents on documents, reports, or research. Visibility turned out to be the real limiter on adoption, not raw capability.
Project Fetch workflow trust therefore hinges on inspectable steps rather than black-box speed.
The core change in Project Fetch
Anthropic ran the second phase of Project Fetch as a controlled test of agent autonomy on defined office tasks. The agents handled summarizing quarterly earnings reports (success criterion: 95% accuracy on key financial figures, audited by humans), drafting client proposal emails (success criterion: inclusion of all required client data points and compliant tone), and analyzing sales data trends (success criterion: surfacing at least three verifiable insights per dataset) without constant human prompts. As one Anthropic project note described it, "inspectable intermediate actions proved more decisive for delegation than final-output accuracy alone." Anthropic researcher notes further emphasized that "the chain of visible decisions lets teams delegate faster than raw output quality alone would allow."
The decisive detail was the logging layer. Every agent produced a visible chain of actions, decisions, and data pulls that reviewers could open at any point. Earlier versions hid those steps behind a single final file.
Teams that received only the finished output showed low willingness to delegate more work. Teams that received the full step log increased delegation volume within the same week.
Why visibility changed the trust equation
Office agents normally reset context each session. Users must re-explain goals and supply background materials every time a new task begins. Project Fetch removed that reset by keeping the full work trail attached to each deliverable.
Inspectors could open any intermediate file, see the source the agent used, and confirm the logic applied. This single feature moved the conversation from "does it work" to "where did it pull this number."
The speed advantage only translated into real usage when reviewers kept that audit path open. Without it, the twenty-times throughput stayed unused because no team would sign off on invisible output.
Comparison with current office tools
General agents such as those from OpenAI or standalone frameworks still deliver a single response or document. Users receive the answer but lack the chain of reasoning that led there. Project Fetch isolated that gap as the main barrier to scaling delegation.
remio keeps an always-on memory layer that records meetings, documents, and prior decisions. When its agents generate a report or spreadsheet, the same memory trail remains attached so reviewers can trace each source. For example, remio can capture a meeting decision on revised Q3 targets and surface that exact note when an agent later produces an updated forecast, letting reviewers instantly verify the origin.
This approach matches the Project Fetch pattern. The agent does not start from zero context, and the user does not start from zero verification.
Risks that remain after the test
The Project Fetch results came from a controlled set of tasks with clear success criteria. Real office work often contains ambiguous requirements that no logging system can fully resolve in advance.
Teams still needed a human to define the initial goal and approve any policy change mid-process. The visible steps reduced verification time but did not remove the need for oversight on judgment calls.
Longer deployments will show whether fatigue sets in once reviewers must scan long trails on every task. Early data suggests selective sampling - reviewing only decision points where the agent's confidence score fell below 80 percent rather than every logged action - works better than full audits on routine items.
What to watch in the next three months
Watch for Anthropic to release controlled enterprise trials that measure delegation volume against step-log length. A sharp rise in accepted autonomous work when logs stay under a certain size would confirm the visibility threshold.
Watch whether competing agent platforms add similar step-exposure features and how quickly adoption curves shift after those updates.
Watch remio usage data on report generation tasks. If users who enable full memory trails delegate more analysis work, the Project Fetch pattern will have crossed from research setting into daily office practice.
Teams that treat workflow visibility as a product requirement rather than an afterthought will see faster trust growth in their agents. The data from Project Fetch already points in that direction.


