feat(web): copy the full error report from the error page

[StiensWout]

When the app hits the root error page, the stack trace is hidden behind a collapsed "Show error details" toggle and there is no way to copy it. Users reporting a crash have to select text out of a scrolling pre by hand, and lose the app version and page they were on.

The error page now shows an always-open error report and a Copy error button next to Try again and Reload app. The report contains the app name and version, the page path, an ISO timestamp, the stack, and up to five levels of the cause chain. The path excludes the query string so pairing tokens never reach the clipboard. Copying uses the existing clipboard hook and flips the button to a check mark for two seconds.

Before

After

Made with Claude Fable 5.1 in T3 Code.

🤖 Generated with Claude Code

---

Note

Low Risk
UI-only changes on the error boundary and clipboard copy of client-side error text; no auth, persistence, or core routing logic changes.

Overview
The root router error page now surfaces a always-visible error report instead of a collapsed “Show error details” section, so users can see context without expanding a <details> block.

A Copy error action (via useCopyToClipboard) copies a formatted report that includes app name/version, router pathname (not the query string, to avoid leaking tokens), ISO timestamp, stack/details, and up to five Error.cause levels. Pathname comes from TanStack Router so desktop hash history still records the real route. The copy button shows brief “Copied” / check feedback.

The report panel uses wrapping and a slightly taller scroll area than the old hidden pre block.

