Cyberpunk 2077 console commands: a dev-oriented guide

Cyberpunk 2077 console commands: how the modding console really works

The retail release of Cyberpunk 2077 does not expose a developer-style console the way Bethesda RPGs or Source-engine games do. There is no in-game command line you can summon from the main menu, no `~` key that opens a built-in REPL, and no menu of toggles labelled “console commands” in the options. What the community calls Cyberpunk 2077 console commands is, in practice, a runtime scripting layer bolted on top of the game by a third-party mod: CyberEngineTweaks. Understanding that distinction is the difference between a safe experiment and a corrupted save.

this page treats the topic as an engineering problem rather than a cheat list. The audience is a player or technical user who wants to understand what the console actually is, where it lives, which commands are reliable across patches, what can break a save, and how the workflow fits into a broader PC modding setup. The goal is not to encourage reckless use, but to document the tool accurately so that readers can decide for themselves which commands are worth enabling and which are best left alone.

What the “console” actually is in Cyberpunk 2077

When modders talk about Cyberpunk 2077 console commands, they are almost always talking about a Lua-scriptable runtime that injects itself into the game’s process and exposes a set of functions for reading and writing game state. It is not part of REDengine’s normal shipping configuration. CD Projekt Red shipped the game with debug hooks disabled for retail builds. CyberEngineTweaks works by reverse-engineering those hooks, re-enabling a subset of them, and presenting them through a console overlay drawn on top of the game window.

From a software architecture standpoint, three pieces matter:

Loader DLL: a small dynamic library that is placed next to the game’s executable. When the game starts, the loader attaches to the process, reads configuration, and starts the runtime.
Overlay: the on-screen console you see when you press the activation key. It accepts typed commands, shows history, and exposes a small status display.
Lua scripting host: the actual programming surface. Most “console commands” are thin wrappers around Lua functions defined by the mod, with a friendly syntax on top.

This matters because it explains why some commands are stable across patches while others break. When CDPR changes an internal class name, a memory layout, or a serialization format, any command that touches that part of the game can silently stop working or, worse, return data in an unexpected shape. The console is a third-party shim, not an official API surface.

CyberEngineTweaks installation and folder layout

Installation is deliberately simple, which is one reason the tool became the de facto standard for Cyberpunk 2077 console commands. The steps described here follow the convention documented by the project and echoed by community wikis such as the IGN Cyberpunk 2077 console commands and cheats list, which provides useful background for this point. Versions and exact filenames can change between releases, so treat the steps below as a structural guide rather than a pixel-perfect recipe.

Locating the game directory

Before dropping any files into the game’s folder, you need to know where Cyberpunk 2077 actually lives on disk. The path differs by storefront:

