Agent activity: messages, events and lifecycle

Run control-openhands conversation start --prompt "Run the terminal command 'echo qa-f06-hello', then create a file qa_f06.txt containing the word hi. Finally reply with a markdown table with columns Step and Result (two rows) followed by a python code block that prints 1." --wait --timeout 300, then control-openhands browser testids 'testid=chat-interface' and control-openhands browser snapshot 'testid=agent-message'. The testids include user-message, event-group ("3 actions completed"), agent-message, markdown-table-scroll with markdown-table-scroll-fade-left/-right; the snapshot shows a table with column headers Step and Result and a code block print(1). Compare with control-openhands conversation events <id>: one user and one agent MessageEvent, three ActionEvents (terminal, file_editor, canvas_ui_control), matching one user-message, one group of three rows and one agent-message. The thinking row (collapsible-thinking) lives inside the group, so it is listed only after the next bullet expands it.

Run control-openhands browser click 'testid=event-group-toggle' (label becomes Collapse actions), control-openhands browser text 'testid=event-group' (three titles, e.g. "Echo test string in terminal", "Create qa_f06.txt containing hi"; titles are model-written), then control-openhands browser click 'testid=event-group-content >> role=button[name="Expand"][exact] >> nth=0' twice (each click expands the next collapsed row). The group text now contains echo qa-f06-hello and its output qa-f06-hello, the file path chip (testid=file-path-chip) and the content hi. control-openhands browser click 'testid=collapsible-thinking-toggle >> nth=0' reveals collapsible-thinking-content. Take control-openhands browser screenshot 'testid=chat-interface' --feature F06.tool-visualizers --name bash-and-file.

On the same page the agent may already have opened the file; run control-openhands browser click 'testid=file-quick-row-close-qa_f06.txt' and check control-openhands browser count 'testid=file-quick-row-item-qa_f06.txt' is 0. Run control-openhands browser click 'testid=agent-message >> testid=markdown-file-path-link': the count is 1 and control-openhands browser text 'testid=file-content-viewer-plain' is hi. Close it again and control-openhands browser click 'testid=file-path-chip' (inside the expanded file-editor row): the count is 1 again.

Run control-openhands conversation start --prompt "Use the file_editor tool to create the file qa_notes.md containing a heading '# QA Notes' and one bullet '- first'. Do nothing else and reply DONE." --wait --timeout 150. Without any click, control-openhands browser text 'testid=markdown-file-preview' reads QA Notes first qa_notes.md View (rendered heading and bullet, then the file name) and count 'testid=event-group' is 0. control-openhands browser count 'testid=file-quick-row-item-qa_notes.md' is 0; control-openhands browser click 'testid=markdown-file-preview-view' makes it 1 and control-openhands browser text 'testid=file-content-viewer-markdown' reads QA Notes first. Then control-openhands browser goto /conversations/<stream id> to return to the stream conversation for the next bullets.

Run control-openhands browser tooltip 'testid=user-message' and control-openhands browser tooltip 'testid=event-group-toggle'. Both return the local date and time, e.g. Oct 4, 2026, 11:08 PM.

