agent-ops-patterns / gallery / OpenHands map / how it decides

How OpenHands decides

This card covers the OpenHands agent SDK, the library that the OpenHands command-line tool and OpenHands Cloud are built on, and not the OpenHands app or its screens. On its default settings the SDK never stops to ask for your approval, even after an app gives the agent tools to run commands and edit files. An app built on it can turn approvals on, but deciding when the work is done and what to remember stays with plain code and AI models.

From OpenHands/software-agent-sdk at source version aae9c437, mapped 2026-10-06. Each answer links the place in the code where that decision is made; the full map has the rest.

What it does without asking you

How it decides it is done

Limits and memory

Three problems in the code

  1. 1. A new message can count as approval

    When the approval policy calls for it, the agent pauses before an action until the app approves or rejects it. If you send a new message instead, and the app then runs the conversation again without rejecting, the waiting action is attempted as if you had approved it. A message saying "wait, not that" does not by itself cancel the action.

    Reported; a fix is proposed, not merged (#5092), checked 2026-11-15.

    Where: local_conversation.py:1981-1988, agent.py:713-722. How we checked: the code was re-read at the source version named above; the sentences were checked by an independent AI reviewer from another company (OpenAI Codex, read-only) in four rounds on 2026-10-18.

  2. 2. The goal judge can read "false" as done

    With the goal feature, a judge model is asked for a short structured reply that includes a "complete" field. The code turns that field into yes or no with a Python conversion (bool) that counts any non-empty text as yes, including the word "false". So if the judge writes "false" as text in that field, the goal is marked complete.

    Reported; a fix is proposed, not merged (#5492), checked 2026-11-15.

    Where: judge.py:128. How we checked: the code was re-read at the source version named above; the sentences were checked by an independent AI reviewer from another company (OpenAI Codex, read-only) in four rounds on 2026-10-18.

  3. 3. A secret inside a tool request is recorded unmasked

    You can register secrets, such as service access keys, so they are masked in text replies that contain no request to use a tool. When the model puts a registered secret into a request to use a tool, such as a shell command, the details of that request are written to the conversation record without masking, and when the model gives no summary of the request, the automatic summary repeats them. Anyone who can read that record can read the key.

    Reported; no linked fix found (#5525), checked 2026-11-15.

    Where: agent.py:1374-1379, agent.py:1243-1245. How we checked: the code was re-read at the source version named above; the sentences were checked by an independent AI reviewer from another company (OpenAI Codex, read-only) in four rounds on 2026-10-18.

See the full map →

This card was taken from the published map of the OpenHands agent SDK at one commit; it did not look at the OpenHands app or its screens, at the hosted services the SDK can call, or at code outside the map's folders, and no OpenHands code was run to make it.

Map: second edition · taken from the full map · card data: gallery/cards/openhands.json. Found something wrong? Use the correction form.