Kilo Code CLI vs OpenHands

Kilo Code CLI

Shell commands ask before running by default, and an optional operating-system sandbox blocks writes outside the workspace and outbound network. Telemetry to PostHog is on by default and the sandbox is off, so an unattended kilo run --auto approves everything not denied unless both are configured first.

OpenHands

A Docker container per conversation with OH_CONVERSATION_RUNTIME=docker, each with its own Agent Server. Confirmation mode is off by default in Agent Canvas, and the npm install gives the agent the host's whole filesystem.

Kilo Code CLI

1. Set sandbox.enabled to true in the global kilo.jsonc before kilo run --auto. --auto approves every permission request not explicitly denied
2. Set experimental.openTelemetry to false, or KILO_TELEMETRY_LEVEL to a value other than all, to stop telemetry
3. Add needed hosts to sandbox.allowed_hosts in global config. MCP tool calls are unavailable while network restriction is on
4. Without --auto a non-interactive run rejects every permission prompt and exits 1
5. Put provider keys in global config or the environment. {env:VAR} in a project kilo.json is ignored

OpenHands

1. Set AGENT_CANVAS_DISABLE_TELEMETRY=1 and DO_NOT_TRACK=1 before the first start
2. Start Canvas with OH_CONVERSATION_RUNTIME=docker or use the Docker image. The npm install runs the agent on the host
3. Turn on confirmation mode with a risk threshold. Canvas starts with it off
4. Use the SDK or the Agent Server API for headless runs. The openhands --headless CLI is no longer maintained
5. Set filter_tools_regex on the agent to keep unneeded MCP tool definitions out of the context