Directory / OpenHands
OpenHands
Runs actions in a Docker sandbox by default. Confirmation mode plus an LLM security analyzer can pause risky actions for a human.
Lock this down first
Set SECURITY_CONFIRMATION_MODE=true so risky actions wait for you.
Scorecard
| Criterion | Rating | Notes |
|---|---|---|
| Permission granularity | Unverified | Not confirmed in the docs we checked. |
| Human approval gates | 2/3 | Confirmation mode and a risk analyzer, configured by env or SDK. |
| Sandboxing | 2/3 | Docker sandbox is the default runtime. |
| Secrets handling | 2/3 | Secrets manager exports values as env vars. The SDK SecretRegistry masks secret values in tool output. |
| Audit logs | Unverified | Not confirmed in the docs we checked. |
| Kill switch / interrupt | 2/3 | Conversations and sandboxes can be paused, resumed or deleted via SDK and API. |
| Network egress control | Unverified | Not confirmed in the docs we checked. |
Sources
- https://docs.openhands.dev/openhands/usage/sandboxes/docker
- https://docs.openhands.dev/openhands/usage/environment-variables
- https://docs.openhands.dev/sdk/guides/security
- https://docs.openhands.dev/openhands/usage/settings/secrets-settings
- https://docs.openhands.dev/enterprise/conversations-and-sandboxes
Vendor? Request a correction. We review corrections within 7 days.
