TAKO SECURITY

Let agents work.
Keep control.

Your permissions. Their actions.
A clear record of what happened.

01 / THE SECURITY ARM

Connect an agent.
Define its limits.
Understand every exception.

LOCAL PRODUCT BUILD · SEPT 2026

From permission to proof.

RECORDED PRODUCT WALKTHROUGH / 1080P

Actual browser interactions with Tako's local service and SDK.
A labelled test scenario: six requests, three refusals, zero executions of the disallowed outbound tool.

Download film ↓

ONE CONNECTED WORKFLOW

Clarity at every step.

Built around decisions you can inspect
and permissions you can change.

01 / PERMISSIONS

Set the boundary.

Pin approved tool definitions. Set call and repetition limits. Keep policy changes under owner control.

02 / INVESTIGATION

See why it stopped.

Open the finding and follow it to the exact run, request, policy version, and reported result.

03 / VERIFICATION

Test before applying.

Compare a candidate policy against recorded request features. Export the evidence. Apply changes separately.

Tako investigation showing why the outbound tool was outside its approved permission — One finding. The evidence behind it.

Policy comparison showing original and candidate decisions for the same recorded requests — Compare decisions before changing authority.

THE CURRENT BUILD

Useful now.
Explicit about its scope.

The local workspace includes a Go service, a TypeScript connector, durable tool-request records, owner policies, issue investigation, policy replay, and evidence export.

The dispatcher controls supported calls routed through it. This demonstration uses local test tools; it does not move funds, run a model, or demonstrate an onchain executor. Replay compares recorded features and does not re-run an agent.

Next financial milestone: an account-enforced grant on testnet.

View recording details ↗

Let agents work.Keep control.