MicrosoftRewardsWebsite is a free, open-source browser extension for Chrome and Firefox, with a companion Flutter Android app, that runs a Microsoft Rewards member's daily Bing searches for them so the points can be collected without performing each search by hand.

What it is

MicrosoftRewardsWebsite is the repository behind the extension published as "Microsoft Automatic Rewards" on the Chrome Web Store and Firefox Add-ons, written in TypeScript under the MIT licence. The modern codebase is built with WXT and React, and a single source tree produces both the Chrome MV3 and the Firefox MV2 builds; the earlier hand-written chrome/ and firefox/ trees with committed compiled output have been removed from the default branch and preserved on a legacy branch. A background service worker (background.ts) handles daily scheduling and the search runner, content scripts (rewards.content.ts, bingResult.content.ts) run on rewards.bing.com and on Bing results pages, and the popup interface is built in React with hooks for storage and search progress.

The problem it addresses is the daily Microsoft Rewards search routine, which otherwise means opening Bing and running a fixed number of searches one at a time to collect points. The extension replaces that manual repetition: it opens ten random Bing tabs by default and closes them once they have loaded, then repeats the cycle each day when the browser is opened. The number of searches, the interval between tabs in seconds, and the delay before each tab closes are all configurable from the popup. The README states plainly that Microsoft's terms prohibit automated searches, so the extension is used at the user's own risk, and it depends on a logged-in Microsoft Rewards account.

Key capabilities

• Produces two browser targets from one WXT + React codebase: a Chrome MV3 build in wxt/dist/chrome-mv3 and a Firefox MV2 build in wxt/dist/firefox-mv2.
• Opens ten random Bing search tabs by default and closes each one after it loads, with the search count adjustable in the popup.
• Schedules the tab batch automatically each day when the browser is opened, a setting that is turned on by default.
• Exposes timing controls for the gap between tabs in seconds, where a value of 0 opens all tabs at once, and for the close delay, where 0 closes a tab as soon as it loads.
• Ships a React popup with shared components and hooks for storage and search-progress tracking, backed by a search term pool in the /data directory.
• Includes a companion Flutter Android app in /microsoft_rewards_app, distributed through a GitHub Releases tag rather than an app store.
• Supports a full development workflow from the wxt directory: npm run dev, npm run dev:firefox, npm run compile, npm run test (Vitest), npm run build, and npm run zip for store uploads.

Who uses it and how

• Individual Microsoft Rewards members who keep a browser profile signed in at rewards.bing.com and want the daily search points collected without a manual routine.
• Desktop users who leave a browser running: the daily batch is triggered on browser start-up, so the run happens as part of opening the browser rather than as a separate task.
• Users who want to pace the run rather than fire everything at once, using the seconds-between-tabs and close-timer settings to spread tabs out.
• Android users who prefer the mobile route, installing the Flutter app from the GitHub release instead of a browser extension.
• Distribution is handled through the two public store listings, with packaged zips produced by npm run zip and npm run zip:firefox for those uploads.

Getting started

The simplest route is to install "Microsoft Automatic Rewards" from the Chrome Web Store or Firefox Add-ons, pin the extension, and log in at the Microsoft Rewards site. To build from source, run npm install and then npm run build inside the wxt directory, open chrome://extensions, enable Developer mode, and load the unpacked build from wxt/dist/chrome-mv3.

How it compares

The provided facts name no comparable extensions or paid products, so this project stands alone in this registry rather than sitting in a documented field of alternatives. The only contrast the facts support is with the manual routine it replaces, in which each daily Bing search is opened and run by hand.

When to use it — and when not to

There is nothing to host: the extension is a client-side browser add-on, so the operational requirements are a supported browser, a logged-in Microsoft Rewards account, and enough trust in the project to accept the risk the README itself flags. Anyone unwilling to act against Microsoft's terms, or whose account they cannot afford to put at risk, should not install it. The extension also tracks the structure of rewards.bing.com and Bing result pages, so it is only as reliable as those pages remain unchanged, and the mobile app is distributed through GitHub Releases rather than a store.

/wxt                        - Browser extension (WXT + React + TypeScript)
  /entrypoints
    background.ts           - Background service worker entry
    /background             - Daily rewards, scheduling, search runner
    rewards.content.ts      - Content script on rewards.bing.com
    bingResult.content.ts   - Content script on Bing search results
    /popup                  - Popup UI (React)
    /components             - Shared React components
    /hooks                  - React hooks (storage, search progress)
    /utils                  - Search, progress, settings, helpers
    /data                   - Search term pool
    /enums, /types          - Shared TypeScript definitions
  /public                   - Static assets copied into the build (icons)
  wxt.config.ts             - Manifest and build configuration
/microsoft_rewards_app      - Android app (Flutter)
/assets                     - Source icon artwork (icon.svg)
/scripts                    - Maintenance scripts (icon rasterization)
/docs                       - Documentation and README images

cd wxt
npm install

npm run dev              # Chrome, hot reload
npm run dev:firefox      # Firefox, hot reload

npm run compile          # TypeScript typecheck
npm run test             # Unit tests (Vitest)

npm run build            # Production build -> wxt/dist/chrome-mv3
npm run build:firefox    # Production build -> wxt/dist/firefox-mv2
npm run zip              # Packaged zip for store upload
npm run zip:firefox