Intent Lock

Simulated: the agent, the gateway, and every tool below are scripts. No real agent, service, or standard is used.

1. Write the task contract

agent-intent.json Proposal, not a standard


          

2. Chat with the simulated agent

Time left:

Press a button. The agent tries that tool call. The gateway decides.

3. What the gateway sees

This panel updates on each call and each contract change.


          

4. Decision timeline

No calls yet. Press a tool button above.

    How it works

    The diagram replays the last tool call, one step at a time. Before any call it shows .

    Intent Lock anatomy An agent sends a tool call to a gateway. The gateway checks the signed task contract from the issuer, then the lists, the cost cap, and the expiry time. It forwards allowed calls to the tool, blocks denied calls, and asks the user to approve calls on the approval list. Agent Gateway Tool Issuer You approve 1 call 2 signed contract ask forward

    Press Play or Step.

    Pain point

    A person can limit which tools an agent calls, but not what it may achieve.

    Problem statement

    Teams give an agent broad tool access or approve each step by hand. Neither lets a person state limits.

    What sparked it

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

    Why this approach

    The person writes a short task contract. A gateway checks every tool call against it.

    Hypothesis tested

    We believed that a short contract with limits and an expiry gives a person enough control. If it holds, the gateway allows, blocks, or asks for each call correctly.

    How to try it

    1. Open the Prototype tab. Move a tool between lists in the contract form.
    2. Press the tool buttons next to the chat.
    3. Speed up the clock to see what happens after the contract expires.

    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 190,769 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.53). 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.