# Open in chat Runs and pipelines expose **Open in chat** in their overflow menus. The action creates a chat using the New chat backend catalog rule (OpenCode when available, otherwise the first advertised harness) in the run/latest-run workspace, or the saved Settings workspace and finally `~`, then routes to the Chat tab. The generated reference is seeded as an unsent composer draft and requests composer focus. Settings and create failures show an error without changing chat state. On narrow pipeline detail layouts, the segmented More sheet includes both Archive/Unarchive and Open in chat. Settings fallback reads the workspace for the active server identity rather than an unscoped preference. Focused regression coverage is in `test/application/open_in_chat_test.dart`: run list desktop menu, run detail phone sheet, pipeline list row menu, and pipeline detail phone overflow all assert selection reaches the callback with the expected entity and latest run. The existing schedule/menu and pipeline destination tests also pass. The full-app browser probe now supports stateful `chat_create`, catalog, session, and transcript replies, so a rendered menu selection can show the created chat and seeded composer rather than stopping at an unsupported-request error. Browser and phone/desktop captures were not run in this implementation stage.