On this page
Know what you are changing
Cheat searches can mean a debug menu, altered save data, console commands or a modified third-party game. These are different methods. A code written for one edition or mirror may not work in another and should not be described as a universal redeem code.
Protect a separate original save
Export the current save and keep an untouched copy, as the saves and backups guide describes, before experimenting. Importing another save can overwrite your current progress. Keep the edition, date and purpose in the backup filename so you can recognise the original later.
The practice bakery is separate
Homepage practice saves use an original format. Official-game cheat names, import strings and commands do not apply to that mode. Resetting the practice game affects only its own local data and must require confirmation.
Cookie Clicker cheat name: saysopensesame
In the official browser game, click your bakery name and change it to Baker saysopensesame. Keep a name before the lowercase suffix saysopensesame. Confirm the rename to open the Open Sesame debug interface. This is the bakery-name cheat people also call the admin panel, dev tools or mod menu; it is not a promo or gift code.
The browser source checks the suffix and disables this name trigger in the Steam app. A similarly named Scratch project or numbered sequel can have entirely different rules. On a Chromebook, the browser method applies only if you can open the official game and rename the bakery. It does not require a browser extension.
Export your original save before enabling debug features. Rename the bakery without the suffix and reload to leave the debug session; that does not undo cookies or achievements already saved. Import your untouched backup to restore the earlier state.
Browser console commands and what they do
Open the official browser game, then open your browser developer tools and select Console. Run one understood command at a time in the game tab. These examples affect your local single-player save; they are not commands for the practice bakery.
Use a finite amount rather than Infinity: infinite values can make later arithmetic and save data unusable. A command changes the game state, so export a backup before testing.
| Item | How it works |
|---|---|
Game.Earn(1000000); | Adds one million cookies through the game’s earning function. Replace the number with another finite amount. |
Game.lumps += 10; | Adds ten sugar lumps to the current state. This bypasses normal lump progression. |
Game.OpenSesame(); | Opens the debug interface directly in the browser game. |
new Game.shimmer('golden'); | Creates a golden-cookie shimmer; click it to trigger its rolled effect. |
Game.RuinTheFun(); | Grants extensive progress and upgrades. Use only on an expendable test save. |
Steam, mobile and commands that do not work
The Steam edition does not activate the browser name-suffix shortcut. It has its own mod system; use the mods guide for that workflow. Mobile editions do not expose a desktop browser console in the same way. This page does not promise that browser commands work on Steam, Android or console editions.
If the console reports that Game is undefined, check that you are on the loaded official game page rather than this guide, an advertisement frame or a clone. If a command produces unexpected results, stop and restore your exported save. Cheats can change the meaning of achievement and speedrun progress; keep an unmodified save for those goals.
Gift codes are separate from cheats
Cookie Clicker also has a gift-code feature through the Wrapping paper heavenly upgrade. A player-generated gift code is different from a universal promo code, a debug command or an exported save. Use the gift redemption controls for that feature; do not paste a game save into a gift-code box.
