Skip to main content
Night Mode — also called YOLO Mode — lets CC Commander run an autonomous build session while you sleep. You answer 10 setup questions before you go, and CC Commander dispatches Claude with Opus at maximum reasoning, a hard budget cap, and a self-testing loop. The goal is to wake up to shipped code.
YOLO Mode uses --dangerously-skip-permissions to allow Claude to act without confirmation prompts. Review all commits and generated code before deploying to production. Hooks such as auto-checkpoint and careful-guard act as safety nets but will not catch every mistake.

​
How to launch

Inside any Claude Code session:

​
The 10-question setup flow

Before starting the autonomous build, CC Commander walks you through 10 questions to produce a precise specification:
  1. What are we building?
  2. Who is this for?
  3. What does success look like?
  4. What is the tech stack?
  5. Are there any constraints?
  6. What are the must-have features?
  7. What are the nice-to-have features?
  8. Is there a deadline?
  9. What is the budget cap?
  10. Anything else Claude should know?
Your answers become the task specification that Claude works from throughout the session.

​
Default configuration

Once you confirm the setup, CC Commander shows you the full configuration before starting:

​
Stopping a running build

To stop the YOLO loop before it reaches the budget cap or the max-turns limit, create the stop file:
CC Commander checks for this file between cycles. The build halts at the next checkpoint, preserving all work completed so far. Delete the file before starting a new YOLO run.
You can also switch to the Claude tab in split mode (Ctrl+A n) and press Ctrl+C for an immediate stop, but this skips the graceful checkpoint. The stop file is the safer option for overnight runs.

​
Best practices

1

Write a clear task description

The more specific your answer to “What are we building?”, the better Claude can stay on track. Include the feature name, user-facing behavior, and any API or data contract constraints.
2

Define acceptance criteria

Answer the success criteria question with concrete, testable conditions — for example, “The checkout flow completes without errors and the Stripe test webhook fires.” Claude uses these criteria to decide when a phase is done.
3

Set a realistic budget

The default 10budgethandlesmostfeature−sizedbuilds.ForafullSaaSscaffoldoracomplexintegration,considerraisingitto10 budget handles most feature-sized builds. For a full SaaS scaffold or a complex integration, consider raising it to 15–$20 in the settings.
4

Review commits before deploying

Night Mode commits at every checkpoint. When you wake up, review the git log and diff before merging or deploying. git log --oneline gives a quick summary of what was built.
Run /ccc:xray on your project before starting a Night Mode build. The health score tells you which dimensions are weakest, and you can include “improve test coverage” or “add CI pipeline” in your task description so Night Mode addresses them automatically.