Add a "Copy Error Detals" button for pasting into an LLM

[paul]

There's several copy buttons all over for the error type, message, backtrace, etc. I was looking for a button to copy the all the relevant error details as markdown, so that I could paste it into an LLM session and have it investigate. I can download the JSON and paste that, and it works, but its noisy.

Something like:

# Argument Error

undefined method foo for nil

## Backtrace

... first 10 lines of the application backtrace ...

## Related errors 

- undefined method x for nil
- ...

[AnjanJ]

Hey @paul — love this idea! Just shipped it in commit 40faac9.

There's now a "Copy for LLM" button right next to "Export JSON" on every error detail page. It copies clean, structured markdown optimized for pasting into an LLM session.

The output includes (conditionally — only sections with data):

• Error type + message
• App backtrace (framework frames filtered out)
• Exception cause chain
• Local variables + instance variables (if captured)
• Request context (method, URL, hostname, duration, IP)
• Breadcrumbs (last 10 activity trail entries)
• Environment (Ruby, Rails, server, DB adapter, app version, git SHA)
• System health at error time (memory, threads, DB pool, GC)
• Related errors with similarity %
• Metadata (severity, status, priority, occurrences, assignment)

All sensitive data stays filtered ([FILTERED]), and values are truncated to keep the context window efficient.

Will be in the next gem release. Thanks for the suggestion!

[paul]

Sweet! Thanks for the quick response. I'll give it a shot today

[AnjanJ]

v0.5.7 is now on RubyGems with a much improved "Copy for LLM" output. The big addition: source code snippets — it now reads the actual Ruby code (±3 lines) around each crash location, so the LLM can see what the code does, not just file:line references.

Also added: request params (pretty JSON), full system health snapshot, controller#action context. Removed noise that doesn't help LLMs debug (process-wide stats, workflow fields).

Would love to hear how it works for your workflow — thanks again for the idea!

[paul]

Just gave it a shot, pretty great! One nitpick, it looks like backticks and quotes are escaped in the output. The LLMs don't care one bit, though.

[AnjanJ]

Thanks for catching that @paul! Those escaped backticks were bugging me too once you pointed them out.

Fixed in commit 8cbe0bf — the j helper was escaping backticks, quotes, and single quotes for HTML attribute safety, but I was only unescaping \n in JavaScript. Now using a universal unescape that handles all escape sequences in one pass.

Also took the opportunity to strip [FILTERED] variables from the output entirely — redacted values don't help the LLM debug anything.

Both will be in the next release. Thanks for sharing details like this — it's exactly the kind of feedback that makes the gem better for everyone.