On the same page run control-openhands browser clipboard --write qa-empty, control-openhands browser hover 'testid=agent-message >> nth=0' and control-openhands browser click 'testid=agent-message >> nth=0 >> testid=copy-to-clipboard >> nth=0' (the bubble's button; the code block has a second, hidden copy-to-clipboard). control-openhands browser attr 'testid=agent-message >> nth=0 >> testid=copy-to-clipboard >> nth=0' aria-label is Copied to clipboard, and Copy to clipboard again about 2 s later; control-openhands browser clipboard starts with | Step | Result | and ends with the fenced print(1) block. Then control-openhands browser hover 'testid=agent-message >> pre', control-openhands browser click 'testid=agent-message >> pre >> testid=copy-to-clipboard' and control-openhands browser clipboard is exactly print(1).

On the stream conversation write a prompt file whose first line is Reply with only the word OK. Do not run any tools., then a blank line and the table | Name | Description | Status |, |---|---|---|, | Alpha | This is a really long sentence in a single cell that goes on and on to explain a very involved aspect of the system, which nobody could read on one line without scrolling forever to the right. | ok |, | Beta | brief | fail |. Run control-openhands browser fill 'testid=chat-input' x --value-file <file>, control-openhands browser click 'testid=submit-button' and control-openhands conversation wait <id> --fresh --timeout 120; the user bubble renders the table. Cells wrap once they reach 28rem (max-w-md): control-openhands browser eval "getComputedStyle(document.querySelector('[data-testid=markdown-table-scroll] td')).whiteSpace + ' ' + getComputedStyle(document.querySelector('[data-testid=markdown-table-scroll] td')).maxWidth" is normal 448px. At desktop with the right panel closed, control-openhands browser bbox 'testid=user-message >> nth=-1 >> testid=markdown-table-scroll' has scrollWidth 582 equal to clientWidth and Status is visible (browser screenshot 'testid=chat-interface' --feature F06.markdown-rendering --name long-cell-table). A table still wider than the conversation keeps the horizontal scroll with its edge fade: with the panel open (control-openhands browser click 'testid=right-panel-toggle') clientWidth is 474, and at phone width 326, so Status is scrolled off there while the long cell stays wrapped. An agent reply with such a table behaves the same.

In an open conversation run control-openhands browser fill 'testid=chat-input' "Run exactly this terminal command, verbatim, with nothing appended: ls /qa_missing_dir2 . Then reply OK.", control-openhands browser click 'testid=submit-button' and control-openhands conversation wait <id> --fresh --timeout 150 (without --fresh it returns the previous run's finished at once). If the reply's actions render as a single row, run control-openhands browser click 'testid=chat-scroll-container >> role=button[name="Expand"][exact] >> nth=-1'; if they render as a group (browser count 'testid=event-group' grew, e.g. 2 actions completed after a terminal reset and rerun), run control-openhands browser click 'testid=event-group-toggle >> nth=-1' and control-openhands browser click 'testid=event-group-content >> nth=-1 >> role=button[name="Expand"][exact] >> nth=-1'. Then control-openhands browser count 'testid=chat-scroll-container >> text="exit 2"' is 1; the badge sits above the No such file or directory output (browser screenshot 'testid=event-group >> nth=-1' --feature F06.tool-visualizers --name exit-code). Repeating the check in the same conversation needs a new directory name and a count that grows, because an earlier expanded badge stays on the page.

From / run control-openhands browser goto /, control-openhands browser fill 'testid=chat-input' "Use your task_tracker tool to plan exactly two tasks titled 'qa step one' and 'qa step two'; mark 'qa step one' done and 'qa step two' todo. Do nothing else and reply DONE." and control-openhands browser click 'testid=submit-button' --expect-url '/conversations/' --observe '[data-testid=chat-status-indicator]' --observe-ms 8000. observed contains Starting for a moment (the pill). Then control-openhands conversation wait <id> --timeout 150 and control-openhands browser text 'testid=chat-scroll-container': it contains Tasks, qa step one, qa step two; the screenshot shows a check icon and muted text for the done task, an empty circle for the todo one.

Run control-openhands browser click 'testid=conversation-panel-new-thread-picker', control-openhands browser click 'testid=launch-no-workspace' --expect-url '/conversations/', then control-openhands browser text 'testid=chat-suggestions': Let's start building! plus Increase test coverage, Auto-merge PRs, Fix README, Clean dependencies. Run control-openhands browser click 'testid=chat-suggestions >> text=Fix README' and control-openhands browser text 'testid=chat-input': the composer holds the README-improvement prompt.

Write a 25-line message to a file (first line Reply with only the word OK. Ignore the filler lines below., then filler line 1…filler line 24), run control-openhands browser fill 'testid=chat-input' x --value-file <file> and control-openhands browser click 'testid=submit-button' --observe '[data-testid=chat-message-sending]' --observe-ms 3000. observed shows Sending... then <absent> once the server echoes it. After control-openhands conversation wait <id> --timeout 120, control-openhands browser testids 'testid=chat-scroll-container' lists chat-message-truncation-gradient and chat-message-expand ("View More"); control-openhands browser click 'testid=chat-message-expand' removes both and the whole text shows. testid=agent-message reads OK.

On the same conversation, skew the page's clock before loading it: control-openhands browser clock --offset-ms 300000, control-openhands browser goto /conversations/<id>, control-openhands browser wait 'testid=chat-input'; control-openhands browser eval "new Date().toISOString()" is about five minutes ahead of date -u (read-only shell check). Run control-openhands browser fill 'testid=chat-input' 'Reply with only: clock-ok' and control-openhands browser click 'testid=submit-button' --observe '[data-testid=chat-message-sending],[data-testid=chat-message-error]' --observe-ms 6000: observed shows Sending... and then <absent> (the server echo confirmed it), never Failed to send. control-openhands browser count 'testid=chat-message-sending' and control-openhands browser count 'testid=chat-message-retry' are 0, and control-openhands conversation events <id> --kinds MessageEvent gains one user row Reply with only: clock-ok whose ts is the server's time (close to date -u), not the browser's. Undo the skew before moving on: control-openhands browser clock --offset-ms 0 and control-openhands browser reload (with a model, control-openhands conversation wait <id> --fresh --timeout 120 first).

With a conversation open run control-openhands service stop agent-server and control-openhands browser wait 'testid=error-message-banner' --timeout 20000: the banner reads Unable to connect to server with error-message-banner-retry, -copy and -dismiss; the composer shows Disconnected. Run control-openhands browser fill 'testid=chat-input' 'Reply with only the word PONG.' and control-openhands browser click 'testid=submit-button' --observe '[data-testid=chat-message-sending],[data-testid=chat-message-error]' --observe-ms 8000: Sending... turns into Failed to send Retry Dismiss. control-openhands browser click 'testid=chat-message-retry' while down fails again; control-openhands browser click 'testid=chat-message-dismiss' removes the bubble (count 'testid=chat-message-error' is 0). Send the same message again so one failed bubble remains, control-openhands browser click 'testid=error-message-banner-dismiss' (banner count 0), then control-openhands restart. Poll control-openhands browser text 'testid=interactive-chat-box' every 10 s: within about a minute after restart returns it no longer contains Disconnected (reconnected without reload). control-openhands browser click 'testid=chat-message-retry', control-openhands conversation wait <id> --timeout 120, then control-openhands conversation events <id> --kinds MessageEvent: Reply with only the word PONG. appears once and the last agent-message is PONG.

Run control-openhands service stop agent-server, wait for testid=error-message-banner as above, control-openhands restart, then control-openhands browser click 'testid=error-message-banner-retry'. control-openhands browser count 'testid=error-message-banner' is 0 and the composer is no longer Disconnected. Take browser screenshot 'testid=chat-interface' --feature F06.error-banner --name disconnected while the banner is up.

With /conversations/<id> open and healthy, run control-openhands service stop agent-server, control-openhands browser wait 'testid=error-message-banner' --timeout 20000, control-openhands browser fill 'testid=chat-input' 'Reply with only: retry-ok' and control-openhands browser click 'testid=submit-button' --observe '[data-testid=chat-message-sending],[data-testid=chat-message-error]' --observe-ms 8000: Sending... turns into Failed to send Retry Dismiss and control-openhands browser count 'testid=chat-message-retry' is 1 (control-openhands browser screenshot 'testid=chat-interface' --feature F06.failed-send-persists --name failed-before-leaving). Run control-openhands restart and control-openhands browser wait 'testid=error-message-banner' --state hidden --timeout 90000 (the page reconnects by itself; testid=error-message-banner-retry hurries it while the banner is still up): the Retry row is still there (count 1). Leave through the sidebar and come back: control-openhands browser click 'role=link[name="New Chat"]', control-openhands browser wait 'testid=home-chat-launcher', control-openhands browser click 'a[href*="/conversations/<id>"] >> nth=0' --expect-url '/conversations/<id>', control-openhands browser wait 'testid=user-message'; control-openhands browser count 'testid=chat-message-retry' is still 1 after the history reloaded (control-openhands browser screenshot 'testid=chat-interface' --feature F06.failed-send-persists --name retry-after-reopen). Send the same text again (fill Reply with only: retry-ok, click testid=submit-button with the same --observe): the new bubble goes Sending... and settles while Failed to send Retry Dismiss stays; control-openhands browser count 'testid=chat-message-sending' is 0, control-openhands browser count 'testid=chat-message-retry' is 1, and the rows of control-openhands conversation events <id> --kinds MessageEvent --grep 'retry-ok' whose source is user number exactly one, Reply with only: retry-ok (in a model-free run count is 1; with a model the agent's retry-ok reply matches the grep too, so count the user rows, not count). Then control-openhands browser click 'testid=chat-message-retry' and control-openhands browser wait 'testid=chat-message-retry' --state detached --timeout 15000: control-openhands browser count 'testid=chat-message-sending' is 0 and the same --grep now lists exactly two user rows Reply with only: retry-ok (one per attempt, none duplicated). With a model, control-openhands conversation wait <id> --fresh --timeout 120 before the next bullet.

Run control-openhands conversation start --prompt "Run exactly one terminal command: sleep 25 && echo qa-slept. Then reply with only its output." (no --wait), control-openhands browser wait 'testid=live-activity-chip' --timeout 30000 and control-openhands browser text 'testid=live-activity-chip': first Thinking, then the action title (e.g. Run sleep 25 then echo qa-slept); browser text 'testid=interactive-chat-box' contains Running. Run control-openhands browser click 'testid=stop-button': control-openhands conversation status <id> is paused, the composer reads Stopped, count 'testid=play-button' is 1 and the chip is gone. Stop interrupts the running sleep too: control-openhands conversation events <id> shows an AgentErrorEvent (Tool call interrupted before completion. The conversation was paused.) followed by an InterruptEvent, and browser text 'testid=chat-scroll-container' shows an Agent error row under the action title. Run control-openhands browser click 'testid=play-button': status running, then control-openhands conversation wait <id> --timeout 120 ends finished with a new agent MessageEvent (the model reports that the command was interrupted; qa-slept never prints).

Run control-openhands conversation start --prompt "Run exactly one terminal command: sleep 15 && echo qa-reloaded. Then reply with only its output.", wait for testid=live-activity-chip, then control-openhands browser reload. The composer still reads Running and the chip is back. After control-openhands conversation wait <id> --timeout 120: testid=agent-message is qa-reloaded, count 'testid=user-message' is 1, control-openhands browser eval "document.querySelectorAll('[data-testid=chat-scroll-container] [data-testid=generic-event-message-title]').length" is 1.

Run control-openhands conversation start --prompt "Run these 16 terminal commands strictly one per tool call, sequentially (never combine them): echo qa1, echo qa2, echo qa3, echo qa4, echo qa5, echo qa6, echo qa7, echo qa8, echo qa9, echo qa10, echo qa11, echo qa12, echo qa13, echo qa14, echo qa15, echo qa16. Then reply DONE." --wait --timeout 400 (note <history-id>); control-openhands conversation events <history-id> --last 500 reports a count above 50. Run control-openhands browser network --clear, control-openhands browser reload, then control-openhands browser network --last 300: two GET /api/conversations/<history-id>/events/search requests (newest page, then the older page). control-openhands browser text 'testid=chat-scroll-container' starts with the prompt and shows 16 actions completed and DONE. The other trigger is the user scrolling to the top, driven without a model on the dummy profile from Preconditions (qa-zeta active; in a keyed run create and activate it with that same llm set command for this bullet, then re-run control-openhands llm preset deepseek and remove it with control-openhands api DELETE /api/profiles/qa-zeta --write, so later families still count two profiles; arrange, not proof). Run control-openhands conversation start --prompt "qa older 1" (no --wait; note <older-id>), then for N in $(seq 2 30); do control-openhands conversation send <older-id> --prompt "qa older $N"; done: every send is accepted while the agent sits in error, about 1.5 s apiece (42 s for the 29 here), and each refused message adds five events (a MessageEvent, three ConversationStateUpdateEvents, a ConversationErrorEvent), so the conversation ends with about 150 events (152 here). control-openhands conversation events <older-id> --last 500 reports "total": 152, "pages": 2, "more": false (both server pages read, see Gotchas); its first row is the SystemPromptEvent and the first MessageEvent is qa older 1, while --last 25 reports "pages": 1, "more": true and starts at qa older 26. Run control-openhands browser network --clear, control-openhands browser reload, control-openhands browser wait 'testid=chat-input', then control-openhands browser network --filter 'events/search' --last 10: two requests, ?limit=50&sort_order=TIMESTAMP_DESC and one with timestamp__lt=<ts of qa older 21>, because the newest 50 events hold only ten bubbles, shorter than the viewport, so the automatic fetch ran once and then stopped. control-openhands browser count 'testid=user-message' is 20, control-openhands browser text 'testid=chat-scroll-container' starts qa older 11 and holds none of qa older 1…qa older 10, and control-openhands browser bbox 'testid=chat-scroll-container' has scrollHeight 1576 against clientHeight 814: taller than the viewport, so the third page waits for the user. Run control-openhands browser scroll 'testid=chat-scroll-container' --by -100000: control-openhands browser network --filter 'events/search' --last 5 gains a request with timestamp__lt=<ts of qa older 11>, control-openhands browser count 'testid=user-message' is 29 and the text starts qa older 2 (that page held messages 2–10 plus the tail of the first message's events; not seen in two runs: if the first refusal ever logs six events instead of seven, the arithmetic gives count 30, text qa older 1 and a last page of only the SystemPromptEvent), and the view stays on qa older 11: control-openhands browser eval "document.querySelector('[data-testid=chat-scroll-container]').scrollTop" is 684, the height of the prepended rows. Scroll to the top again the same way: a fourth request (timestamp__lt= the oldest loaded event), the count is 30, the text starts qa older 1 and scrollTop is 76 (control-openhands browser screenshot 'testid=chat-interface' --feature F06.load-older-history --name scroll-top-loaded-qa-older-1). A third scroll adds no request: the short page ended the paging. control-openhands browser count 'testid=loading-older-events' is 0 after each scroll because the Fetching older messages… row lasts a few tens of milliseconds on a local stack; to see it, scroll with control-openhands browser scroll 'testid=chat-scroll-container' --by -100000 --observe 'testid=loading-older-events' --observe-ms 1500 instead (both scrolls were driven this way here, with the same counts), whose observed goes <absent> at 0 ms, Fetching older messages… at about 20 ms and <absent> again within about 40 to 120 ms (116 ms on the first scroll, 39 on the second; observedBy mutation); the timestamp__lt= network rows remain the durable proof. Return to the 16-command conversation for the next bullet: control-openhands browser goto /conversations/<history-id> and control-openhands browser wait 'testid=chat-input'.

On the 16-command conversation (<history-id>; in a model-free run this bullet is blocked with the automatic-fetch half, prerequisite DEEPSEEK_API_KEY), control-openhands browser click 'testid=event-group-toggle' makes the transcript taller than the viewport while the view stays where it was. Run control-openhands browser scroll 'testid=chat-scroll-container' --by 2000 first (the button only reacts to scroll events, so a page that is already at the top never shows it): count 'testid=scroll-to-bottom' is 0. Run control-openhands browser scroll 'testid=chat-scroll-container' --by -2000; the count is 1. control-openhands browser click 'testid=scroll-to-bottom', then the count is 0 and control-openhands browser eval "(()=>{const e=document.querySelector('[data-testid=chat-scroll-container]');return Math.round(e.scrollHeight-e.scrollTop-e.clientHeight)})()" is 0.

Arrange through the settings UI, in this order (the Security Analyzer field appears only once Confirmation Mode is on): control-openhands browser goto /settings/verification, control-openhands browser click 'testid=verification-settings-screen >> text=Confirmation Mode', control-openhands browser click 'testid=sdk-section-all-toggle', control-openhands browser click 'testid=verification-settings-screen >> role=button[name="Show suggestions"]', control-openhands browser click 'role=listbox >> role=option[name="None"]', control-openhands browser value 'testid=verification-settings-screen >> role=combobox[name="Security Analyzer"]' (None), control-openhands browser click 'testid=verification-settings-screen >> testid=save-button'; control-openhands api GET /api/settings shows "confirmation_mode": true and "security_analyzer": "none" (None means every action is confirmed; the default LLM analyzer only stops HIGH-risk actions, so echo would run unprompted). Run control-openhands conversation start --prompt "Run the terminal command 'echo qa-confirm-ok' and reply with its output." --wait --timeout 180: it returns "status": "waiting_for_confirmation". control-openhands browser text 'testid=chat-scroll-container' ends Do you want to continue with this action? Cancel Ctrl+⇧+⌫ Continue Ctrl+↩ on Linux (Cancel ⇧⌘⌫ Continue ⌘↩ on macOS, #18127), control-openhands browser tooltip 'testid=action-confirm-button' is Confirm the requested action, and a lock icon sits above the composer (screenshot). The tooltip stays open over the Cancel button, so move the pointer first: control-openhands browser hover 'testid=chat-input'. Run control-openhands browser click 'testid=action-reject-button': status idle, the buttons are gone, conversation events <id> --last 6 ends with UserRejectObservation, and the action's row reads Rejected (control-openhands browser count 'testid=rejected-indicator' is 1) with no spinner. Send Run the terminal command 'echo qa-confirm-two' and reply with its output. through testid=chat-input / testid=submit-button, control-openhands browser wait 'testid=action-confirm-button' --timeout 20000, control-openhands browser click 'testid=action-confirm-button'; about 15 s later the status is finished and the events contain the observation qa-confirm-two. A rejection inside a group resolves it too: send Run the terminal command 'echo qa-g1'. After it finishes, run the terminal command 'echo qa-g2' as a separate tool call. Then reply DONE., continue the first action (browser wait 'testid=action-confirm-button', then control-openhands browser press Control+Enter, which is also the next bullet's shortcut) and cancel the second (browser wait 'testid=action-confirm-button' --timeout 60000, control-openhands browser press Control+Shift+Backspace): status idle, control-openhands browser text 'testid=event-group >> nth=-1' ends 2 actions completed, control-openhands browser count 'testid=event-group >> nth=-1 >> .animate-spin' is 0, the same after browser reload, and the expanded group (control-openhands browser click 'testid=event-group >> nth=-1 >> button >> nth=0') shows Rejected on the qa-g2 row (browser screenshot 'testid=chat-interface' --feature F06.confirmation-mode --name group-after-reload). Each button keeps its label and hint on one line: while the prompt is waiting, control-openhands browser eval "[...document.querySelectorAll('[data-testid=action-reject-button],[data-testid=action-confirm-button]')].map(b=>b.offsetHeight+'/'+b.scrollHeight).join(' ')" is 26/26 26/26 at desktop, also with the side panel open (testid=right-panel-toggle). At phone width (browser viewport phone) the shortcut hints are hidden (no hardware keyboard), the buttons read Cancel and Continue, and browser text 'testid=chat-scroll-container' ends Do you want to continue with this action? Cancel Continue (screenshot the awaiting prompt at phone width).

The previous bullet resolved its action, so arrange a new one in the same conversation: send Run the terminal command 'echo qa-confirm-three' and reply with its output. through testid=chat-input / testid=submit-button and control-openhands browser wait 'testid=action-confirm-button' --timeout 20000. control-openhands browser text 'testid=action-confirm-button' is Continue Ctrl+↩ off macOS. Ctrl works off macOS (#17928, fixed by #18127): the previous bullet's Control+Enter continued and Control+Shift+Backspace cancelled. control-openhands browser press Meta+Enter continues too: control-openhands conversation wait <id> --fresh --timeout 120 ends finished and control-openhands conversation events <id> --kinds ObservationEvent contains qa-confirm-three. Restore afterwards: browser goto /settings/verification, click testid=sdk-section-all-toggle, Show suggestions, role=listbox >> role=option[name="LLM"], then testid=verification-settings-screen >> text=Confirmation Mode, then save-button; api GET /api/settings shows "confirmation_mode": false, "security_analyzer": "llm".

Open a conversation with at least two exchanges (the OK/PONG one above): control-openhands browser goto /conversations/<id> with its id (the previous bullet left /settings/verification). Agent message: control-openhands browser hover 'testid=agent-message >> nth=0', control-openhands browser click 'testid=agent-message >> nth=0 >> role=button[name="Branch from here"]' --expect-url '/conversations/(?!<id>)'; after control-openhands browser wait 'testid=user-message' (the history mounts a moment after the URL changes, so an immediate count reads 0) the new conversation has count 'testid=user-message' 1, the agent message OK, and browser eval "document.title" contains (branch). User message (edit): back on the OK/PONG conversation (control-openhands browser goto /conversations/<id>; the branch above has one user message), control-openhands browser hover 'testid=user-message >> nth=1' and control-openhands browser click 'testid=user-message >> nth=1 >> role=button[name="Branch from here"]' --observe '[data-testid=chat-input]' --observe-ms 4000: observed shows the composer change from empty to Reply with only the word PONG. and stay. The new conversation (<branch-id> from browser url) omits that message, control-openhands browser text 'testid=chat-input' is Reply with only the word PONG., and nothing was sent: control-openhands conversation events <branch-id> --kinds MessageEvent lists only the copied first exchange (count 2: the long message that starts Reply with only the word OK., then OK; no PONG). control-openhands browser enabled 'testid=submit-button' should be true with the prefilled text; today it is false until the text is edited or the page is reloaded (see Gotchas). Send it with control-openhands browser press Enter --selector 'testid=chat-input' (Enter sends whatever the Send button's state is) and control-openhands conversation wait <branch-id> --fresh --timeout 120: expected finished with a reply; today it ends error (Agent Server bug, see Gotchas).

Run control-openhands fixture image --name qa-f06-img (prints the PNG path), control-openhands browser upload 'testid=upload-image-input' <png path> (a thumbnail appears in the composer), fill testid=chat-input with Reply with only the word SEEN. and click testid=submit-button. The user bubble contains image-carousel / image-preview. Run control-openhands browser hover 'testid=image-preview', control-openhands browser click 'testid=expand-image-button' (count 'testid=image-lightbox' is 1), control-openhands browser press Escape (0), click expand-image-button again and control-openhands browser click 'testid=image-lightbox-close' (0).

Any run that ends in a ConversationErrorEvent (today: any message sent in a branched conversation) leaves conversation wait <id> at "status": "error"; control-openhands browser testids 'testid=chat-interface' lists error-message-banner with warning-message-banner-icon and the error's text, and the composer status reads Error. Read the code with control-openhands api GET "/api/conversations/<id>/events/search?limit=3&sort_order=TIMESTAMP_DESC".

The banner keys on the installer's success line in terminal output. Put this one line in a prompt file: Run exactly this one terminal command, verbatim, then reply DONE: mkdir -p .agents/skills/qa-skill && printf '# qa-skill\n' > .agents/skills/qa-skill/SKILL.md && echo "✅ Successfully installed 'qa-skill' to $PWD/.agents/skills/qa-skill", then run control-openhands conversation start --prompt "$(cat <prompt file>)" --wait --timeout 150. control-openhands browser text 'testid=skill-install-restart-banner' reads Installed to this workspace: qa-skill. Skills load when a conversation starts, so this conversation can't use them yet. Run control-openhands browser click 'testid=skill-install-restart-action' --expect-url '/conversations/(?!<id>)'; control-openhands api GET /api/conversations/<new id> has the same workspace.working_dir as the source. Back on the source (control-openhands browser goto /conversations/<id>), control-openhands browser click 'testid=skill-install-restart-dismiss' hides it (count 0); after browser reload it is back (dismissal is session-only by design).

On the fresh no-LLM run: control-openhands onboard --skip, control-openhands browser click 'testid=conversation-panel-new-thread-picker', control-openhands browser click 'testid=launch-no-workspace' --expect-url '/conversations/'. control-openhands browser text 'testid=home-llm-not-configured-banner' reads Your LLM isn't set up yet, so conversations won't run. Finish setup to get started. Set up LLM; count 'testid=chat-suggestions' is 0; the composer cannot take text (control-openhands browser attr 'testid=chat-input' contenteditable is false, so browser fill fails) and control-openhands browser enabled 'testid=submit-button' is false. control-openhands browser click 'testid=home-llm-not-configured-action' then browser url ends in /settings/llm.

Toggle the hidden switch through its label on /settings/verification: control-openhands browser goto /settings/verification, control-openhands browser click 'label:has([data-testid="sdk-settings-verification.critic_enabled"])', save, api GET /api/settings shows "critic_enabled": true. Without a Critic API key a Reply with only the word OK. conversation renders no critic block. With a key and a model, run control-openhands conversation start --prompt "Create qa_critic.txt containing hi, then finish." --wait --timeout 180: every scored event carries a block, so control-openhands browser count 'text=Critic: agent success likelihood' is at least 1 and a finishing action (finish tool row) shows its own block next to the agent's message; the stars carry the score as their label, which an ARIA snapshot does not list: control-openhands browser count '[aria-label^="Score: "]' is at least 2 and control-openhands browser attr '[aria-label^="Score: "] >> nth=0' aria-label reads Score: <N.N>% with one decimal (Score: 82.0%), the same number as the (82.0%) text beside the stars. control-openhands browser click 'role=button[name="Expand details"] >> nth=0' opens the categories Potential Issues:, Infrastructure: and Likely Follow-up: with their named issues in control-openhands browser text 'testid=chat-scroll-container', and the button's label flips to Collapse details. Blocked here: DEEPSEEK_API_KEY and a Cloud critic key. Turn it off again the same way.

Run control-openhands browser viewport phone, open the table conversation (control-openhands browser goto /conversations/<stream id>), control-openhands browser bbox 'testid=chat-interface' (insideViewport true, pageHorizontalOverflow false) and control-openhands browser bbox 'testid=markdown-table-scroll' (scrollWidth larger than clientWidth: the table scrolls inside itself). control-openhands browser screenshot --feature F06.phone --name conversation, then control-openhands browser viewport desktop.

After each group run control-openhands browser errors --app-only. Outages driven with service stop log connection-refused console errors by design; pageErrors must stay 0.

Expected: reloading a parent still discovers its plannerparent-tagged planner when it has100 child conversations. Known failure (reproduced 2026-10-16, SDK 1.55.0, OpenHands/software-agent-sdk#5790): the unchunked100-ID request returns500, shows Internal Server Error and omits the planner session connection. A99-child control returns200 and opens both planner and parent sockets. These are genuine idle API-created children, without a model run or browser-storage changes; a new parent ID has no UI-created planner hint.

sh known-bug F06.tool-visualizers planner-batch-100

  control-openhands browser viewport desktop
  QA_ID="$(python3 - <<'PY'
  import json, os, pathlib, subprocess, tempfile
  base = pathlib.Path(os.environ["OH_VERIFY_RUN"]) / "workspace"
  base.mkdir(exist_ok=True)
  fixture = pathlib.Path(tempfile.mkdtemp(prefix="qa-surface-", dir=base))
  llm = {"model":"openai/gpt-4o", "base_url":"http://127.0.0.1:1/v1", "api_key":"qa-not-real", "num_retries":0, "timeout":2}
  def create(workspace, parent=None, tags=None):
      payload = {"agent":{"kind":"Agent", "llm":llm, "tools":[]}, "workspace":{"working_dir":str(workspace)}, "autotitle":False}
      if parent: payload["parent_conversation_id"] = parent
      if tags: payload["tags"] = tags
      request = fixture / "request.json"
      request.write_text(json.dumps(payload))
      result = subprocess.run(["control-openhands", "api", "POST", "/api/conversations", "--write", "--data", "@"+str(request), "--pick", "id"], check=True, capture_output=True, text=True)
      return json.loads(result.stdout)["value"]
  def git(directory, *args):
      subprocess.run(["git", "-C", str(directory), *args], check=True, capture_output=True)
  workspace = fixture / "workspace"
  workspace.mkdir()
  parent = create(workspace)
  for index in range(100):
      create(workspace, parent, {"plannerparent":parent} if index == 0 else None)
  print(parent)
  PY
  )"
  control-openhands assert --field value --equals 100 -- api GET "/api/conversations/$QA_ID" --pick sub_conversation_ids.length
  QA_PLANNER="$(control-openhands api GET "/api/conversations/$QA_ID" --pick sub_conversation_ids.0 | python3 -c 'import json,sys; print(json.load(sys.stdin)["value"])')"
  control-openhands browser network --clear
  control-openhands browser goto "/conversations/$QA_ID"
  control-openhands browser wait 'testid=chat-input'
  control-openhands browser screenshot --feature F06.tool-visualizers --name planner-batch-100
  control-openhands assert --field recent.0.status --equals 200 --bug-shows 500 -- browser network --filter "ids=$QA_PLANNER"  # bug