Select #26

I am a big fan of copy paste. I keep copy pasting Zig output to share with an AI (when AI coding, even though I usually don't) or a better Zig dev, or to grep to find the definition:
/tmp/errtest.zig:5:9: error: Error at compile time: error.NotTrue
@CompileError(std.fmt.comptimePrint("Error at compile time: {}", .{err}));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/errtest.zig:19:36: note: called at comptime here
const MyType = errable_comptime(test_fn, .{false});
~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~
I know that I made that Zig program intentionally fail, but I could copy paste the function name "errable_comptime" into grep and see why it failed, like if I was a debugger, and see that it intentionally returns the error.
I also love copy/paste because if a Zig app has a binary serialization format, I could copy the garbage code out of the app and into a decoder so I know what it means. I know that stdin/stdout works, but if not in the terminal, you GOTTA use copy/paste.
However, I then try to copy paste out of a Zigtools Playground. I do not see a copy button, nor does it let me select the output.
Now, I cloned the old version of the Playground and ran it locally, and copy paste worked perfectly. I think that the playground should keep the old terminal available until this bug gets solved.
Personally, I am more of a Zig dev than a JS dev, and I don't really know how xterm-js works. I don't know if there will have to be a Zigtools fork of xterm-js or something, or if it will just be a change in the playground.