AugmentedSteam: A Browser Extension for Steam

What AugmentedSteam Changes in Steam

AugmentedSteam addresses a familiar problem: Steam exposes substantial information, but finding and acting on it can require repeated navigation and manual sorting. The extension adds controls and information directly to Steam pages for users who spend time researching games, managing a library, tracking prices, or organizing marketplace and community activity.

Its documented scope is broad. Price panels can show the current best price and historical low for games and downloadable content, with data sourced from authorized stores. Library-facing pages can make owned, wishlisted, and ignored products easier to distinguish. The extension also recognizes an IsThereAnyDeal Waitlist and Collection, but the repository warns that the browser extension is not the server repository. That distinction matters for anyone searching the GitHub organization and expecting to find the complete service infrastructure in this project.

Other features operate on community and inventory surfaces. Users can sort or filter the market, games, friends, groups, achievements, badges, and reviews. Product search can use criteria such as review count, review score, and Early Access status. Inventory pages can expose Quick / Instant Sell items. There are also game notes, custom profile styles, custom links, controls for hiding content blocks, automatic skipping of Steam age gates for NSFW content, and batch operations such as registering several product keys or adding several pieces of downloadable content to a cart.

This is not a separate game client or a Steam replacement. It is an extension that augments Steam through the browser. Its value is therefore tied to Steam's own web interface, browser support, extension permissions, and continued compatibility with site changes.

Supported Browsers and Extension Distribution

The README links separate distribution pages for three browsers: Chrome, Firefox, and Microsoft Edge. End users should install from the browser's extension listing rather than building from source unless they intend to work on the code. Each store listing is the authoritative place to inspect the version available to a particular browser, because the repository's development branches and local build output are not the same distribution channel.

The source identifies `augmented-steam` as its npm package name. Its package scripts build Firefox and Chrome artifacts, while the README also documents an Edge badge and store entry. However, the README does not give an Edge-specific build command, so this article does not invent one. It also does not describe the steps for loading an unsigned local build into a browser. A first extension run through a local build therefore cannot be documented completely from the README.

The README explicitly directs users to augmentedsteam.com for more information and provides direct Chrome, Firefox, and Edge listings. It also points support requests toward Discord channels named `#as-general` and `#as-bugs`, while asking contributors and users to report bugs through the repository issue tracker. This split may be useful to prospective adopters: general questions and bug reports have documented destinations, although the README does not state a response policy or service-level expectation.

Browser distribution also means that Steam behavior can differ from native desktop-client behavior. Features described in terms of Steam pages, search filters, profiles, inventory actions, or batch controls assume that users operate those surfaces in a browser. The README does not document support for Steam's standalone desktop application.

Development Setup and First Build

AugmentedSteam documents a Node.js and npm development path. The first documented setup command installs the packages listed by `package.json` and locked by `package-lock.json`. From a checkout of the default `develop` branch, run:

npm install

After installation, create a development build for Firefox with:

npm run build firefox

Or create a development build for Chrome with:

npm run build chrome

These commands invoke the repository's `build` script, defined in `package.json` as `node scripts/build.mjs`. The README does not state the output directory, so a user should inspect `scripts/build.mjs` and the generated build location rather than assume a conventional extension path.

For a production build, the documented commands are:

npm run build firefox -- --production

npm run build chrome -- --production

The additional `-- --production` argument reaches the Node build script through npm. The README also documents this way to list all available build options:

npm run build -- --help

That help command is the correct first step if a user needs an option not covered by the basic tutorial. The repository does not document browser installation of the resulting local artifact, so loading it into Chrome or Firefox remains outside the README's setup instructions.

Before release work, the package exposes a static checking command:

npm run check

According to `package.json`, this runs TypeScript checking with `npx tsc --noEmit` and then `svelte-check`. It is a useful verification step because the repository combines TypeScript tooling with Svelte components.

Source Layout and Release Toolchain

Based on the repository layout, the extension is maintained as a JavaScript-oriented project with TypeScript configuration and Svelte components. The top-level `src/` directory contains application code, while `scripts/` contains the build and maintenance programs. Root files such as `package.json`, `package-lock.json`, and `tsconfig.json` define the local toolchain. Other visible entries include `.gitmodules`, `changelog.yml`, localization badges, and GitHub configuration.

