feat(frontend): Unmask static content for Sentry replays

[Copilot]

Plan to unmask all statically named content in the platform frontend for Sentry replays:

• Unmask error boundary components (3 files)
  • global-error.tsx - error messages and headings (uses ErrorCard)
  • error.tsx - error headings and button labels
  • (platform)/error.tsx - error context and messages (uses ErrorCard)
  • ErrorCard component and subcomponents (ErrorHeader, ErrorMessage, ActionButtons)
• Unmask marketplace components - Phase 1 (12 files completed)
  • Hero section - headings and descriptions
  • Featured section - section titles
  • Agent cards - static labels like "runs", "by"
  • Agent info - labels like "Description", "Categories", "Version history", button text
  • Creator cards and info - labels like "agents", "Top categories", "Average rating"
  • Search results page - headings like "Results for:", "No results found"
  • BecomeACreator section - titles and descriptions
  • AgentsSection - section titles and "No agents found"
  • StoreCard - static labels like "runs", "by"
• Unmask remaining marketplace components - Phase 2
  • Admin marketplace components
  • Other marketplace pages and components
• Test the changes
  • Run linter to ensure code quality
  • Build the frontend to ensure no errors
  • Verify changes don't break existing functionality

Original prompt

I want you to go through and unmask all the statically named content in the platform frontend so that it's reported in sentry replays. Anything in the marketplace is fair game so let's start there. Also on error boundaries since that's where sentry helps most

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev ready!

Name	Link
🔨 Latest commit	9251424
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs-dev/deploys/68f9241aee66190008c390e6
😎 Deploy Preview	https://deploy-preview-11219--auto-gpt-docs-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for auto-gpt-docs ready!

Name	Link
🔨 Latest commit	9251424
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs/deploys/68f9241a0e5b210009395fbd
😎 Deploy Preview	https://deploy-preview-11219--auto-gpt-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[deepsource-io]

Here's the code health analysis summary for commits e2a9923..9251424. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success	❗ 2 occurences introduced 🎯 2 occurences resolved	View Check ↗
Python	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[AutoGPT-Agent]

Thank you for working on unmasking static content for Sentry replays. This is an important improvement for debugging and error tracking. However, before this PR can be merged, there are several requirements that need to be addressed:

Title Format

The PR title needs to follow the conventional commit format, starting with a type and optional scope. For example:

• fix(frontend): Unmask static content for sentry replays
• or feat(frontend): Unmask static content for sentry replays

PR Description

The PR description is currently incomplete. Please update it to include:

1. A clear explanation of why these changes are needed
2. A concise description of what changes you've made
3. The required checklist filled out completely

Specifically for this PR, please include:

• What problem this solves (e.g., "Improves error reporting by making static text content visible in Sentry replays")
• Which areas of the frontend you've modified
• Your test plan showing how you've verified these changes work correctly

Your actual code changes look good - they consistently add the sentry-unmask class to static text elements throughout the marketplace and error components. Once the PR metadata is updated according to the guidelines above, this should be ready for another review.

[AutoGPT-Agent]

Thank you for working on unmasking static content for Sentry replays. I see a few things that need to be addressed before this PR can be merged:

1. The PR title needs to follow our conventional commit format. Consider changing it to something like feat(frontend): Unmask static content for sentry replays

2. The PR is marked as WIP and none of the checklist items are checked, suggesting the work is incomplete. Please complete the tasks and check them off in the PR description.

3. The code changes look good - you're consistently adding the sentry-unmask class to static content elements as intended. Once you've completed all the planned changes, please update the checklist accordingly.

Please let me know if you need any clarification or assistance completing these tasks.

[AutoGPT-Agent]

Thank you for your work on unmasking static content for Sentry replays. Here are a few points to address before this PR can be merged:

1. PR Title Format: The title needs to follow our conventional commit format. Since this appears to be a feature improvement related to the frontend, consider something like feat(frontend): Unmask static content for sentry replays.

2. Incomplete Checklist: Please complete the remaining items in your checklist or update the PR description to reflect the current state if you're planning this as a partial implementation. Specifically:

   • The "Unmask remaining marketplace components - Phase 2" item is unchecked
   • Some testing items are still marked as incomplete

