SurfSense/surfsense_browser_extension
API Test Bot 4be8c1b996 feat(chat): add command patterns for Epic 2, 3, 4 widgets
- Add new command patterns to COMMAND_PATTERNS:
  * SHOW_WHALE_ACTIVITY - Matches 'show whale activity/transactions'
  * TRADING_SUGGESTION - Matches 'suggest/recommend entry/exit for TOKEN'
  * SHOW_PORTFOLIO - Matches 'show my portfolio'
  * CAPTURE_CHART - Matches 'capture/screenshot chart'
  * GENERATE_THREAD - Matches 'generate/create thread'

- Update handleSendMessage to handle new commands:
  * Whale activity: Shows MOCK_WHALE_TRANSACTIONS with smart money insights
  * Trading suggestion: Shows MOCK_TRADING_SUGGESTION with risk/reward analysis
  * Portfolio: Shows MOCK_PORTFOLIO with P&L and best performer
  * Chart capture: Shows chart capture tool with auto-filled metadata
  * Thread generator: Shows thread generator with token info pre-filled

- Import mock data for new widgets:
  * MOCK_WHALE_TRANSACTIONS
  * MOCK_TRADING_SUGGESTION
  * MOCK_PORTFOLIO

- Update help message to include all Epic commands organized by category

Enables users to trigger Epic 2, 3, 4 widgets via natural language commands
2026-02-04 02:59:34 +07:00
..
assets feat: monorepo 2025-04-07 23:47:06 -07:00
background docs: update PRD with comprehensive extension features and UX integration strategy 2026-02-01 21:32:06 +07:00
lib Biome: Fixes for extenstion repo 2025-07-27 12:01:11 -07:00
routes chore: update links in documentation and metadata to use the correct domain 2025-12-09 01:27:13 -08:00
sidepanel feat(chat): add command patterns for Epic 2, 3, 4 widgets 2026-02-04 02:59:34 +07:00
utils Biome: Fixes for extenstion repo 2025-07-27 12:01:11 -07:00
.env.example feat: monorepo 2025-04-07 23:47:06 -07:00
.gitignore chore: updated .gitignore files and added forgotten .env.example to frontend. 2025-04-10 23:43:47 -07:00
biome.json Biome: Fixes for extenstion repo 2025-07-27 12:01:11 -07:00
content.ts docs: update PRD with comprehensive extension features and UX integration strategy 2026-02-01 21:32:06 +07:00
font.css Biome: Fixes for extenstion repo 2025-07-27 12:01:11 -07:00
package.json feat(crypto): add SurfSense 2.0 Crypto Co-Pilot UI components 2026-02-04 02:19:57 +07:00
pnpm-lock.yaml fix(extension): resolve sharp module error on Node.js 22 (fixes #413) 2025-11-27 14:04:57 +08:00
popup.tsx docs: update PRD with comprehensive extension features and UX integration strategy 2026-02-01 21:32:06 +07:00
postcss.config.js Biome: Fixes for extenstion repo 2025-07-27 12:01:11 -07:00
README.md feat: monorepo 2025-04-07 23:47:06 -07:00
sidepanel.tsx docs: update PRD with comprehensive extension features and UX integration strategy 2026-02-01 21:32:06 +07:00
tailwind.config.js Biome: Fixes for extenstion repo 2025-07-27 12:01:11 -07:00
tailwind.css Biome: Fixes for extenstion repo 2025-07-27 12:01:11 -07:00
tsconfig.json Biome: Fixes for extenstion repo 2025-07-27 12:01:11 -07:00

SurfSense Cross Browser Extension

Use this guide to build for your browser https://docs.plasmo.com/framework/workflows/build

This is a Plasmo extension project bootstrapped with plasmo init.

Getting Started

First, run the development server:

pnpm dev
# or
npm run dev

Open your browser and load the appropriate development build. For example, if you are developing for the chrome browser, using manifest v3, use: build/chrome-mv3-dev.

You can start editing the popup by modifying popup.tsx. It should auto-update as you make changes. To add an options page, simply add a options.tsx file to the root of the project, with a react component default exported. Likewise to add a content page, add a content.ts file to the root of the project, importing some module and do some logic, then reload the extension on your browser.

For further guidance, visit our Documentation

Making production build

Run the following:

pnpm build
# or
npm run build

This should create a production bundle for your extension, ready to be zipped and published to the stores.

Submit to the webstores

The easiest way to deploy your Plasmo extension is to use the built-in bpp GitHub action. Prior to using this action however, make sure to build your extension and upload the first version to the store to establish the basic credentials. Then, simply follow this setup instruction and you should be on your way for automated submission!