Worker Quick Start Guide
Get started with AnyTask workers in 5 minutes.Prerequisites
Install AnyTask CLI
Install Claude Code CLI
Setup
1. Configure Authentication
2. Initialize Workspace
3. Create Test Tasks
Get Your Agent ID
- Visit https://anyt.dev/home/agents
- Create a new agent if needed
- Copy your agent identifier (e.g.,
agent-xxx)
Running the Worker
Start Worker with Built-in Workflows
The CLI includes built-in workflows for common development tasks:Common Options
--workspace, -w PATH: Workspace directory (default: current)--workflow TEXT: Specific workflow to run (exclusive)--workflows-dir PATH: Custom workflows directory (default:.anyt/workflows)--poll-interval, -i SECONDS: Polling interval (default: 5)--max-backoff SECONDS: Maximum backoff interval (default: 60)--agent-id, -a TEXT: Agent identifier (required)--project-id, -p INT: Project ID to scope task suggestions
Built-in Workflows
The CLI includes four production-ready workflows: 1. Local Development (local_dev)
- Triggers: Any task updated to
todostatus - Best for: Quick iterations on current branch
- Timeout: 30 minutes
- Actions: Analyze task, implement changes, lint, test, commit, mark done
feature_development)
- Triggers: Tasks with
featurelabel - Best for: Full feature implementation with branch management
- Timeout: 60 minutes
- Actions: Create branch, analyze, implement, test, commit, push, mark done
general_task)
- Triggers: Any task created with
todostatus - Best for: Catch-all automation for general tasks
- Timeout: 60 minutes
- Actions: Checkout main, analyze, implement, test, commit, mark done
dry_run)
- Triggers: Any task created with
todostatus - Best for: Testing worker setup without making code changes
- Timeout: 30 minutes
- Actions: Analyze task (read-only), post analysis, mark done (no code changes)
Example Workflow
1. Start the Worker
2. Worker Output
3. Verify Results
View Available Workflows
List all available workflows:Validate Custom Workflows
Validate a workflow file before using it:Monitoring Worker Activity
Check Task Progress
Monitor Worker
The worker runs in the foreground and outputs status to stdout. You can monitor it in real-time.Stopping the Worker
PressCtrl+C to gracefully stop:
Common Issues
”ANYT_API_KEY environment variable not set"
"No agent-id provided"
"No tasks available"
"Not in a workspace directory”
Advanced Usage
Run as Background Service
For production use, run as a systemd service:Filter Tasks by Project
Use the--project-id option:
Use with tmux
Multiple Workers
Run multiple workers for different workflows:Next Steps
- Custom Workflows - Create your own workflows
- Production Deployment - Deploy workers in production
- Authentication - Configure secure authentication
- Complete Guide - Comprehensive documentation
Support
- Full documentation: See Worker System Overview
- CLI reference: See CLI Complete Reference
- Questions: Contact [email protected]