Sandbox

Test your agent before it touches real users.

A sandbox is a safe test environment. In Hussh, it lets you run an agent with synthetic personas, simulated Nav approvals, and consent-gated context before you register it for real use.

What the sandbox helps you test

It is not production. It is where you prove the agent can be useful, respectful, and safe before it receives real user context.

01

Run against synthetic personas instead of real users.

02

Simulate what Nav asks the user to approve.

03

Verify only approved context reaches the agent.

04

Check the agent response when context is denied or limited.

05

Capture evidence before review or registration.

What you can inspect

The sandbox shows the important trust moments clearly so a builder can fix the agent before review.

Synthetic users

Try the agent against representative people and situations without touching real private data.

Consent decisions

See what the user would be asked, what they approve, and what they decline.

Released context

Inspect the exact fields the specialist receives after Nav mediates access.

Useful output

Confirm the agent still produces a meaningful result inside the approved boundary.

Run it where you build

Hussh does not force your agent into one runtime. Bring the environment that fits the job while Hussh keeps the personal-context boundary consistent.

Local and MLX

Run a local specialist or Apple-silicon model path while Hussh simulates the consent boundary.

OpenClaw and agent runtimes

Bring framework-native agents into a Hussh run without changing the user-context contract.

Google ADK

Use the Python SDK path for ADK-first personal-agent development.

BYOC service

Keep your production logic in your own cloud, HTTP service, or enterprise environment.