Orchestrator
Claude Code running while I sleepRunning nightlyI built a system to run Claude Code autonomously overnight. Second Max plan. Zero human intervention. Wake up to working code.
- 24/7 development cycle. Day: human-in-the-loop architecture and debugging. Night: Orchestrator clears the task queue autonomously.
- Autonomous task management. Reads task files, spawns Claude instances, manages state, handles errors. Runs until the list is empty or morning arrives.
- Two Max plans consumed weekly. Primary plan for day work. Second plan dedicated to orchestrator. Maxing out Claude's limits 24/7.
- Wake up to working features. Go to sleep with a task list. Wake up to commits, deployed features, and a cleared queue.
- Input
- Task files with goals & context
- Process
- Autonomous Claude execution
- Output
- Commits, deploys, closed tasks
How it works. Orchestrator is a Node.js daemon that interfaces with Claude Code's CLI. It reads task definitions, spawns isolated Claude sessions, monitors progress, and handles the full dev cycle: research, implementation, testing, commits.