DocsBook a demo

Platform

Platform overviewArchitectureWorkflow orchestrationGitOps configurationGovernance and AAAAI and MCPKnowledge and contextRuntime and executionEvidence and monitoring

Use cases

All use casesProduction incidentRelease preparationHotfix to productionSecurity scan triage
Why NopsAIIntegrationsSecurity

Resources

All resourcesAI agent governanceMCP governanceMCP securitySelf-hosted platforms
PricingGitHub

Company

How a run worksAboutContactBook a demo

Browser console warnings

Telling injected browser-extension noise apart from real NopsAI UI errors.

TroubleshootingOperatorDeveloper

Key points

  • A stack pointing at contentscript.js and mentioning app-init-liveness or background-liveness is almost always injected extension code, not NopsAI.
  • ObjectMultiplex warnings come from wallet and similar extensions.
  • Reproduce in a clean browser profile with extensions disabled before filing a UI bug.
  • A genuine NopsAI error has a stack frame in a NopsAI source file.

Runbooks

Triage an unexplained browser console warning

Usually none. The risk is spending time on injected extension code instead of a real defect.

Symptoms
  • DevTools shows repeated warnings or errors while using the NopsAI UI.
  • The stack trace does not obviously name a NopsAI source file.
Initial checks
  • Expand the stack trace and read the top frame file name.
  • Check whether the frame is contentscript.js or another injected script.
  • Note whether the message mentions app-init-liveness, background-liveness, or ObjectMultiplex.
Diagnostics
  • Open the same page in a clean browser profile with all extensions disabled.
  • Reload with DevTools open and the console cleared.
  • Compare the console output between the two profiles.
Resolution
  • If the warning disappears in the clean profile, it is injected extension code. No NopsAI change is needed.
  • If it reproduces with a NopsAI source-file stack frame, capture the full stack, the route, and the reproduction steps.
  • File the UI defect with that evidence rather than the original extension-polluted trace.
Required access

Browser access to the NopsAI UI. No platform permission needed.

Escalation

Escalate to the UI owners with the clean-profile stack trace and route.

How it works

The backend serves GET /favicon.ico as an empty cacheable response specifically so missing-favicon requests do not produce bearer token errors in the console or audit logs. A favicon 404 is therefore not expected and is worth investigating.

Examples

Separate extension noise from product errorstext
DevTools > Console > filter box:
  -chrome-extension://  -moz-extension://  -safari-web-extension://

DevTools > Network: reproduce with "Disable cache" checked,
then confirm the failing request is same-origin with the NopsAI API
before reporting it as a product bug.
Result

Most console warnings on the operator UI come from injected extension content scripts. Filtering them first is what makes the remaining messages meaningful.

Implementation evidence

  • doc/browser-console-troubleshooting.md

    How to triage DevTools warnings from injected content scripts.