^{Reviewed by Cursor Bugbot for commit 9ff7bf8. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add copy-to-clipboard button for full error report on error page

Replaces the expandable error-details disclosure in RootRouteErrorView with an always-visible error report panel and a new CopyErrorButton that copies the report and shows a copied confirmation state.

• The errorReport formatter assembles app name and version, router pathname, ISO timestamp, error details, and up to five nested Error cause entries into a newline-separated string.
• The pathname is taken from router state rather than window.location, so query-string content is excluded from the report.
• Behavioral Change: error details are now always visible instead of behind a disclosure toggle.

📊 Macroscope summarized 9ff7bf8. 1 file reviewed, 2 issues evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 77a5bb4. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This production-facing PR adds a new error-report copying capability and changes the root error page from collapsible details to an always-visible report, including nested causes and runtime metadata. The implementation is localized and does not touch backend, schema, auth, billing, or deployment code, but the new user-facing behavior lacks focused test coverage and merits human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[StiensWout]

When the app hits the root error page, the stack trace is hidden behind a collapsed "Show error details" toggle and there is no way to copy it. Users reporting a crash have to select text out of a scrolling pre by hand, and lose the app version and page they were on.

The error page now shows an always-open error report and a Copy error button next to Try again and Reload app. The report contains the app name and version, the page path, an ISO timestamp, the stack, and up to five levels of the cause chain. The path excludes the query string so pairing tokens never reach the clipboard. Copying uses the existing clipboard hook and flips the button to a check mark for two seconds.

Before

After

Made with Claude Fable 5.1 in T3 Code.

🤖 Generated with Claude Code

---

Note

Low Risk
UI-only changes on the error boundary and clipboard copy of client-side error text; no auth, persistence, or core routing logic changes.

Overview
The root router error page now surfaces a always-visible error report instead of a collapsed “Show error details” section, so users can see context without expanding a <details> block.

A Copy error action (via useCopyToClipboard) copies a formatted report that includes app name/version, router pathname (not the query string, to avoid leaking tokens), ISO timestamp, stack/details, and up to five Error.cause levels. Pathname comes from TanStack Router so desktop hash history still records the real route. The copy button shows brief “Copied” / check feedback.

The report panel uses wrapping and a slightly taller scroll area than the old hidden pre block.

^{Reviewed by Cursor Bugbot for commit 9ff7bf8. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add copy-to-clipboard button for full error report on error page

Replaces the expandable error-details disclosure in RootRouteErrorView with an always-visible error report panel and a new CopyErrorButton that copies the report and shows a copied confirmation state.

• The errorReport formatter assembles app name and version, router pathname, ISO timestamp, error details, and up to five nested Error cause entries into a newline-separated string.
• The pathname is taken from router state rather than window.location, so query-string content is excluded from the report.
• Behavioral Change: error details are now always visible instead of behind a disclosure toggle.

📊 Macroscope summarized 9ff7bf8. 1 file reviewed, 2 issues evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 77a5bb4. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This production-facing PR adds a new error-report copying capability and changes the root error page from collapsible details to an always-visible report, including nested causes and runtime metadata. The implementation is localized and does not touch backend, schema, auth, billing, or deployment code, but the new user-facing behavior lacks focused test coverage and merits human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[StiensWout]

When the app hits the root error page, the stack trace is hidden behind a collapsed "Show error details" toggle and there is no way to copy it. Users reporting a crash have to select text out of a scrolling pre by hand, and lose the app version and page they were on.

The error page now shows an always-open error report and a Copy error button next to Try again and Reload app. The report contains the app name and version, the page path, an ISO timestamp, the stack, and up to five levels of the cause chain. The path excludes the query string so pairing tokens never reach the clipboard. Copying uses the existing clipboard hook and flips the button to a check mark for two seconds.

Before

After

Made with Claude Fable 5.1 in T3 Code.

🤖 Generated with Claude Code

---

Note

Low Risk
UI-only changes on the error boundary and clipboard copy of client-side error text; no auth, persistence, or core routing logic changes.

Overview
The root router error page now surfaces a always-visible error report instead of a collapsed “Show error details” section, so users can see context without expanding a <details> block.

A Copy error action (via useCopyToClipboard) copies a formatted report that includes app name/version, router pathname (not the query string, to avoid leaking tokens), ISO timestamp, stack/details, and up to five Error.cause levels. Pathname comes from TanStack Router so desktop hash history still records the real route. The copy button shows brief “Copied” / check feedback.

The report panel uses wrapping and a slightly taller scroll area than the old hidden pre block.

^{Reviewed by Cursor Bugbot for commit 9ff7bf8. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add copy-to-clipboard button for full error report on error page

Replaces the expandable error-details disclosure in RootRouteErrorView with an always-visible error report panel and a new CopyErrorButton that copies the report and shows a copied confirmation state.

• The errorReport formatter assembles app name and version, router pathname, ISO timestamp, error details, and up to five nested Error cause entries into a newline-separated string.
• The pathname is taken from router state rather than window.location, so query-string content is excluded from the report.
• Behavioral Change: error details are now always visible instead of behind a disclosure toggle.

📊 Macroscope summarized 9ff7bf8. 1 file reviewed, 2 issues evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 77a5bb4. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This production-facing PR adds a new error-report copying capability and changes the root error page from collapsible details to an always-visible report, including nested causes and runtime metadata. The implementation is localized and does not touch backend, schema, auth, billing, or deployment code, but the new user-facing behavior lacks focused test coverage and merits human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[StiensWout]

When the app hits the root error page, the stack trace is hidden behind a collapsed "Show error details" toggle and there is no way to copy it. Users reporting a crash have to select text out of a scrolling pre by hand, and lose the app version and page they were on.

The error page now shows an always-open error report and a Copy error button next to Try again and Reload app. The report contains the app name and version, the page path, an ISO timestamp, the stack, and up to five levels of the cause chain. The path excludes the query string so pairing tokens never reach the clipboard. Copying uses the existing clipboard hook and flips the button to a check mark for two seconds.

Before

After

Made with Claude Fable 5.1 in T3 Code.

🤖 Generated with Claude Code

---

Note

Low Risk
UI-only changes on the error boundary and clipboard copy of client-side error text; no auth, persistence, or core routing logic changes.

Overview
The root router error page now surfaces a always-visible error report instead of a collapsed “Show error details” section, so users can see context without expanding a <details> block.

A Copy error action (via useCopyToClipboard) copies a formatted report that includes app name/version, router pathname (not the query string, to avoid leaking tokens), ISO timestamp, stack/details, and up to five Error.cause levels. Pathname comes from TanStack Router so desktop hash history still records the real route. The copy button shows brief “Copied” / check feedback.

The report panel uses wrapping and a slightly taller scroll area than the old hidden pre block.

^{Reviewed by Cursor Bugbot for commit 9ff7bf8. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add copy-to-clipboard button for full error report on error page

Replaces the expandable error-details disclosure in RootRouteErrorView with an always-visible error report panel and a new CopyErrorButton that copies the report and shows a copied confirmation state.

• The errorReport formatter assembles app name and version, router pathname, ISO timestamp, error details, and up to five nested Error cause entries into a newline-separated string.
• The pathname is taken from router state rather than window.location, so query-string content is excluded from the report.
• Behavioral Change: error details are now always visible instead of behind a disclosure toggle.

📊 Macroscope summarized 9ff7bf8. 1 file reviewed, 2 issues evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 77a5bb4. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This production-facing PR adds a new error-report copying capability and changes the root error page from collapsible details to an always-visible report, including nested causes and runtime metadata. The implementation is localized and does not touch backend, schema, auth, billing, or deployment code, but the new user-facing behavior lacks focused test coverage and merits human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[StiensWout]

When the app hits the root error page, the stack trace is hidden behind a collapsed "Show error details" toggle and there is no way to copy it. Users reporting a crash have to select text out of a scrolling pre by hand, and lose the app version and page they were on.

The error page now shows an always-open error report and a Copy error button next to Try again and Reload app. The report contains the app name and version, the page path, an ISO timestamp, the stack, and up to five levels of the cause chain. The path excludes the query string so pairing tokens never reach the clipboard. Copying uses the existing clipboard hook and flips the button to a check mark for two seconds.

Before

After

Made with Claude Fable 5.1 in T3 Code.

🤖 Generated with Claude Code

---

Note

Low Risk
UI-only changes on the error boundary and clipboard copy of client-side error text; no auth, persistence, or core routing logic changes.

Overview
The root router error page now surfaces a always-visible error report instead of a collapsed “Show error details” section, so users can see context without expanding a <details> block.

A Copy error action (via useCopyToClipboard) copies a formatted report that includes app name/version, router pathname (not the query string, to avoid leaking tokens), ISO timestamp, stack/details, and up to five Error.cause levels. Pathname comes from TanStack Router so desktop hash history still records the real route. The copy button shows brief “Copied” / check feedback.

The report panel uses wrapping and a slightly taller scroll area than the old hidden pre block.

^{Reviewed by Cursor Bugbot for commit 9ff7bf8. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add copy-to-clipboard button for full error report on error page

Replaces the expandable error-details disclosure in RootRouteErrorView with an always-visible error report panel and a new CopyErrorButton that copies the report and shows a copied confirmation state.

• The errorReport formatter assembles app name and version, router pathname, ISO timestamp, error details, and up to five nested Error cause entries into a newline-separated string.
• The pathname is taken from router state rather than window.location, so query-string content is excluded from the report.
• Behavioral Change: error details are now always visible instead of behind a disclosure toggle.

📊 Macroscope summarized 9ff7bf8. 1 file reviewed, 2 issues evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 77a5bb4. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This production-facing PR adds a new error-report copying capability and changes the root error page from collapsible details to an always-visible report, including nested causes and runtime metadata. The implementation is localized and does not touch backend, schema, auth, billing, or deployment code, but the new user-facing behavior lacks focused test coverage and merits human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[StiensWout]

When the app hits the root error page, the stack trace is hidden behind a collapsed "Show error details" toggle and there is no way to copy it. Users reporting a crash have to select text out of a scrolling pre by hand, and lose the app version and page they were on.

The error page now shows an always-open error report and a Copy error button next to Try again and Reload app. The report contains the app name and version, the page path, an ISO timestamp, the stack, and up to five levels of the cause chain. The path excludes the query string so pairing tokens never reach the clipboard. Copying uses the existing clipboard hook and flips the button to a check mark for two seconds.

Before

After

Made with Claude Fable 5.1 in T3 Code.

🤖 Generated with Claude Code

---

Note

Low Risk
UI-only changes on the error boundary and clipboard copy of client-side error text; no auth, persistence, or core routing logic changes.

Overview
The root router error page now surfaces a always-visible error report instead of a collapsed “Show error details” section, so users can see context without expanding a <details> block.

A Copy error action (via useCopyToClipboard) copies a formatted report that includes app name/version, router pathname (not the query string, to avoid leaking tokens), ISO timestamp, stack/details, and up to five Error.cause levels. Pathname comes from TanStack Router so desktop hash history still records the real route. The copy button shows brief “Copied” / check feedback.

The report panel uses wrapping and a slightly taller scroll area than the old hidden pre block.

^{Reviewed by Cursor Bugbot for commit 9ff7bf8. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add copy-to-clipboard button for full error report on error page

Replaces the expandable error-details disclosure in RootRouteErrorView with an always-visible error report panel and a new CopyErrorButton that copies the report and shows a copied confirmation state.

• The errorReport formatter assembles app name and version, router pathname, ISO timestamp, error details, and up to five nested Error cause entries into a newline-separated string.
• The pathname is taken from router state rather than window.location, so query-string content is excluded from the report.
• Behavioral Change: error details are now always visible instead of behind a disclosure toggle.

📊 Macroscope summarized 9ff7bf8. 1 file reviewed, 2 issues evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 77a5bb4. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This production-facing PR adds a new error-report copying capability and changes the root error page from collapsible details to an always-visible report, including nested causes and runtime metadata. The implementation is localized and does not touch backend, schema, auth, billing, or deployment code, but the new user-facing behavior lacks focused test coverage and merits human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[StiensWout]

When the app hits the root error page, the stack trace is hidden behind a collapsed "Show error details" toggle and there is no way to copy it. Users reporting a crash have to select text out of a scrolling pre by hand, and lose the app version and page they were on.

The error page now shows an always-open error report and a Copy error button next to Try again and Reload app. The report contains the app name and version, the page path, an ISO timestamp, the stack, and up to five levels of the cause chain. The path excludes the query string so pairing tokens never reach the clipboard. Copying uses the existing clipboard hook and flips the button to a check mark for two seconds.

Before

After

Made with Claude Fable 5.1 in T3 Code.

🤖 Generated with Claude Code

---

Note

Low Risk
UI-only changes on the error boundary and clipboard copy of client-side error text; no auth, persistence, or core routing logic changes.

Overview
The root router error page now surfaces a always-visible error report instead of a collapsed “Show error details” section, so users can see context without expanding a <details> block.

A Copy error action (via useCopyToClipboard) copies a formatted report that includes app name/version, router pathname (not the query string, to avoid leaking tokens), ISO timestamp, stack/details, and up to five Error.cause levels. Pathname comes from TanStack Router so desktop hash history still records the real route. The copy button shows brief “Copied” / check feedback.

The report panel uses wrapping and a slightly taller scroll area than the old hidden pre block.

^{Reviewed by Cursor Bugbot for commit 9ff7bf8. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add copy-to-clipboard button for full error report on error page

Replaces the expandable error-details disclosure in RootRouteErrorView with an always-visible error report panel and a new CopyErrorButton that copies the report and shows a copied confirmation state.

• The errorReport formatter assembles app name and version, router pathname, ISO timestamp, error details, and up to five nested Error cause entries into a newline-separated string.
• The pathname is taken from router state rather than window.location, so query-string content is excluded from the report.
• Behavioral Change: error details are now always visible instead of behind a disclosure toggle.

📊 Macroscope summarized 9ff7bf8. 1 file reviewed, 2 issues evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 77a5bb4. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This production-facing PR adds a new error-report copying capability and changes the root error page from collapsible details to an always-visible report, including nested causes and runtime metadata. The implementation is localized and does not touch backend, schema, auth, billing, or deployment code, but the new user-facing behavior lacks focused test coverage and merits human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[StiensWout]

When the app hits the root error page, the stack trace is hidden behind a collapsed "Show error details" toggle and there is no way to copy it. Users reporting a crash have to select text out of a scrolling pre by hand, and lose the app version and page they were on.

The error page now shows an always-open error report and a Copy error button next to Try again and Reload app. The report contains the app name and version, the page path, an ISO timestamp, the stack, and up to five levels of the cause chain. The path excludes the query string so pairing tokens never reach the clipboard. Copying uses the existing clipboard hook and flips the button to a check mark for two seconds.

Before

After

Made with Claude Fable 5.1 in T3 Code.

🤖 Generated with Claude Code

---

Note

Low Risk
UI-only changes on the error boundary and clipboard copy of client-side error text; no auth, persistence, or core routing logic changes.

Overview
The root router error page now surfaces a always-visible error report instead of a collapsed “Show error details” section, so users can see context without expanding a <details> block.

A Copy error action (via useCopyToClipboard) copies a formatted report that includes app name/version, router pathname (not the query string, to avoid leaking tokens), ISO timestamp, stack/details, and up to five Error.cause levels. Pathname comes from TanStack Router so desktop hash history still records the real route. The copy button shows brief “Copied” / check feedback.

The report panel uses wrapping and a slightly taller scroll area than the old hidden pre block.

^{Reviewed by Cursor Bugbot for commit 9ff7bf8. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add copy-to-clipboard button for full error report on error page

Replaces the expandable error-details disclosure in RootRouteErrorView with an always-visible error report panel and a new CopyErrorButton that copies the report and shows a copied confirmation state.

• The errorReport formatter assembles app name and version, router pathname, ISO timestamp, error details, and up to five nested Error cause entries into a newline-separated string.
• The pathname is taken from router state rather than window.location, so query-string content is excluded from the report.
• Behavioral Change: error details are now always visible instead of behind a disclosure toggle.

📊 Macroscope summarized 9ff7bf8. 1 file reviewed, 2 issues evaluated, 0 issues filtered, 1 comment posted

🗂️ Filtered Issues

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 77a5bb4. Configure here.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This production-facing PR adds a new error-report copying capability and changes the root error page from collapsible details to an always-visible report, including nested causes and runtime metadata. The implementation is localized and does not touch backend, schema, auth, billing, or deployment code, but the new user-facing behavior lacks focused test coverage and merits human review.

^{You can add or adjust custom eligibility rules. Learn more.}