A mod manager for Cyberpunk 2077 that lives inside VS Code and REDcode. One list of mods, four verbs, no jargon.
REDdeck keeps your mods in a library outside the game folder, deploys the ones you turn on with hardlinks, and undoes it just as cleanly. It recognises the frameworks (RED4ext, CET, redscript, ArchiveXL, TweakXL and friends), prepares REDmod packages, installs REDnode packages into REDnode's apps folder, writes the archive load order, and, with REDbridge present, shows conflicts between files inside mod archives, which file-level managers cannot see. The name: a deck of mods, a nod to the cyberdeck, and the mods waiting "on deck" before you deploy them.
Read the guide · Design · Releases · REDcode · REDbridge · REDnode
Note
Status: 0.20.1, in daily use on two PCs. Add from zip, 7z, rar, folder, Nexus link or Vortex; one row per mod with a version dropdown; hardlink deploy with a manifest, undo and backups; a pending-changes list that explains every file; conflicts by order with Let X win, and inside archives through REDbridge, which Get REDbridge fetches and keeps current; the Frameworks group with the game version and a warning after a game patch; Nexus sign-in in the browser (OAuth with PKCE, or a pasted key), daily update checks, update from the row, nxm download links; a wide table page with search, facets and sizes; loadouts; a Set up group for new installs; a reddeck command line with --json. Not on the Marketplace: install the VSIX from the releases page. npm run smoke and npm run test:ui cover it. The guide says how to use it.
Library (outside the game) REDdeck (VS Code extension) Game folder
┌───────────────────────────┐ ┌───────────────────────────┐ ┌──────────────────────────┐
│ one folder per mod, laid │ deploy │ Mods view: on/off, status │ hardlink│ archive/pc/mod/ │
│ out exactly as it deploys │────────►│ classifier: kind + target │────────►│ r6/scripts, r6/tweaks │
│ mod.json, library.json │◄────────│ deployer: manifest, undo │◄────────│ red4ext/plugins, mods/ │
│ downloads/ (originals) │ undo │ Nexus client, nxm links │ verify │ bin/x64/plugins/cet/mods │
└───────────────────────────┘ └───────────────────────────┘ └──────────────────────────┘
optional: REDcode (install a packed project), REDbridge (archive conflicts)
| You do | REDdeck does |
|---|---|
| Install it | The Set up group in the Mods view walks through the rest: find the game (Steam's library list, GOG, Epic), Get REDbridge, sign in to Nexus, take the download links, import from Vortex. Each row is a button. |
| Open REDdeck | The wide table: every mod with version, kinds, size and status in columns, a search box, status facets and Largest first, the verbs across the top. For the bigger admin jobs; the sidebar is the compact companion. |
| Get REDbridge | Fetches the bridge that reads inside archives, and its .NET runtime if needed, into REDdeck's own folder. One click, nothing to configure. |
| Show conflicts | One page with every conflict, who wins, and a "Let ... win" button that changes the order. The deploy toast opens it. |
| Add a zip, 7z, rar, folder or Nexus link | Works out what kind of mod it is and where its files go. Asks only when it cannot tell. With REDdeck handling nxm links, the Mod manager download button on Nexus lands the file in the library. |
| Turn a mod on or off | Nothing on disk yet. The Deploy button counts the changes waiting, and Show pending changes lists each file with its reason. |
| Pick a version | One row per mod; the version cell is a dropdown of what is in the library, plus Get x.y from Nexus when there is a newer file. |
| Patch day | The Frameworks header says "game updated to 2.31" when the game changed since the last deploy, and REDdeck checks the frameworks on Nexus once for that version. |
| Deploy | Hardlinks the enabled mods into the game, writes the load order, prepares REDmod packages, records a manifest. |
| Remove | Deletes the mod from the library. Deployed files come out on the next deploy. |
| Add to Project | With a REDcode project open, copies a mod's loose files into its source/resources under their deploy paths. Archives are for REDcode's Game Assets view. |
| Undo deploy | Removes every file in the manifest and nothing else. |
| Path | Contents |
|---|---|
src/ |
The extension. core.ts gathers the VS Code-free parts: classifier, library, deploy, extract, vortex |
bin/reddeck.mjs |
The command line over the same core; reddeck mcp starts the MCP server |
src/mcp.ts, src/verbs.ts |
The MCP server and the verbs it shares with the command line |
scripts/smoke.mjs |
End-to-end test of the core against a fake game folder |
images/ |
Activity bar icon and extension icon |
docs/ |
Documentation site: the guide, the design and the dev setup |
tools/brand/ |
Generates the banner, badges and icon |
git clone https://github.com/Edgemodders/REDdeck.git
cd REDdeck
npm install
npm run build # or: npm run watch
npm run smoke # classify, add, deploy, undo against a temp folderOpen the folder in VS Code and press F5 to run the extension in a second window. Details in the setup guide.
node bin/reddeck.mjs list # what is in the library and its status
node bin/reddeck.mjs add "C:\Downloads\Mod.zip" --name "My Mod"
node bin/reddeck.mjs install-project "C:\Mods\MyMod\MyMod.cpmodproj" # a packed project, added or refreshed
node bin/reddeck.mjs on my-mod && node bin/reddeck.mjs deploy
node bin/reddeck.mjs conflicts --json # every command prints JSON with --json
--library and --game override the folders. The library's JSON files are the only state, so an assistant can read them directly and use the command line to act.
On npm as @edgemodders/reddeck-mcp: npx -y @edgemodders/reddeck-mcp (server) and reddeck (CLI), published with every release at the extension's version; scripts/npm-package.mjs assembles it from the build, the README is docs/npm.md.
The same verbs are MCP tools: node dist/mcp.js --library <folder> --game <folder> serves reddeck_list, reddeck_mod, reddeck_add, reddeck_install_project, reddeck_turn, reddeck_move, reddeck_remove, reddeck_pending, reddeck_deploy, reddeck_undo, reddeck_changes, reddeck_conflicts, reddeck_loadout and reddeck_vortex over stdio. VS Code 1.101 and later picks the server up from the extension for the agents it hosts; REDdeck: Connect an assistant (MCP)... copies the claude mcp add line for Claude Code. The Mods view follows what an assistant changes.
- M0 Decide. Name, repository, the word list, the extension scaffold.
- M1 Library. Add from archives and folders, the library layout, hardlink deploy with manifest and undo, changes made outside REDdeck, Vortex detection and import. Done.
- M2 Kinds. Frameworks group with game version check, REDmod packages, file and archive conflicts with reorder. Done.
- M3 Nexus. Sign in (OAuth with PKCE in the browser once Nexus assigns the client id, a pasted key until then and as a choice always), mod metadata, updates, nxm links. Done.
- M4 Loop. Install and test a REDcode project with one click (REDdeck side done; the REDcode side is in that repo). REDnode packages as a mod kind.
- M5 Share. Loadouts, the
reddeckCLI and the MCP server are done. No Marketplace publishing for now; releases carry the VSIX.
Vortex works and supports two hundred games. REDdeck supports one, so it can leave out profiles, activators, phases and the thirty-odd installer rules that make Vortex feel heavy for Cyberpunk. It keeps the parts that are unavoidable: a library outside the game, a deployment manifest, detection of changes made outside the manager, load order, conflicts and Nexus links. REDdeck refuses to deploy while Vortex manages the same game folder, and can import Vortex's library.
MIT. This repository contains no game files, no mod files and no data extracted from the game. Single-player modding only. Nexus Mods is used through its public API under its acceptable use policy. REDmod, REDengine and Cyberpunk 2077 are CD PROJEKT's. A cyberdeck is theirs too; a deck of mods is ours.