OpenHands

Context

Uses repository workspaces, conversation state, file content, command output, runtime observations, and integrations exposed through the platform or SDK.

Actions

Executes commands, edits files, interacts with development environments, and can be extended through SDK components and integrations.

Execution

Workspace abstractions support local processes, Docker containers, and remote API workspaces. The Docker runtime is designed to isolate arbitrary agent-executed code from the host.

Memory & rules

Conversation and workspace state live in the platform; project guidance depends on the selected agent, app configuration, and repository files rather than one universal instruction format.

Permissions

Isolation comes primarily from the chosen runtime and workspace configuration. Host mounts, network access, secrets, and remote services still require explicit operator policy.

Verification

Agents can run builds, tests, and commands inside the runtime and return the resulting changes and logs for review.

Best for

• Teams building or self-hosting developer-agent systems
• Experiments needing an isolated execution runtime
• Developers who want an SDK and platform rather than one fixed UI

Limitations

• Editorial judgment: lightweight one-command pair programming
• Editorial judgment: operators unwilling to manage images, runtimes, credentials, and platform upgrades