GOG: the default install path is `GOG Games\Cyberpunk 2077\` inside the folder where you keep GOG titles. The launcher stores a small metadata file alongside the binary, but the playable files all sit under that root.
Steam: the canonical path is `SteamLibrary\steamapps\common\Cyberpunk 2077\`. If you keep Steam on a non-default drive, substitute the actual library root.
Epic Games Store: the install path is normally under `Program Files\Epic Games\Cyberpunk 2077\` on Windows, or under the custom folder you chose during install.

Whichever storefront you use, the binary you are looking for is `Cyberpunk2077.exe`. Everything else in the install, including the `archive` and `r6` subfolders that contain the bulk of the game data, is treated as read-only by the mod.

Placing the loader and scripts

Once you have located the install directory, download the latest stable CyberEngineTweaks archive. The release is shipped as a zip containing a small number of files:

The loader DLL, which the project’s installer expects you to drop directly next to `Cyberpunk2077.exe`.
A `bin` folder containing additional native dependencies.
A `cyber_engine_tweaks` folder with the Lua scripts, UI definitions, and config files that define how the console behaves.

After extraction, the install root should look roughly like the structure below. Names can shift between releases, so use this as a reference, not a literal file list.

Path (relative to game root)	Purpose	Notes
`Cyberpunk2077.exe`	Game binary	Original CDPR file, do not modify.
`version.dll` (or current loader name)	CyberEngineTweaks loader	Sits beside the executable; renamed only if the project instructs it.
`bin/`	Native dependencies	Includes graphics and input bridges used by the overlay.
`cyber_engine_tweaks/scripts/`	Lua command implementations	Where most “console commands” actually live.
`cyber_engine_tweaks/config.json`	User-editable settings	Controls hotkeys, telemetry, and startup behaviour.

Once the files are in place, start the game normally. If the loader attaches successfully, pressing the tilde key (`~`) brings up the console overlay. If nothing appears, the most common cause is that an antivirus product or a custom permission blocked the DLL, or that the loader was placed in a subfolder instead of the game root.

Opening and navigating the console

The default hotkey for the CyberEngineTweaks console is the tilde key, the same key many PC games use for their built-in terminals. If your keyboard layout does not expose `~` in a convenient place, the project’s settings allow remapping to other keys. The overlay is modal: when it is open, the game world pauses for input, but the underlying simulation does not freeze, which means timed events and NPC behaviour continue while you type.

A few practical habits make the console easier to live with:

History recall: the up and down arrow keys scroll through previously typed commands, which matters because long Lua calls are tedious to retype.
Tab completion: tab expands partial identifiers, including function names defined by the scripts and many of the game’s internal singletons.
Multi-line input: shift plus enter inserts a line break, which is useful for the longer command blocks described later.

These behaviours are not part of the base game. They are part of the mod’s user experience layer, which is why a clean, current install matters. Older releases had rougher text input and a less responsive overlay.

Categories of useful Cyberpunk 2077 console commands

Once the console is open, the command surface is broad enough that it helps to think in terms of categories rather than individual lines. Most readers will only need a handful of categories, and each has different reliability characteristics.

Player state and stats

Player-targeted commands change the avatar’s health, money, attributes, perks, and cyberware capacity. They are the most common reason players install the console at all. Two patterns dominate:

Additive commands: functions that take a numeric argument and add it to the current value, for example adding a fixed amount of eddies or a flat bonus to a stat.
Setter commands: functions that overwrite a value entirely, useful for clamping a stat to a specific level or restoring a corrupted perk tree.

Reliability for this category is generally high across patches because the player object is one of the most stable interfaces in the game. What changes more often is the syntax of the helper, not the underlying data.

Inventory and item spawning

Item commands let you spawn weapons, clothing, consumables, and quest items directly into the player’s inventory. The command takes an item identifier and an optional count, and the helper script does the work of resolving the identifier into a real item record.

Item identifiers are not the same as the names you see in the in-game UI. They are short strings drawn from the game’s data tables, and they vary by patch. A reference list of stable identifiers is one of the more useful resources to keep offline, because spawning a weapon with the wrong identifier either does nothing or, in some cases, creates a record the inventory system does not know how to render.

Gameplay and quality-of-life toggles

This category is the most varied. It includes toggles that change how the simulation behaves rather than the player’s state. Common examples include:

Time scale: changes how fast the in-game clock advances, useful for skipping long waits or slowing combat for analysis.
Permanent unlocks: shortcuts to mark a perk, a skill, or a cyberware slot as unlocked without paying the in-game cost.
AI behaviour: switches that freeze or detach nearby NPCs, which can be used to clear a stuck encounter or to test how a quest progresses without interference.

Quality-of-life commands are also where patch sensitivity is highest. CDPR adjusts AI behaviour, perk trees, and progression systems in almost every major update, so a command that worked in one patch may be ignored or, worse, partially execute in the next.

Teleport and world navigation

Teleport commands take X, Y, and Z coordinates and place the player at that position in the world. They are useful for unstucking a save, for skipping a long on-foot segment during a replay, and for reaching debug-only coordinates that the game normally hides. As the IGN guide on Cyberpunk 2077 console commands and cheats notes, teleporting to coordinates that are not associated with a valid navigation mesh can leave the player stuck. The console does not check whether the destination is a legal place to stand; it simply sets the position and lets the engine sort out collisions on the next frame.

Safe practice is to keep a small notebook of verified coordinates for major fast travel points, mission triggers, and the player’s owned apartments, and to treat any coordinate posted in a forum thread as untrusted until it is tested in a controlled save.

Example command patterns and what they actually do

The exact syntax of CyberEngineTweaks commands shifts between releases, so the patterns below are written as illustrative examples rather than as copy-paste-ready lines. Treat them as templates and adapt the helper names to whatever the current release exposes.

Adding money, perks, and stat points

Player resources are the simplest place to start, because the helpers involved are stable across most patches and the effect is visible immediately.

Add currency: a function such as `AddMoney(amount)` increases the player’s eddies by the given amount. It is additive, not a setter, so it cannot reduce the player’s wallet.
Grant perk points: a function such as `AddPerkPoints(n)` adds unspent perk points. It does not automatically spend them, so the player can still choose where to apply them.
Grant attribute points: similar to perk points, attribute points are usually granted by a separate function because they feed into a different part of the progression system.

These helpers are implemented in Lua, not in the engine, which means the actual game logic that consumes the points is unchanged. You are still earning the reward through the normal validation path, which is why the values stick across save and reload.

Spawning items by identifier

Item spawning is the second pattern most players learn. A representative template looks like the line below, where the angle-bracket placeholders mark values the user must supply:

`SpawnItem(““, )`

The `` is a string drawn from the item database, not the display name. For example, a category like “iconic pistols” maps to a small set of identifiers, each tied to a specific record. `` is optional and defaults to one. The helper places the resulting record into the player’s inventory at the next available slot.

Two failure modes are common:

Unknown identifier: the function returns an error in the console, and the inventory is unchanged. The game is unaffected.
Known but unavailable identifier: in rare cases, a valid identifier references a record the current quest state or DLC ownership does not allow. The item appears in the inventory but is invisible to the UI until the gating condition is satisfied.

Teleporting with coordinates

Teleport commands accept three numbers, normally in the order X, Y, Z. The coordinate system is the same one used by the in-game photo mode and by most world-space overlays, with Z being vertical.

`Teleport(, , )`

A few guardrails make coordinate teleporting less risky:

Stand at a known-good location, open the console, and read the player’s current position with the equivalent of a `GetPlayerPos()` helper. Use that as a reference frame for any teleports you script by hand.
Prefer coordinates that are known to sit on a navigation mesh. The safest sources are mission triggers and fast travel points, which the game’s own systems validate every time the player uses them.
Avoid teleporting during a cinematic, a quest dialogue, or a vehicle sequence. The console can run, but the underlying scripted sequence may not handle the discontinuity and can softlock the mission.

Practical risk analysis: what is safe, what is fragile

Not all commands carry the same risk profile. The list below separates them by impact on the save file, ranked from least to most disruptive.

Risk level	Category	Typical effect	Recovery if it goes wrong
Low	Read-only queries	Display stats, coordinates, or quest state without writing anything.	Reload the save; nothing changed.
Low	Additive money or perk grants	Increase the player’s wallet or unspent points.	Reload the save; values are small and easy to detect.
Medium	Item spawn by identifier	Adds an item to the inventory. May create gating mismatches with quests.	Reload the save and avoid the affected quest until the gating is resolved.
Medium	Teleport to a verified coordinate	Relocates the player. Risk of being stuck in geometry.	Teleport back to a known anchor or reload the save.
High	Quest state mutation	Force-completes a quest stage or rewires a flag used by scripted events.	Reload a previous save; the affected quest may be unrecoverable on the current save.
High	Mass AI freeze or hostile NPC edits	Disables nearby NPCs or rewrites AI blackboards.	Reload a previous save and avoid running the command during active combat or scripted scenes.
Severe	Direct memory writes outside the mod’s helpers	Modifies engine structures the mod does not validate.	Save may be unrecoverable; expect to roll back to a backup.

Two patterns explain most of the failures in the upper rows of the table. First, CDPR refactors quest systems, perk trees, and inventory serialization between patches, and any command that touches those systems has a built-in expiry date. Second, the mod exposes helpers that look generic but actually wrap a small Lua snippet that itself depends on a specific engine version. When the engine changes, the snippet silently degrades.

Performance and stability: why the console is not free

Running an external runtime on top of a retail game is never free. The console overlay, the Lua host, and the bridge between Lua and the engine all cost frame time, memory, and occasionally stability. The impact is usually small on a modern desktop CPU, but it is not zero.

Frame time and input latency

Every time the console overlay draws, it issues a small batch of rendering work that the engine has to schedule alongside the normal frame. On a high-end machine, this is invisible. On a mid-range laptop or a handheld PC, it can show up as occasional microstutter, especially when the console is open while the engine is streaming new world data.

Input latency is a subtler effect. Because the overlay is modal, the game processes input either through the console or through the simulation, never both. The round-trip time is normally trivial, but if the Lua host is in the middle of a long script, the next input can be delayed by tens of milliseconds. For most players this is irrelevant; for someone trying to record clean combat footage, it is not.

Memory overhead and garbage collection

The Lua host is a managed runtime, and the helpers that ship with CyberEngineTweaks allocate small objects every time they are called. Most of them are short-lived and are cleaned up by the next garbage collection cycle, but a script that runs in a tight loop can outpace the collector and trigger a noticeable hitch. The standard mitigation is to keep console scripts short, to avoid tight loops unless the helper is explicitly designed for them, and to clear the console history when it grows.

Save file integrity

This is the part that matters most in the long run. Cyberpunk 2077 saves are large binary blobs, and the integrity checks the game runs on load are stricter than the checks it runs on save. The console does not corrupt saves directly, but it can put the save into a state the engine later decides is inconsistent. The two scenarios to watch for are:

Quest flags in impossible combinations: a command that grants a reward normally tied to a quest stage that has not been set can put the quest system into a configuration the next patch decides is invalid.
Inventory records that reference missing assets: spawning an item with the wrong identifier can leave a record in the inventory that points at a deleted asset, which the next save cycle may or may not clean up.

Both cases are recoverable by rolling back to a previous save, which is why the next section treats backup discipline as a non-optional part of the workflow.

Backup discipline before opening the console

The cheapest insurance against a console-induced problem is a clean backup, taken before any command is run. The game’s save files live in a platform-specific user folder, separate from the install directory.

Storefront	Typical save folder on Windows	Backup approach
Steam	`%USERPROFILE%\Saved Games\CD Projekt Red\Cyberpunk 2077\`	Copy the entire folder before the first console session.
GOG	`%USERPROFILE%\Saved Games\CD Projekt Red\Cyberpunk 2077\`	Same folder as Steam; cloud sync can be paused in the launcher.
Epic	`%USERPROFILE%\Saved Games\CD Projekt Red\Cyberpunk 2077\`	Same folder; cloud sync uses the same path.

Two practical habits help. First, take a fresh backup before every major console session rather than relying on the cloud copy, because cloud sync can overwrite a working local save with a corrupted one before the user notices. Second, name backups with the date and a short tag such as `before-teleport-test` or `before-perk-respec`, so it is obvious which save to roll back to without opening each one.

Console commands and mod compatibility

Cyberpunk 2077 supports a richer modding ecosystem than most players realise, and the console is only one part of it. Script extenders, gameplay overhauls, and cosmetic mods all touch the same engine the console does, and conflicts are common when more than one of them wants to modify the same data.

The general rules of thumb are:

One scripting runtime at a time: running CyberEngineTweaks alongside another Lua-based mod that already provides its own console or scripting host can lead to double execution of the same hook. Disable one of the two if a conflict appears.
Patch parity: mods written for a specific patch may rely on internal class names that CDPR renames in the next one. If a console command stops working after an update, check the mod’s release notes before assuming the command is broken.
Load order: when several mods touch the same game system, the order in which they load can change which one wins. The console’s own scripts are usually loaded last, which means they can override earlier mods but not the other way around.

This is also why most serious modders keep a separate install of the game for console-driven experimentation, distinct from the install they use for their main playthrough. A clean, minimal install with only the console mod and a small set of compatible utilities is much easier to debug than a heavily modded one.

Troubleshooting common problems

Even a clean install can fail in subtle ways. The list below covers the issues that come up most often in community threads, with the diagnostic steps that usually resolve them.

The console does not open on `~`: the most common cause is that the loader DLL was blocked by Windows SmartScreen or by an antivirus product. Right-click the DLL, check the file properties, and confirm it is allowed to run. The second most common cause is that the DLL was placed in a subfolder instead of the game root.
The console opens but no commands work: the Lua scripts failed to load. Check the `cyber_engine_tweaks` folder for a log file, and confirm that the `scripts` directory is present and readable. A missing or renamed folder is the usual culprit.
Commands run but have no visible effect: the helper is targeting a game system that the current patch has refactored. Roll back to a previous save, update the mod to the latest release, and re-test.
The game crashes when a command runs: the command is either out of date or was applied to a state the engine does not handle. Reload the previous save and avoid the specific command until the mod author publishes a fix.
The game crashes on launch with the mod installed: another mod is conflicting with the loader. Disable other mods, confirm the console works, then re-enable the rest one at a time.

None of these failures are unique to Cyberpunk 2077, but the mix of a retail console game, a third-party runtime, and a heavily modded ecosystem means the failure surface is wider than a typical single-player RPG. A patient diagnostic approach pays off.

Ethical and policy considerations for PC players

Console commands live in a grey area for online play. Cyberpunk 2077 does not have a competitive multiplayer mode, so the usual arguments about fair play do not apply, but the mod still touches the same save format and can interact with cloud sync. A few ground rules help avoid the most common misunderstandings:

Single-player only: the console is intended for offline, single-player experimentation. Using it while connected to a service that expects unmodified game state is a good way to lose progress.
Cloud sync: many storefronts will happily upload a save that has been mutated by console commands. If you intend to share a save with another player or carry it to a new install, consider disabling cloud sync for that save first.
Screenshot and video policy: content recorded with the help of console commands should be presented honestly. Most platform terms of service require clear disclosure when a game’s normal progression has been altered.

None of these are legal requirements; they are practical habits that protect the user from avoidable loss.

Where the tooling is likely to go next

CD Projekt Red’s approach to the console has been to leave the retail build as it is and let the community maintain its own runtime. There is no public roadmap for shipping an in-game console, and the studio’s official position is that mods and console commands are a community concern rather than a first-party feature. That has not changed in recent patches, and there is no verified announcement that suggests it will.

What has changed is the maturity of the tooling. Newer releases of CyberEngineTweaks focus less on adding commands and more on hardening the host, reducing the failure modes described in the troubleshooting section, and providing better diagnostics when a command does not work. The community wiki pages and project changelogs are the best source of current detail; the older the source, the more likely it is to be wrong about a specific command.

For the reader who treats Cyberpunk 2077 console commands as a development-style tool rather than a cheat code, the practical path is straightforward: keep a clean install, back up the save before every session, learn the categories rather than memorising individual lines, and treat each patch as a reset of the command surface. The console is a useful piece of kit, and like most useful kit, it works best when it is treated with a small amount of caution.

Frequently asked questions

Does Cyberpunk 2077 have a built-in console like Skyrim or Fallout?

No. The retail release does not expose an in-game command line. The console players use is provided by the third-party mod CyberEngineTweaks, which injects a runtime into the game process and draws an overlay on top of the window. Calling it a “built-in console” is a useful shorthand, but it is technically a mod.

Is installing CyberEngineTweaks safe for the main save?

Installing the mod is safe for the save as long as the user follows the usual hygiene: place the files in the correct folder, confirm the loader is not blocked by the operating system, and take a backup of the save directory before the first console session. Running the mod itself does not touch the save until a command is actually issued.

What is the tilde key supposed to open the console?

The default activation key is the tilde (`~`), the same key used by many PC games for their debug terminals. If the key does not work, the most likely cause is that the loader failed to attach, often because the DLL is in the wrong folder or was blocked by security software. The activation key can also be remapped in the mod’s configuration file.

Do console commands work in the latest patch?

They work for the categories that the current mod release has been updated to support, which usually includes the most common player state, inventory, and teleport commands. More advanced commands, especially anything that touches quest state or AI blackboards, often lag the engine and may be missing or partially implemented for one or two patches after a major update.

Can console commands be used in Phantom Liberty or other DLC content?

Yes, the console runs at the engine level and is not gated by ownership of a specific expansion. That said, the quest and world systems in Phantom Liberty are different enough from the base game that some commands have to be re-tested after the expansion is installed. Treat the DLC as a separate environment until the mod’s release notes confirm full support.

Why does teleporting to a coordinate sometimes leave the character stuck?

The console writes the player’s position directly and does not check whether the destination is a valid place to stand. If the coordinate is inside a wall, below the world, or above the navigation mesh, the engine will not move the player back. The safe practice is to use coordinates taken from known-good locations, such as fast travel points or mission triggers, and to keep an anchor coordinate in the notes for an emergency return.

Are there commands that grant cyberware or perks without spending points?

Yes, the mod provides helpers for adding unspent perk points and for granting specific perks and attribute points. The exact helper names change between releases, so the current documentation is the right reference. The granted values go through the normal progression validation, which is why they stick across save and reload.

Can two players share a save that has been edited with console commands?

Technically yes, but with caveats. The save itself is portable across installs of the same game version, and the console does not embed a signature into the file. The risk is that the other player’s install may be on a different patch, in which case the mutated state can fail validation. Sharing mutated saves between players is best done with both players on the same patch and the same mod version.

Do console commands affect achievements or trophies?

Cyberpunk 2077 does not use a console-platform achievement system that ties to a verification server, so most local achievements are unaffected. Where the game does sync to a service, the safest assumption is that mutated saves are not treated as equivalent to a clean playthrough. If achievement integrity matters, the cleanest approach is to keep two parallel saves, one for experimentation and one for clean progression.

What is the best way to learn the current command set?

Start with the mod’s own release notes, which usually list the helpers added or removed in the latest version. Cross-reference with a community wiki or guide such as the IGN Cyberpunk 2077 console commands and cheats list, and then verify any command on a backed-up save before relying on it for a real playthrough. The command surface changes often enough that last year’s list is rarely a reliable source for this year’s patch.

Cyberpunk 2077 console commands: a developer-oriented guide