Trust Diff

Simulated: the agent, the plan, the account, and the receipt are fake. Nothing leaves this page.

Chat with the agent

What will change

Before

    After (preview)

      Receipt and undo record

      The agent host writes this before it runs. The repo or ticket system keeps it.

      
                  
      How Trust Diff works Six stages. The request reaches the agent. The agent writes a plan. The host shows a plan diff. The person picks steps. The executor runs only those steps and the host writes an undo record. The repo stores the receipt. 1 Requestfrom you 2 Agent plan 3 Plan diffshown by host 4 You picksteps 5 Executor runspicked steps 6 Repo keepsthe receipt

      The executor gets only the steps the person picked. The check happens at stage 3.

      Try this

      1. Wait for the plan. Leave the amber steps unchecked. Click Apply selected.
      2. Click Undo. Check one amber step. Watch the What will change panel.
      3. Pick the second request. Find the data loss warning.

      Pain point

      A person approves an agent without seeing what it will really change.

      Problem statement

      An agent plans more steps than the request named. The person sees a summary, not the difference.

      What sparked it

      Mozilla's W3C WebExtensions notes (issue 1041) say no browser primitive lets a user see, scope, or withdraw an agent's access.

      Why this approach

      Compare the request with the agent's plan and show the difference, like a code diff.

      Hypothesis tested

      We believed that a diff of the plan helps a person approve only what they meant. If it holds, people deselect the steps that go beyond the request.

      How to try it

      1. Open the Prototype tab. Check or uncheck plan steps.
      2. Click Apply selected, then Undo.

      What this does not do

      Notes

      Traces

      Prompts used to make this prototype
      StepPromptModelToolDate

      Cost

      Cost to make this prototype
      StepModelInput tokensOutput tokensCost (USD)
      Total

      Measured: the author runs used 183,870 tokens in total. Estimated: the split into input and output tokens (90 percent input, 10 percent output) and the dollar cost, at $2 input and $10 output per million tokens for Sonnet 5.5 (about $0.51). The run reported one total only. The lead session's planning, research, and publishing are not included. The prompts in the Traces section are listed in the order they were given.