The code changes themselves look good - I see consistent application of the sentry-unmask class to static text elements throughout the codebase, which aligns well with the goal of improving Sentry replay visibility.

Once you've updated the title and addressed the checklist items (either by completing them or by updating the PR scope to indicate this is a partial implementation), this PR should be ready for another review.

[AutoGPT-Agent]

Thank you for working on unmasking static content for Sentry replays! This will improve error reporting and debugging capabilities. However, there are a few issues to address before this PR can be merged:

1. The PR title needs to follow the conventional commit format required by the project. It should be something like dx(frontend): Unmask static content for sentry replays. Please update the title to follow this format.

2. Your checklist isn't fully completed yet. You need to:

   • Build the frontend to ensure no errors
   • Verify changes don't break existing functionality

3. Since this is marked as WIP (Work in Progress), I assume you're still working on it. Once you've completed the remaining tasks, please remove the WIP tag from the title.

The actual code changes look good - consistently adding the sentry-unmask class to static text elements across the specified components. Once you address these issues, this PR should be ready for re-review.

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[ntindle]

@claude fix the conflicts taht are preventing updaing from base and also go through and see if there's any more we can unmask while not exposing any PII

[claude]

Claude finished @ntindle's task —— View job

---

✅ Completed your request

I've successfully addressed your request with the following changes:

Conflicts Resolution

• The branch histories had diverged significantly, making direct merge/rebase complex
• Verified that all our sentry-unmask changes from the original commits are preserved in the current branch

Additional Static Content Unmasked

I've added sentry-unmask class to additional static content across the platform:

Authentication Pages

• Login page: Button text ("Login"/"Logging in...")
• Signup page: Button text ("Sign up"/"Signing up...") and agreement text ("I agree to the", "and")

Library Pages

• EmptyAgentRuns component: Empty state messages ("You don't have any runs", "Get started with creating a run...", "New Run" button)

PII Safety Verification

All unmasked content consists only of:

• Static UI labels and button text
• System messages and instructions
• Empty state messages
• No user-generated content, emails, names, or other PII

Code Quality

• Fixed ESLint errors (unescaped quotes)
• Applied proper formatting to all modified files
• All changes pass linting checks

The changes have been committed and pushed to the branch. The sentry-unmask classes will make this static content visible in Sentry replays, improving debugging capabilities without exposing any personal information.

---

🔗

[AutoGPT-Agent]

Thanks for your detailed work on unmasking static content for Sentry replays! The changes look good technically, with consistent application of the sentry-unmask class to static text elements throughout the frontend components.

Before this can be merged, please update the PR title to follow our conventional commit format. For example:

feat(frontend): Unmask static content for Sentry replays

This would properly indicate that it's a new feature in the frontend scope. Once you complete the remaining tasks in your checklist (especially testing the changes), please remove the [WIP] tag.

Also, make sure to complete the remaining tasks you've outlined in your checklist:

• Unmasking remaining marketplace components (Phase 2)
• Completing the testing (building the frontend and verifying functionality)

Otherwise, the changes look good and align well with the stated purpose of improving Sentry replay reporting.

[github-actions]

Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Accessibility Button label "New Run" is now wrapped in a span; ensure the icon and text order/aria labeling remain accessible to screen readers and that the button still conveys its purpose when loading/disabled states change. <Button variant="primary" size="large" className="w-full"> <PlusIcon size={20} /> <span className="sentry-unmask">New Run</span> </Button> Link In Button Wrapping a Next.js Link inside a Button can cause nested interactive elements and focus/ARIA issues; consider making the Button itself the link or styling the Link as a button. <Button> <Link href="/" className="sentry-unmask"> Go to Homepage </Link> </Button> Dynamic Text Unmasking "runs" counters and other dynamic values are unmasked; verify this aligns with privacy policy for replays and does not unintentionally expose user-specific or sensitive runtime data. <div className="sentry-unmask whitespace-nowrap text-base font-semibold text-neutral-800 dark:text-neutral-200 sm:text-lg"> {runs.toLocaleString()} runs </div>