Latchling Local simulation
SMALL PERMISSIONS. BIG PEACE OF MIND.

Give agents
a little room.

Set the limits. Let them work.
Keep the keys.

Make your first policy
YOUR RULESTHEIR REACH
BudgetTimeTools
01—03 / ONE CLEAR BOUNDARYClosed to surprises.
01 / THE SANDBOX

Your agent. Your terms.

Permission policy

POLICY / 001
USDC
0.00 used100.00 remaining
minutes

Expires at the limit. No open-ended sessions.

03 Tool allowlist 2 / 4
Saved on this device

Knock on the door.

TRY A REQUEST

Send a pretend request through your policy.
No wallet. No real funds. Just a clear answer.

USDC
min
WAITING AT THE LATCH

A yes should have a reason.

Your first request will be checked against all three limits.

    Approved requests spend demo USDC. Denied requests leave your budget untouched. Changing rules keeps previous demo spending.

    Test a request to preview the next step.

    Request trail

    0 REQUESTS

    Nothing through the door. Yet.

    02 / A SMALLER LEAP OF FAITH

    Trust isn't
    a blank check.

    01

    Give a budget, not a blank check.

    Every approved request counts toward the same allowance. A small limit makes the consequences easier to understand.

    02

    Permission should have an ending.

    A session closes at its time limit. Explore that boundary by changing the simulated elapsed time.

    03

    Let the right tools in.

    Reading a balance and moving it are very different privileges. Keep each capability a deliberate choice.

    ONCHAIN POLICY REGISTRATION

    One more latch.
    Coming soon.

    The local sandbox is ready. Registering an enforceable policy still needs a deployed contract and a wallet signing flow.

    No transaction has been sent. Your sandbox stays just as you left it.