Experience · Frontend · Active

cs-tools chrome extension

Chrome Manifest V3 browser-local bridge that exports selected data from supported external tools into CS Tools frontend workflows without new backend APIs.

• Chrome MV3
• TypeScript
• esbuild
• Vitest

Spec sheet

Repository path

cs-tools/apps/chrome-extension

Runtime

Chrome Manifest V3

Build output

apps/chrome-extension/dist

Supported source

Anypoint Monitoring Logs

Target

Unipol Monitoring interpreter-flow-logs

Responsibilities

• Expose a manual popup export action for supported browser sources.
• Keep content scripts scoped to declared Anypoint and CS Tools hosts.
• Route extension messages through a small service worker.
• Forward validated import payloads to the CS Tools frontend through window.postMessage.
• Avoid backend persistence, CORS changes, MCP tools and status-service operations.

Interfaces and contract surface

• Content script on https://eu1.anypoint.mulesoft.com/monitoring/*
• Content script on http://tools.cs.lvh.me/* with runtime origin guard for :8080
• Shared bridge contract @tools/shared

Consumers

• Internal users via Chrome

Dependencies and external touchpoints

• cs tools web
• cs tools shared

Notes

• The first adapter only exports manually selected Anypoint log text; DOM extraction can be added behind the same bridge contract.

Source references

• cs-tools/apps/chrome-extension/package.json
• cs-tools/apps/chrome-extension/src/manifest.json
• cs-tools/apps/chrome-extension/src

Browser-local bridge

cs-tools/apps/chrome-extension e una Chrome Extension Manifest V3 caricabile in locale da apps/chrome-extension/dist. Il bridge ha scope funzionale limitato a https://eu1.anypoint.mulesoft.com/monitoring/* e http://tools.cs.lvh.me:8080/*, usa un popup manuale e inoltra al frontend solo payload validati dal contratto @tools/shared. Per compatibilita con i match pattern Chrome, il manifest dichiara http://tools.cs.lvh.me/* e il content script applica il vincolo sulla porta 8080 a runtime.