Composer, slash commands and plan mode

Gotchas and known limits

• Always export your own OH_VERIFY_RUN. launch --new repoints the shared current symlink, and another agent relying on current drove and then stopped this family's stack mid-run. If the URL jumps to a page you never opened or fetch failed appears, run control-openhands status before blaming the product.
• conversation wait <id> right after sending returns at once with the previous finished status. Use conversation wait <id> --fresh; --until running then a terminal wait only works for turns longer than the poll interval (a Reply with only turn on deepseek-flash can finish first, and --until running then times out).
• The slash menu stays open while you type a command; press Escape before Enter or Enter selects the highlighted option instead of sending.
• Conversation drafts are saved 500 ms after the last keystroke and not flushed on unmount (the home draft is): navigating sooner restores the older draft (fail row) (#17926). Wait a second before navigating when testing restoration.
• Escape closes the + tools menu (browser count 'testid=tools-context-menu' is 0) and returns focus to chat-plus-button, whether focus was on the trigger or on a menu item. A menu left open covers attachments in screenshots. Escape should also close the narrow-width "More input actions" overflow menu and return focus to its trigger. Known failure (reproduced 2026-10-08): browser count 'testid=chat-input-overflow-menu' stays 1 and the trigger's aria-expanded stays true, with focus on the trigger or on a menu item (#18172): close it with its trigger or an outside click (browser mouse-click 160 100 at narrow).
• After a client-side switch between conversations (a sidebar row, or a user-message branch in F06.branch-from-here) Send keeps the previous conversation's state (repro candidate, not filed yet). Switching from an empty composer to one with a saved draft restores the text next to a disabled Send; this is a race (Send came up enabled in 1 of 7 tries), so one enabled reading does not show the bug is gone. Switching from a composer with text to an empty one leaves Send enabled, and clicking it does nothing. Typing or browser reload fixes it, and Enter in the field sends the restored text anyway. Read browser enabled 'testid=submit-button' after a reload, or after typing.
• Uploaded chips and thumbnails have no test ids. Their remove buttons are named Remove <file name> (file chip) and Remove image (thumbnail), and Send, Stop and Play read Send message, Stop and Resume the agent task (#18033); select by those names, or by text/alt.
• browser upload feeds the hidden input directly. To drive the real path, + > Add Files and Images, use control-openhands browser upload-via 'testid=add-files-and-images-button' <file>, which answers the native file chooser.
• The home composer has no interactive-chat-box wrapper: scope its chips and thumbnails with testid=home-chat-launcher.
• conversation events rows show a message's text and its attachment count (images: 1 for the image-only message, whose text is a blank); --grep 'data:image/png;base64' searches whole events and quotes the image content block in excerpts.
• A user row with images: 1 proves that the image reached the Agent Server, not the model. Only the reply proves that the model saw it. On agent-server 1.53.0 and older, deepseek/* profiles drop the image before the LLM call (F05.image-only-send). An image sent with no text then leaves deepseek-flash with an empty task. On 2026-10-08 it ran env, read the run directory and other files on the host, and decoded the picture from the event store with PIL to answer. Pause such a conversation (control-openhands conversation pause <id>), and use the question-plus-image send for the model check.
• The pill resolves the conversation's stamped profile before the user-level default, so profiles that share a model are told apart by name. The stamp lives in this browser's localStorage (openhands-agent-server-conversation-metadata), not on the server (api GET /api/conversations/<id> has no profile name): read it with browser eval, not api GET.
• The Switched to profile notes are client-side and gone after reload; assert the pill and conversation status.
• /plan messages go to a separate planner conversation; the browser stays on the parent /conversations/<id>, so wait on the planner id from conversation list.
• Only the newest goal status offers Resume (#18036): once a resumed goal has posted a newer status, the old interrupted row shows no button, also after a reload. Count testid=goal-resume after the resumed goal ends; while it runs the count is 0 anyway.
• Opening the context popover logs a 404 for /api/llm/balance on the local backend in browser errors --app-only; it does not break the popover.
• --observe takes the verbs' selector syntax: testid= and plain CSS segments are watched by an in-page MutationObserver (observedBy mutation), while role=, text= and other engines are polled every 20 ms (poll-20ms), which misses a state shorter than that; prefer a testid= or CSS form for anything brief.
• At narrow (320 px) the overflow menu's Model submenu opens to the right of the menu and runs off screen: each profile row starts at x about 270 with width 210 (browser bbox 'testid=chat-input-llm-profile-option-deepseek-flash', insideViewport false), so both names read deepse…. Pick profiles by test id: the click lands on the strip of about 50 px that stays on screen. Known issue: #18063 (filed from the follow-up noted in #18015; the submenu also runs past the bottom edge, so the LLM Profiles link cannot be clicked at narrow) (F05.overflow-menu).