What Citron cheats actually are and why you'd use them
Citron is a lightweight hypervisor and container runtime designed for testing and development. When people talk about "adding cheats" to Citron, they mean enabling debug flags, environment variables, and undocumented parameters that change how the hypervisor behaves — usually to skip validation steps, inject test data, or access features that aren't exposed in the normal interface.
These aren't cheat codes in the video game sense. They're development tools built into Citron that let you bypass normal restrictions for testing purposes. You might use them to test how your container behaves under resource constraints that would normally be enforced, to skip network initialization during rapid iteration, or to enable verbose logging that shows exactly what Citron is doing under the hood.
The catch: cheat flags are unsupported in production. They exist for development and testing only. Using them in a live environment means you lose the safety guarantees Citron normally provides, and you won't get help from maintainers if something breaks.
Key Takeaways
- Citron cheat flags are passed as environment variables or command-line arguments when you start the hypervisor, not added to a configuration file.
- The most common cheats disable resource limits, skip network setup, and enable debug logging — each one changes what Citron validates before running a container.
- You can find the full list of available flags by running citron --help-debug or checking the Citron source code repository under the flags package.
- Cheat flags only work during development and testing; they are not supported for production workloads and may cause unpredictable behavior.
Passing cheat flags as environment variables
The simplest way to enable Citron cheats is to set environment variables before you start the hypervisor. Citron reads variables prefixed with CITRON_ at startup and applies them as flags.
For example, to disable memory limit enforcement and enable debug output, you would run:
export CITRON_SKIP_MEMORY_LIMITS=1 export CITRON_DEBUG=1 citron start
Each variable corresponds to a specific behavior change. CITRON_SKIP_MEMORY_LIMITS tells Citron not to enforce the memory ceiling you set for a container — useful for testing what happens when a container tries to allocate more than it should. CITRON_DEBUG=1 writes detailed logs to stderr showing every step Citron takes, which helps you understand why a container failed to start or why networking isn't working.
Environment variables persist for the entire session, so if you set them in your shell, every Citron instance you start will use those flags until you unset them or close the terminal.
Passing cheat flags as command-line arguments
You can also pass flags directly to the citron command when you start it. This approach is useful when you want to enable cheats for a single run without affecting other instances.
The syntax is citron --flag-name=value or citron --flag-name for boolean flags:
citron start --skip-network-init --debug --cpu-limit-disabled
--skip-network-init tells Citron not to wait for the network interface to be ready before starting your container — this speeds up iteration when you're testing code that doesn't need network access. --cpu-limit-disabled removes CPU throttling, so your container can use all available cores regardless of what you specified in its configuration.
Command-line flags only apply to that single invocation of Citron. Once the process exits, the flags are gone, and the next time you run Citron it will use default behavior unless you pass the flags again.
Common cheat flags and what they do
Citron includes dozens of debug flags, but a few are used far more often than others. Here are the ones you'll encounter in most development workflows:
| Flag | What it does | When to use it |
|---|---|---|
| CITRON_DEBUG=1 | Writes detailed logs to stderr showing every step Citron takes | When a container fails to start and you need to see exactly where it breaks |
| CITRON_SKIP_MEMORY_LIMITS=1 | Disables memory ceiling enforcement | Testing how your code behaves when it tries to allocate more memory than allowed |
| CITRON_SKIP_CPU_LIMITS=1 | Removes CPU throttling | When you want to measure raw performance without Citron's resource constraints |
| CITRON_SKIP_NETWORK_INIT=1 | Skips waiting for network interface to be ready | Speeding up container startup when testing code that doesn't need the network |
| CITRON_INSECURE_MODE=1 | Disables security checks and allows privileged operations | Testing code that needs root access, but only in isolated development environments |
Each flag removes a safety check or validation step. The more flags you enable, the less Citron protects you from misconfiguration or resource exhaustion. That's why they're only meant for development.
Finding the complete list of available cheats
Citron's full set of debug flags changes between versions, so the best way to see what's available is to check the source code or the built-in help output.
Run citron --help-debug to print all available flags with short descriptions. This command works on any Citron installation and shows only the flags available in your version.
If you want more detail — what each flag actually changes in the code, or which other flags it interacts with — check the Citron repository on GitHub. Look in the flags package under the version you're running. Each flag is documented with comments explaining its purpose and any side effects.
The Citron documentation site also maintains a page listing common debug flags and their use cases, though it may lag behind the latest version. Use it as a starting point, but verify against --help-debug before relying on a flag in production code.
Why cheat flags break in production and how to avoid that mistake
Cheat flags work by removing validation and safety checks. In a development environment where you control all the inputs, that's fine — you know your container won't actually exhaust memory, or you're testing exactly what happens if it does. In production, where you don't control what users do, those removed checks become serious problems.
A container running with CITRON_SKIP_MEMORY_LIMITS=1 can allocate memory until the host runs out, then crash or become unresponsive. A container with CITRON_INSECURE_MODE=1 can access files and devices it shouldn't. These aren't bugs — they're the intended behavior of the cheat flags. They're designed to let you test edge cases, not to run safely at scale.
The safest approach is to use cheat flags only in isolated development environments, never in staging or production. If you find yourself tempted to use a cheat flag in production because it solves a problem, that's a sign you need to file a bug with the Citron maintainers or redesign your setup. The flag exists to help you test, not to work around a real limitation.
Frequently Asked Questions
Can I use cheat flags in a Dockerfile or container configuration?
No. Cheat flags are passed to the Citron hypervisor itself, not to the container. They must be set as environment variables or command-line arguments when you start Citron, before the container even begins. You cannot embed them in a Dockerfile or in a container's configuration file.
What happens if I enable conflicting cheat flags at the same time?
Citron will usually apply both flags, which can produce unexpected behavior. For example, enabling both CITRON_SKIP_MEMORY_LIMITS and CITRON_DEBUG will disable memory enforcement and log every step — the logs will show that memory limits are not being checked. If two flags directly contradict each other, Citron will either apply the last one you specified or raise an error. Check the debug output to see what actually happened.
Do cheat flags slow down Citron?
Debug logging (CITRON_DEBUG=1) does slow things down noticeably because Citron writes detailed output for every operation. Flags that skip validation or limits usually make Citron faster because it has less work to do. If performance matters for your test, disable debug logging and enable only the specific flags you need.
Will cheat flags work if I upgrade Citron?
Maybe. Citron's maintainers try to keep debug flags stable, but they're not part of the public API, so they can change or disappear between versions. After upgrading, run citron --help-debug again to see if your flags still exist. If a flag you relied on is gone, check the release notes to see what replaced it.