The build entry point is `scripts/build.mjs`, as shown by the `build` script. Dependencies include `esbuild`, `esbuild-svelte`, `svelte-preprocess`, and `svelte-loader`, which points to a JavaScript build process that also handles Svelte-related compilation. `webextension-polyfill` provides the browser extension API layer exposed to the code. Runtime and utility packages include `luxon`, `idb`, `zod`, `dompurify`, `protobufjs`, and `@melloware/coloris`.

The package scripts also reveal maintenance tasks that the README does not describe in narrative form. Locale data can be downloaded or compiled:

npm run update-locales

npm run compile-locales

A combined locale command is available:

npm run locales

That script attempts `npm run update-locales` and falls back to `npm run compile-locales`. Protocol buffer sources can be compiled through the documented `protobufs` script, and releases are produced through `npm run release`, which first runs `npm run check` and then invokes `node scripts/make-release.mjs`.

These scripts make the repository more than a collection of page modifications. It has a build pipeline, locale maintenance, schema checking, protocol buffer compilation, and release packaging. Contributors still need to account for the cost of keeping those pieces compatible as Steam and browser extension interfaces change.

Maintenance Signals and GPL-3.0 Obligations

The repository is not archived. Its last push was on 2026-10-16. Recent tagged releases include `v5.0.0` on 2026-10-02, `v4.8.3` on 2026-08-18, and `v4.8.2` on 2026-08-08. Those facts indicate recent project activity, but they do not guarantee compatibility with every Steam workflow or browser release.

The declared license is GPL-3.0. The README credits Enhanced Steam copyright from 2012 through 2018 and identifies AugmentedSteam as both a fork and a spiritual successor of Enhanced Steam, which reached end of life in February 2019. Anyone redistributing or modifying the project must follow the GNU General Public License version 3 or later as stated in the README. This is a license requirement, not legal advice.

The broad feature surface creates a meaningful upgrade cost. Steam page selectors, visible layouts, marketplace behavior, inventory actions, and profile features can change independently of this repository. The README does not publish a compatibility matrix for individual Steam features or browsers, and it does not promise automatic handling when Steam changes its pages.

There is also a release pipeline, but adopters cannot infer upgrade safety from the presence of tags alone. The most concrete pre-release check available in `package.json` is `npm run check`, followed by building the specific browser artifact and comparing the workflows that matter to the user. For normal installation, browser-store versioning and the permissions shown on the listing are more relevant than the Git commit date.

Limits of AugmentedSteam and the Native Steam Alternative

AugmentedSteam's main limitation is its dependence on browser behavior and Steam's web interface. A page-level feature can stop matching its target after Steam changes markup or workflow. Browser extension permissions can also grant the extension access to sensitive browsing contexts, so users should inspect the exact permission list in the Chrome, Firefox, or Edge listing before installation. The README describes the features but does not publish a full permission analysis or a guarantee that every page modification remains functional.

It is also the wrong tool for users who do not browse Steam through Chrome, Firefox, or Edge. The repository does not document a standalone desktop application, a mobile extension, or a self-hosted deployment of the companion service. Automatic age-gate skipping is a convenience documented by the project, not an administrative way to change account visibility settings.

The clearest alternative is Steam's native web interface without an extension. That approach grants no additional extension permissions and leaves the user with Steam's standard layout, search, store, library, inventory, and community controls. The tradeoff is direct. Native Steam does not add the documented price history panel, IsThereAnyDeal collection indicators, custom profile styles, extra sort and filter choices, notes, or batch actions described by AugmentedSteam.

Enhanced Steam is the historical alternative named by the project, but the README says it ended its life in February 2019. It is not a current substitute for evaluating present-day compatibility. For users who only need occasional Steam actions, the unmodified interface avoids extension maintenance and permission concerns. For users who repeatedly research prices or manage large Steam collections, the added controls justify closer evaluation of AugmentedSteam's browser permissions and current compatibility.

Editorial conclusion

Steam users who want price context, stronger filters, visible library states, profile changes, and batch operations should inspect the extension before installing it. Users who need an unchanged Steam interface, a documented self-hosted deployment, or minimal browser permissions should look elsewhere. Verify the store permissions and privacy behavior first, confirm that the required Steam workflows still match the extension, and inspect the GPL-3.0 obligations before modifying or redistributing the code. For developers, the first project-specific check should be whether `npm run check` passes after `npm install` on the default `develop` branch.

Frequently asked questions

Official sources

1. IsThereAnyDeal/AugmentedSteam on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases