Cookie Clicker Cheats: 9 Console Commands Tested, and Only 2 Unlock ‘Cheated Cookies Taste Awful’

In short

  • Cookie Clicker cheats: 7 of the 9 console commands we tested never set the “Cheated cookies taste awful” shadow achievement.
  • Only Open Sesame and setting the cookie bank directly do, and the flag can be removed.
  • Back up first: a NaN or text value in the bank wrecks a save.
  • Checked against: Cookie Clicker’s own game code (v2.058) and our test runs.

Seven of the nine Cookie Clicker cheats we tested never touch “Cheated cookies taste awful”, the shadow achievement some guides call a permanent mark. The game decides it with one line: every five seconds it checks whether your cookie bank is bigger than the cookies you have earned, and the Open Sesame panel awards it on opening. Cheats that add cookies the normal way, or hand you items, do neither.

We ran each command on a fresh save of the web version (v2.058, game code last modified 21 October 2026) on 16 November 2026, checked the result six seconds later, and read the game’s own main.js to explain it. We did not run the Steam version, so the Steam part rests on community guides and Orteil’s mod notes, and says so.

Quick start: open the console and run one safe command

  1. Back up: Options, then Export save, and keep the code somewhere safe.
  2. Open the console: in Chrome press Ctrl+Shift+J (Windows, Linux) or Cmd+Option+J (Mac), per Chrome’s DevTools documentation.
  3. Type Game.Earn(1000000) and press Enter. One million cookies land in your bank and the shadow achievement stays untouched.
  4. Stop there if you care about a clean record. Setting Game.cookies on its own, or opening Open Sesame, sets the flag.

Two things get mixed up. The browser console is where you type commands. Open Sesame is a separate “Dev tools” panel of buttons inside the game; the Cookie Clicker Wiki says you open it by ending your bakery name with saysopensesame or running Game.OpenSesame(); in the console. The shortcut Ctrl+O does not open it: in the game code it opens the Import save window.

Two-lane step diagram comparing the browser console route with the Steam dev-mode and mod routes for Cookie Clicker cheats
Browser steps were run on v2.058. Steam steps come from community guides and Orteil’s mod ReadMe and were not run by us. Diagram, not in-game footage.

The 9 console commands we tested, and what each one did

Only two of the nine set the shadow achievement: setting Game.cookies directly (item 2) and Game.OpenSesame() (item 9). The other seven left it at zero after six seconds. A tenth command, Ruin The Fun, comes just after the list.

  1. Game.Earn(1000000): adds to the bank and to cookies earned together, so the bank never exceeds what you earned. No flag.
  2. Game.cookies=1000000000: sets only the bank, so earned stays at 0. The flag arrived within six seconds. Game.cookies+=1000000 did the same.
  3. Game.Objects['Grandma'].getFree(10): ten free Grandmas, and the next one still cost 100, because the game’s own code comment says the price behaves as if you still didn’t have them. No flag.
  4. Game.Objects['Cursor'].buy(50): an ordinary purchase from the bank; after Game.Earn(1000000) it cost about 108,000 cookies. No flag.
  5. Game.Upgrades['Reinforced index finger'].earn(): owns the upgrade without paying. No flag.
  6. Game.Win('Click'): awards one named achievement. No flag, unless the name you pass is the shadow one itself.
  7. Game.gainLumps(10): ten sugar lumps. No flag.
  8. var s=new Game.shimmer('golden');s.force='frenzy': spawns a golden cookie with the effect you pick; clicking it gave the Frenzy buff. No flag.
  9. Game.OpenSesame(): opens the Dev tools panel and sets the flag at once.
Table of nine Cookie Clicker console commands showing which two set the Cheated cookies taste awful shadow achievement, with browser and Steam notes
Each command was run on a fresh save of the web version (v2.058, 16 November 2026) and checked six seconds later; the Steam column was not tested. Diagram, not in-game footage.

Two more are worth knowing. Game.RuinTheFun(), the “Ruin The Fun” button in the panel, earns about 1e30 cookies and unlocks nearly every upgrade and achievement, so it sets the flag too. And Game.cookiesPs=100000, which a competing guide lists as a cheat, does not stick: the game recomputes cookies per second, and in our runs it was back to its real value within about ten seconds, because the game recalculates cookies per second every ten seconds.

A bonus that is not console-only: a script that calls Game.ClickCookie() every 20 milliseconds, such as setInterval(()=>Game.ClickCookie(),20), managed about 47 clicks a second in our run. That earns the regular “Uncanny clicker” achievement, which the game’s changelog calls “pretty fast” clicking, not the shadow one.

What actually sets “Cheated cookies taste awful”

Three routes set it: a bank above cookies earned, opening Open Sesame, and the Open Sesame “All achievs” button or Game.RuinTheFun(). The first is the one that catches people.

The check is a single comparison in the game’s five-second pass: if cookies earned is lower than the cookies in the bank, win the achievement. Spending lowers the bank but not earned, so honest play always keeps earned at or above the bank. Game.Earn raises both together, which is why it is invisible. Our own check agrees: setting both values to a billion left it at zero.

