Security

Last updated 22 October 2026

The agent runs in a locked-down container per session, with no network unless a person approves a command. Every action is recorded in a history that nobody, including the agent, can rewrite.

Sandboxing

One container per session, with CPU, memory and process limits, all Linux capabilities dropped, and running as an unprivileged user.
No network by default. A command that needs it, such as installing a package, waits for approval and then runs in a separate one-off container.
The container and its volume are removed when the session ends.

Approvals and history

Pushes, file deletions, network access and writes outside the workspace wait for a person in the session.
Session settings decide whether only the driver, or anyone in the session, can approve.
The session is an append-only event log. Every message, approval, edit and command is attributed to a person or to the agent, with a timestamp.

Accounts and data

Sign-in uses GitHub OAuth. Login cookies are signed, HttpOnly, Secure and SameSite.
GitHub tokens are encrypted at rest with AES-256-GCM.
All traffic is served over HTTPS. Pages use a strict Content Security Policy with no third-party scripts.
State-changing requests are checked against the app's origin.

Reporting a vulnerability

Email security@gethuddle.dev with steps to reproduce. We acknowledge reports within two working days and will keep you updated until it is fixed. Please give us a reasonable time to fix an issue before you publish it, and do not access other people's data while testing.