René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add a \"Copy\" (copy-as-Markdown) action to assistant/agent responses","articleBody":"## Problem or Motivation\n\nOpenWork already lets you copy **user** messages (hover → copy) and **code blocks** (each `CodeBlock` has a copy button), but a full **assistant/agent response** cannot be copied. The only hover action on an assistant bubble is \"open in new window\" (pop-out). To grab a response today you have to manually select the rendered text, which loses the Markdown and is awkward for long, multi-block answers.\n\nEvery comparable AI desktop surface offers a per-message copy:\n- **Codex desktop** — \"Copy as Markdown\" is one of its most-requested features (openai/codex [#2880](https://github.com/openai/codex/issues/2880), [#17241](https://github.com/openai/codex/issues/17241)).\n- **Claude desktop / ChatGPT desktop** — every assistant message has a copy button.\n\nThis is a clear, frontend-only parity gap.\n\n## Proposed Solution\n\nAdd a **Copy** button to the assistant message bubble's hover actions (next to the existing pop-out control) that copies the response's raw Markdown (`message.content`) to the clipboard.\n\n- Renderer-only: `navigator.clipboard.writeText(message.content)`, a 2-second \"copied\" check state, and a `toast.copyFailed` on error — mirroring the existing user-message copy and `CodeBlock` copy patterns.\n- Extract an `AssistantMessage` component in `ChatDisplay.tsx` so it can own the `copied` state (the same reason `ErrorMessage` was already extracted — a hook can't live in `MessageBubble`'s role switch).\n- Only shown on a settled (non-streaming) response.\n- **Zero new i18n keys** — reuses `common.copy`, `common.copied`, `toast.copyFailed`.\n\n**Feasibility: frontend-only.** No qwen-code backend change — it reads text already in the rendered message and calls the Web Clipboard API.\n\n## Alternatives Considered\n\n- A \"Copy as Markdown\" entry in a per-message context menu — heavier and less discoverable than a hover button; OpenWork's assistant bubble already has an inline hover-action slot (pop-out), so a sibling button fits the existing pattern.\n- Copying the *entire* conversation — larger surface; per-message copy is the atomic, most-requested unit and can be composed later.\n\n## Additional Context\n\n**Acceptance / CDP assertion (`e2e/assertions/copy-message.assert.ts`):** seed a user+assistant session on disk (via a new backend-independent `seed` hook on the e2e harness — the embedded `SessionManager` loads it on boot), open it, and drive the copy button. Assert that clicking it (a) writes the **exact** response Markdown to the clipboard and (b) flips the button into its `data-copied=\"true\"` state — proving it copies the right content and is a real wired action, not just an icon.\n\nPart of the autonomous desktop-feature loop (`loop-bot`).","author":{"url":"https://github.com/DragonnZhang","@type":"Person","name":"DragonnZhang"},"datePublished":"2026-07-08T13:43:50.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/70/openwork/issues/70"}