Skip to main content

Advanced Configuration

Advanced configuration topics for AnyTask CLI.
For basic setup, see the Quick Start Guide. This page covers advanced topics only.

Environment Variables

VariableDescriptionDefault
ANYT_API_KEYAgent API key (required)None
Example:
# Use different API key per command
ANYT_API_KEY=anyt_agent_xxx anyt task list

Configuration Files

Workspace config (.anyt/anyt.json):
{
  "workspace_id": 123,
  "workspace_name": "Development",
  "workspace_identifier": "DEV",
  "api_url": "https://api.anyt.dev",
  "current_project_id": 456
}
Active task (.anyt/active_task.json):
{
  "identifier": "DEV-42",
  "title": "Implement OAuth callback",
  "picked_at": "2025-11-06T10:30:00Z"
}
API keys are NEVER stored in config files. Use environment variables only.

Workspace Switching

Switch between workspaces:
# Interactive workspace switch
anyt workspace switch

# View current workspace
anyt workspace current
The interactive flow will:
  1. Show all accessible workspaces
  2. Let you select a new workspace
  3. Show all projects in that workspace
  4. Let you select a project
  5. Update .anyt/anyt.json

Multi-Project Setup

Each directory can have its own workspace:
cd /path/to/project1
anyt init  # Select workspace A

cd /path/to/project2
anyt init  # Select workspace B

Non-Interactive Init (CI/CD)

For automation and CI/CD:
# Auto-select first workspace/project
anyt init -y

# Specify explicitly
anyt init --workspace-id 123 --project-id 456

# With custom identifier
anyt init -y --workspace-id 123 --identifier DEV
Options:
  • -y, --non-interactive: Skip interactive prompts
  • --workspace-id <id>: Workspace ID
  • --project-id <id>: Project ID
  • --identifier <prefix>: Task identifier prefix (e.g., DEV, PROJ)
  • --dir <path>: Directory to initialize

JSON Output

All commands support --json for machine-readable output:
anyt task list --json
anyt board --json
Output format:
{"success": true, "data": {...}}
{"success": false, "error": "ErrorType", "message": "..."}

See Also