-
Notifications
You must be signed in to change notification settings - Fork 18
Quick Start
Get up and running with Claude Autopilot in under 5 minutes! This guide will walk you through setting up your first "set it and forget it" automated Claude Code workflow.
Work smarter, not harder. Claude Autopilot is designed to let you:
- ✅ Queue up tasks Friday evening, enjoy your weekend, return Monday to completed work
- ✅ Start a large refactoring before dinner, come back to a transformed codebase
- ✅ Begin code generation while kids are awake, finish playing with everything done
- ✅ Sleep peacefully while Claude Autopilot handles hundreds of tasks automatically
Ensure you have:
- ✅ VS Code 1.74.0 or later
- ✅ Claude Code CLI installed and accessible
- ✅ Python 3.8 or later
- ✅ Claude Autopilot extension installed
Need help with installation? See the Installation Guide.
- Open VS Code
- Open a folder/workspace where you want to use Claude Autopilot
- Ensure you have some files to work with (code files, documents, etc.)
- Press
Cmd/Ctrl + Shift + Pto open Command Palette - Type "Claude: Start Claude Autopilot"
- Press Enter
- Look for the Claude Autopilot icon in the VS Code sidebar
- Click to open the Claude Autopilot panel
When Claude Autopilot starts, it automatically checks your dependencies:
- 🟢 Green checkmarks: Everything is ready
- 🟡 Yellow warnings: Minor issues (often safe to ignore)
- 🔴 Red errors: Must be fixed before proceeding
If you see red errors, check the Troubleshooting Guide.
- In the Claude Autopilot panel, click "Add Message"
- Enter a simple task, for example:
Please analyze the current directory structure and create a brief summary of the main files and their purposes. - Click "Add to Queue"
- Click the "Start Processing" button
- Watch as Claude Autopilot:
- Sends your message to Claude Code
- Processes the response
- Shows results in real-time
- Real-time Output: Watch the processing in the main panel
- History Tab: Click "History" to see completed tasks
- Queue Tab: Monitor pending and completed messages
Perfect for weekend productivity:
Message 1-50: "Convert each .js file in /src/components/ to TypeScript with proper interfaces"
Message 51-75: "Add comprehensive JSDoc comments to all converted TypeScript files"
Message 76-100: "Generate unit tests for each converted component using Jest"
Result: Start your weekend with a JavaScript codebase, return Monday to a fully-typed, documented, and tested TypeScript project.
Great for family time:
Message 1-25: "Refactor all class components in /src/ to functional components with hooks"
Message 26-50: "Add error boundaries to all converted functional components"
Message 51-60: "Generate comprehensive PropTypes documentation for each component"
Result: Start cooking dinner with legacy code, eat with family, return to modern React codebase.
Ideal for large-scale generation:
Message 1-30: "Generate CRUD operations for each model in /models/ directory"
Message 31-60: "Create corresponding API endpoints for each CRUD operation"
Message 61-90: "Generate comprehensive integration tests for all API endpoints"
Message 91-100: "Create detailed API documentation with examples for each endpoint"
Result: Go to sleep with basic models, wake up to a complete API with tests and documentation.
- Status Bar: Shows current processing status
- Queue Section: Lists pending and processing messages
- Output Section: Displays real-time results
- Controls: Start/stop processing, add messages
- ➕ Add: Add new messages
- ✏️ Edit: Modify existing messages
- 🗑️ Delete: Remove messages
- 📋 Duplicate: Copy messages
-
↕️ Reorder: Change message order
- 🟢 Ready: System ready for processing
- 🟡 Processing: Currently working on tasks
- 🔴 Error: Issue requires attention
- ⏸️ Paused: Processing paused (manual or auto-resume)
- Begin with simple, single-task messages
- Gradually increase complexity as you learn
✅ Good: "Add error handling to the login function in src/auth.js"
❌ Vague: "Fix the authentication stuff"
Instead of:
"Refactor the entire application to use TypeScript and add comprehensive testing"
Try:
Message 1: "Convert src/utils/helpers.js to TypeScript"
Message 2: "Add type definitions for the main User interface"
Message 3: "Create Jest tests for the helpers module"
- Keep an eye on the processing status
- Review outputs before adding dependent tasks
- Use the history feature to track what's been completed
Start with these essential settings:
{
"claudeLoop.session.skipPermissions": true,
"claudeLoop.sleepPrevention.enabled": true,
"claudeLoop.queue.autoMaintenance": true,
"claudeLoop.developmentMode": false
}Solution: Ensure Claude Code is installed and in your PATH
claude --version # Should show version numberSolution: Check the dependency status indicators
Solution: Wait a moment - Claude Code responses can take time
Solution: Enable claudeLoop.session.skipPermissions in settings
Now that you have Claude Autopilot running:
- Explore Configuration: Customize settings in Configuration Guide
- Learn Advanced Features: Check out Use Cases for inspiration
- Optimize Your Workflow: Read Best Practices
- Join the Community: Visit GitHub Discussions
| Action | Command |
|---|---|
| Start Claude Autopilot | Claude: Start Claude Autopilot |
| Stop Claude Autopilot | Claude: Stop Claude Autopilot |
| Add Message | Claude: Add Message to Queue |
| Open Settings |
Cmd/Ctrl + , → Search "Claude Autopilot" |
If you run into issues:
- Check the status indicators in the Claude Autopilot panel
- Review the Troubleshooting Guide
- Enable debug logging and check for error messages
- Ask for help in GitHub Discussions
Congratulations! You've completed your first Claude Autopilot workflow. You're now ready to automate your Claude Code tasks efficiently.
Quick start guide last updated: July 2025