Andy
1d64615211
* auto-claude: subtask-1-1 - Add queue capacity check to handleStatusChange When a task status is changed to 'in_progress' via handleStatusChange (e.g., from column header buttons or context menus), enforce the maxParallelTasks limit by redirecting to 'queue' if capacity is full. Also auto-process the queue when a task leaves in_progress. This mirrors the existing logic in handleDragEnd. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * auto-claude: subtask-1-2 - Add queue capacity check before startTask() in TaskCard, TaskDetailModal, WorkspaceMessages Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: extract shared queue capacity logic and fix stuck task restart regression - Extract `startTaskOrQueue()`, `isQueueAtCapacity()`, and `DEFAULT_MAX_PARALLEL_TASKS` into task-store.ts to eliminate identical queue capacity logic duplicated across 4 files (DRY violation) - Fix stuck task restart regression: exclude the current task from the in_progress count so restarting a stuck task doesn't incorrectly queue it - Fix inconsistent default: use ?? 3 everywhere (was ?? 1 in 3 new files vs ?? 3 in KanbanBoard, causing different behavior per UI element) - Fix unawaited persistTaskStatus in TaskCard (was fire-and-forget in a sync handler) and TaskDetailModal (missing await in async handler) - Add explanatory comment in KanbanBoard handleStatusChange about why isAutoPromotionInProgress guard is not needed (only user interactions) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: remove duplicate processQueue() call in handleDragEnd handleStatusChange already calls processQueue() when a task leaves in_progress, so the second call in handleDragEnd was redundant. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: log queue failures, remove dead bypass code, fix comment - startTaskOrQueue now logs an error when persistTaskStatus fails instead of silently discarding the result - Remove dead isAutoPromotionInProgress bypass from drag handler since handleStatusChange enforces capacity independently (the bypass was negated by the second check) - Fix inaccurate comment: handleStatusChange is called from both the dropdown menu and the drag handler, not just the dropdown Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: return queue failure result from startTaskOrQueue and remove duplicate processQueue startTaskOrQueue now returns a result object so callers can surface errors to the user (toast in TaskDetailModal, console.error in WorkspaceMessages). Removed explicit processQueue() from handleStatusChange since the useEffect task status change listener already handles queue auto-promotion. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: correct i18n key path and surface startTaskOrQueue failures to users Fix wrong i18n key path (tasks:errors → tasks:wizard.errors) so the toast shows the translated message instead of a raw key. Add toast feedback in TaskCard on start failure. Add inline error display in WorkspaceMessages when Proceed to Coding fails. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: show user feedback when task is queued instead of started All three startTaskOrQueue callers (TaskCard, TaskDetailModal, WorkspaceMessages) now notify the user when a task is redirected to the queue due to the parallel task limit. Uses existing i18n keys (tasks:queue.movedToQueue). Also clarifies startTaskOrQueue JSDoc regarding fire-and-forget semantics of the 'started' action. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: use i18n and neutral styling for queued notice in WorkspaceMessages Replace hardcoded English string with t('tasks:queue.movedToQueue') and use a separate notice state with text-muted-foreground styling instead of reusing the destructive error state. Also add missing status.queue key to French translations. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Auto Claude
Autonomous multi-agent coding framework that plans, builds, and validates software for you.
Download
Stable Release
| Platform | Download |
|---|---|
| Windows | Auto-Claude-2.7.5-win32-x64.exe |
| macOS (Apple Silicon) | Auto-Claude-2.7.5-darwin-arm64.dmg |
| macOS (Intel) | Auto-Claude-2.7.5-darwin-x64.dmg |
| Linux | Auto-Claude-2.7.5-linux-x86_64.AppImage |
| Linux (Debian) | Auto-Claude-2.7.5-linux-amd64.deb |
| Linux (Flatpak) | Auto-Claude-2.7.5-linux-x86_64.flatpak |
Beta Release
⚠️ Beta releases may contain bugs and breaking changes. View all releases
| Platform | Download |
|---|---|
| Windows | Auto-Claude-2.7.6-beta.3-win32-x64.exe |
| macOS (Apple Silicon) | Auto-Claude-2.7.6-beta.3-darwin-arm64.dmg |
| macOS (Intel) | Auto-Claude-2.7.6-beta.3-darwin-x64.dmg |
| Linux | Auto-Claude-2.7.6-beta.3-linux-x86_64.AppImage |
| Linux (Debian) | Auto-Claude-2.7.6-beta.3-linux-amd64.deb |
| Linux (Flatpak) | Auto-Claude-2.7.6-beta.3-linux-x86_64.flatpak |
All releases include SHA256 checksums and VirusTotal scan results for security verification.
Requirements
- Claude Pro/Max subscription - Get one here
- Claude Code CLI -
npm install -g @anthropic-ai/claude-code - Git repository - Your project must be initialized as a git repo
Quick Start
- Download and install the app for your platform
- Open your project - Select a git repository folder
- Connect Claude - The app will guide you through OAuth setup
- Create a task - Describe what you want to build
- Watch it work - Agents plan, code, and validate autonomously
Features
| Feature | Description |
|---|---|
| Autonomous Tasks | Describe your goal; agents handle planning, implementation, and validation |
| Parallel Execution | Run multiple builds simultaneously with up to 12 agent terminals |
| Isolated Workspaces | All changes happen in git worktrees - your main branch stays safe |
| Self-Validating QA | Built-in quality assurance loop catches issues before you review |
| AI-Powered Merge | Automatic conflict resolution when integrating back to main |
| Memory Layer | Agents retain insights across sessions for smarter builds |
| GitHub/GitLab Integration | Import issues, investigate with AI, create merge requests |
| Linear Integration | Sync tasks with Linear for team progress tracking |
| Cross-Platform | Native desktop apps for Windows, macOS, and Linux |
| Auto-Updates | App updates automatically when new versions are released |
Interface
Kanban Board
Visual task management from planning through completion. Create tasks and monitor agent progress in real-time.
Agent Terminals
AI-powered terminals with one-click task context injection. Spawn multiple agents for parallel work.
Roadmap
AI-assisted feature planning with competitor analysis and audience targeting.
Additional Features
- Insights - Chat interface for exploring your codebase
- Ideation - Discover improvements, performance issues, and vulnerabilities
- Changelog - Generate release notes from completed tasks
Project Structure
Auto-Claude/
├── apps/
│ ├── backend/ # Python agents, specs, QA pipeline
│ └── frontend/ # Electron desktop application
├── guides/ # Additional documentation
├── tests/ # Test suite
└── scripts/ # Build utilities
CLI Usage
For headless operation, CI/CD integration, or terminal-only workflows:
cd apps/backend
# Create a spec interactively
python spec_runner.py --interactive
# Run autonomous build
python run.py --spec 001
# Review and merge
python run.py --spec 001 --review
python run.py --spec 001 --merge
See guides/CLI-USAGE.md for complete CLI documentation.
Development
Want to build from source or contribute? See CONTRIBUTING.md for complete development setup instructions.
For Linux-specific builds (Flatpak, AppImage), see guides/linux.md.
Security
Auto Claude uses a three-layer security model:
- OS Sandbox - Bash commands run in isolation
- Filesystem Restrictions - Operations limited to project directory
- Dynamic Command Allowlist - Only approved commands based on detected project stack
All releases are:
- Scanned with VirusTotal before publishing
- Include SHA256 checksums for verification
- Code-signed where applicable (macOS)
Available Scripts
| Command | Description |
|---|---|
npm run install:all |
Install backend and frontend dependencies |
npm start |
Build and run the desktop app |
npm run dev |
Run in development mode with hot reload |
npm run package |
Package for current platform |
npm run package:mac |
Package for macOS |
npm run package:win |
Package for Windows |
npm run package:linux |
Package for Linux |
npm run package:flatpak |
Package as Flatpak (see guides/linux.md) |
npm run lint |
Run linter |
npm test |
Run frontend tests |
npm run test:backend |
Run backend tests |
Contributing
We welcome contributions! Please read CONTRIBUTING.md for:
- Development setup instructions
- Code style guidelines
- Testing requirements
- Pull request process
Community
- Discord - Join our community
- Issues - Report bugs or request features
- Discussions - Ask questions
License
AGPL-3.0 - GNU Affero General Public License v3.0
Auto Claude is free to use. If you modify and distribute it, or run it as a service, your code must also be open source under AGPL-3.0.
Commercial licensing available for closed-source use cases.