That also settles a common claim. One guide, 3zebras, calls the flag permanent and says nothing removes it. The game has a function for it, Game.RemoveAchiev('Cheated cookies taste awful'), and we tested the catch. If the bank is still above earned, the check hands the achievement straight back within six seconds. Run Game.cookiesEarned=Game.cookies first, then the removal, and it stayed gone, including after an export and import. The flag does survive a plain save and load while it is set.

The flag costs little in play. Shadow achievements do not count toward your achievement total, and the milk level is that total divided by 25, so the flag never changes your milk. The only cost we found is a possible one on Steam, covered below.

Cheats that break your save

The commands that break saves are not the ones that flag you. They leave the bank holding something that is not a normal number.

Risk ladder for Cookie Clicker cheats, from harmless commands to flag-setting ones to save-breaking edits, with a back-up-first reminder
Harmless, flag-setting and save-breaking commands from our own test runs on throwaway saves. Diagram, not in-game footage.
  • Game.cookies=NaN (not a number): in the five-second pass the game resets the bank and cookies earned to 0. We lost a million earned cookies that way, and the code does exactly this.
  • Game.cookies='1e9' (quotes make it text): every later += glues digits on instead of adding. In our run the bank was a long text string six seconds later and read Infinity after an export and import.
  • The panel’s Wipe button, which keeps your bakery name and sets the flag again, and Game.HardReset(2) both delete your progress.

So back up first, every time. Options has Export save, and the web version also has Save to file. The game’s own warning is blunt: clearing your browser cache or cookies wipes a web save. Because the save lives in the browser, a second browser profile should give you a throwaway save to break, though we did not test that.

The Steam version: different doors

The bakery-name trick is web-only: the game code skips it when it runs as the Steam app, and the wiki says it “does not work in the Steam version”. The 3zebras guide says it works on both; the code and the wiki disagree, and we trusted them.

For a console on Steam, two community guides, GamePretty and Gameplay.tips, give the same steps: browse the local files, open resources/app/start.js, change DEV=0 to DEV=1 (around line 11) and relaunch. Both warn that it disables Steam achievements until DEV is back at 0, and a Steam discussion reply from November 2024 says you must switch DEV or BETA mode off again. We could not test this.

The official door is mods. Orteil’s mod ReadMe says a mod is a folder with an info.txt and usually a main.js, that you can drop your own into mods/local, and that by default mods “block the unlocking of Steam achievements while enabled” unless info.txt sets AllowSteamAchievs to 1. A mod’s main.js runs inside the game, so it should be able to call the same functions as the console, but we have not built one.

One more Steam warning, from a community thread and not verified by us: a player reported that owning the shadow achievement stops Steam achievements syncing, with a fix that involves removing it in the browser version, exporting and importing the save. Several others said the fix did not work for them.

Which approach fits you

If you are…Do this
Curious, never cheatedUse Game.Earn and getFree only. Nothing flags and nothing breaks.
Chasing every achievementKeep the main save clean: no Game.cookies=, no Open Sesame. Treat Game.Win as a debug tool.
Wanting to see the endgameUse Open Sesame and Ruin The Fun on a throwaway save, then delete it.
A Steam playerExpect Steam achievements to switch off while DEV=1 or a mod is on (unless the mod allows them), and test on a copy.

The short rule: if the flag bothers you, stay on Game.Earn; if it does not, anything goes, as long as you exported first. If the tab is the appeal, our best browser games of 2026 has more free picks that need no download, the casual games for busy players list covers games you can leave for a week, and the free games for a low-end PC list covers the same idea outside the browser.

FAQ

Does cheating in Cookie Clicker ruin your save?

Not by itself. Seven of our nine commands never set the flag, and none of the nine broke a save. What ruins saves are values that are not normal numbers (NaN, text) and the Wipe button, so export the save before you type anything.

Can you remove the Cheated cookies taste awful achievement?

Yes, on the web version: set Game.cookiesEarned=Game.cookies, then run Game.RemoveAchiev('Cheated cookies taste awful'). Reversing the order brings the achievement back within seconds, because the bank is still higher than earned.

Does Open Sesame work on Steam?

Not through the bakery name. Running it from a console you have unlocked with DEV=1 should work, since the function is the same, but we could not confirm that and Steam achievements stay off while DEV is on.

Is the flag worth avoiding?

Only for the sake of a clean record. It never changes your milk or achievement total. It matters on Steam, where a community report links it to achievement syncing problems.

Sources

  1. Orteil / Dashnet. Cookie Clicker game code (main.js), version 2.058, last modified 21 October 2026
  2. Cookie Clicker Wiki. Open Sesame. Wiki.gg
  3. Chrome for Developers. Open Chrome DevTools
  4. Orteil. Cookie Clicker Steam Workshop (copy of the mods folder ReadMe.txt). Dashnet
  5. GamePretty. Cookie Clicker: How to Enable Dev Mode & Console on Steam
  6. Gameplay.tips. Cookie Clicker: Enabling Dev Tools & Console (Cheats)
  7. Steam Community. Cookie Clicker discussion: achievements and mods (reply of 14 November 2024)
  8. Steam Community. Cookie Clicker discussion: achievements not syncing
  9. 3zebras. Cookie Clicker Cheat Codes (31 July 2026)
Michael R.
Michael R.

I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.