claude-task-master 0.1.4__tar.gz → 0.1.5__tar.gz

{claude_task_master-0.1.4 → claude_task_master-0.1.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: claude-task-master
-Version: 0.1.4
+Version: 0.1.5
 Summary: Autonomous task orchestration system that keeps Claude working until a goal is achieved
 Author: Claude Task Master Team
 License-Expression: MIT
@@ -13,13 +13,11 @@ Keywords: claude,agent,autonomous,task,orchestration,ai,automation
 Classifier: Development Status :: 3 - Alpha
 Classifier: Intended Audience :: Developers
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.10
-Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Operating System :: OS Independent
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
-Requires-Python: >=3.10
+Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 Requires-Dist: claude-agent-sdk>=0.1.0
 Requires-Dist: typer>=0.12.0
@@ -39,6 +37,7 @@ Requires-Dist: pytest>=8.0.0; extra == "dev"
 Requires-Dist: pytest-cov>=4.1.0; extra == "dev"
 Requires-Dist: pytest-asyncio>=0.23.0; extra == "dev"
 Requires-Dist: pytest-timeout>=2.4.0; extra == "dev"
+Requires-Dist: hypothesis>=6.100.0; extra == "dev"
 Requires-Dist: ruff>=0.3.0; extra == "dev"
 Requires-Dist: mypy>=1.9.0; extra == "dev"
 Provides-Extra: all
@@ -159,9 +158,19 @@ Claude Task Master uses the Claude Agent SDK to autonomously work on complex tas
 4. **Handle CI** - Wait for checks, fix failures, address review comments
 5. **Merge** - Auto-merge when approved (configurable)
 6. **Verify** - Confirm all success criteria are met
+7. **Adapt** - Accept dynamic plan updates via mailbox while working
 
 **Core Philosophy**: Claude is smart enough to do the work AND verify it. Task Master keeps the loop going and persists state between sessions.
 
+### Key Features
+
+- **Autonomous Execution** - Runs until goal is achieved or needs human input
+- **PR-Based Workflow** - All work flows through pull requests for review
+- **CI Integration** - Handles CI failures and review comments together
+- **Mailbox System** - Receive dynamic plan updates while working (via REST API, MCP, or CLI)
+- **Multi-Instance Coordination** - Multiple instances can communicate via mailbox
+- **State Persistence** - Survives interruptions, resumes where it left off
+
 ## Workflow
 
 ```
@@ -346,6 +355,7 @@ Complete documentation for all features and deployment options:
 | **[Authentication](./docs/authentication.md)** | Password-based authentication for REST API, MCP server, and webhooks |
 | **[REST API Reference](./docs/api-reference.md)** | Complete REST API endpoint documentation with examples |
 | **[Webhooks](./docs/webhooks.md)** | Webhook events, payload formats, HMAC signature verification, and integration examples |
+| **[Mailbox System](./docs/mailbox.md)** | Inter-instance communication, dynamic plan updates, and multi-instance coordination |
 
 ## Usage
 
@@ -355,6 +365,7 @@ Complete documentation for all features and deployment options:
 |---------|-------------|
 | `claudetm start "goal"` | Start a new task |
 | `claudetm resume` | Resume a paused task |
+| `claudetm resume "message"` | Update plan with message, then resume |
 | `claudetm status` | Show current status |
 | `claudetm plan` | View task list |
 | `claudetm progress` | View progress summary |
@@ -364,6 +375,9 @@ Complete documentation for all features and deployment options:
 | `claudetm comments` | Show review comments |
 | `claudetm clean` | Clean up task state |
 | `claudetm doctor` | Verify system setup |
+| `claudetm mailbox` | Show mailbox status |
+| `claudetm mailbox send "msg"` | Send message to mailbox |
+| `claudetm mailbox clear` | Clear pending messages |
 
 ### Start Options
 
@@ -392,6 +406,14 @@ claudetm start "Fix bug in parser" --max-sessions 5
 
 # Monitor progress
 watch -n 5 'claudetm status'
+
+# Resume with a change request (updates plan first)
+claudetm resume "Also add input validation to the forms"
+
+# Send message to mailbox via REST API
+curl -X POST http://localhost:8000/mailbox/send \
+  -H "Content-Type: application/json" \
+  -d '{"content": "Prioritize security fixes", "priority": 2}'
 ```
 
 ## Examples & Use Cases
@@ -428,6 +450,202 @@ claudetm start "Add API documentation and examples"
 7. **[CI/CD Integration](./examples/07-cicd.md)** - GitHub Actions workflows
 8. **[Advanced Workflows](./examples/08-advanced-workflows.md)** - Complex scenarios
 
+## AI Developer Workflow
+
+Claude Task Master includes built-in support for repository cloning and setup, enabling an AI-driven development environment. This is particularly useful for:
+
+- **AI Server Deployments** - Deploy Claude Task Master to servers and have it autonomously clone and setup projects
+- **Development Environment Setup** - Automatically configure repositories for local development
+- **Multi-Project Coordination** - Manage multiple projects simultaneously, each in isolated directories
+- **Continuous AI Development** - Receive work requests, setup projects, implement tasks, all autonomously
+
+### Repo Setup Workflow
+
+The repo setup workflow consists of three phases:
+
+1. **Clone** - Clone a git repository to `~/workspace/claude-task-master/{project-name}`
+2. **Setup** - Automatically install dependencies, create virtual environments, run setup scripts
+3. **Plan or Work** - Either analyze the project and create a plan, or immediately start working on tasks
+
+### Clone a Repository
+
+**Via REST API:**
+```bash
+curl -X POST http://localhost:8000/repo/clone \
+  -H "Content-Type: application/json" \
+  -d '{
+    "repo_url": "https://github.com/example/my-project.git",
+    "project_name": "my-project"
+  }'
+```
+
+**Via MCP Tools (IDE Integration):**
+```
+Claude: Clone the repository https://github.com/example/my-project.git
+→ Uses clone_repo tool to clone to ~/workspace/claude-task-master/my-project
+```
+
+### Setup a Cloned Repository
+
+After cloning, setup installs dependencies and prepares the project for development:
+
+**Via REST API:**
+```bash
+curl -X POST http://localhost:8000/repo/setup \
+  -H "Content-Type: application/json" \
+  -d '{
+    "project_name": "my-project"
+  }'
+```
+
+**Via MCP Tools:**
+```
+Claude: Set up the project my-project for development
+→ Uses setup_repo tool to configure and prepare the repository
+```
+
+The setup phase:
+- Detects project type (Python, Node.js, Ruby, etc.)
+- Installs package manager if needed (uv, npm, pip, bundler, etc.)
+- Creates virtual environments (venv, node_modules, etc.)
+- Runs setup scripts if present (setup.sh, Makefile, scripts/setup-hooks.sh, etc.)
+- Installs dependencies from lock files (requirements.txt, package.json, Gemfile, etc.)
+
+### Plan a Repository (Analysis Only)
+
+Analyze a project and generate a task plan without executing work:
+
+**Via REST API:**
+```bash
+curl -X POST http://localhost:8000/repo/plan \
+  -H "Content-Type: application/json" \
+  -d '{
+    "project_name": "my-project",
+    "goal": "Add authentication to the application"
+  }'
+```
+
+**Via MCP Tools:**
+```
+Claude: Plan the task "Add authentication" for project my-project
+→ Uses plan_repo tool to analyze and generate a task plan
+```
+
+This phase creates a plan in `.claude-task-master/plan.md` without executing any tasks, allowing review before work begins.
+
+### Complete AI Developer Workflow Example
+
+A full end-to-end workflow:
+
+```bash
+# 1. Clone a repository
+curl -X POST http://localhost:8000/repo/clone \
+  -H "Content-Type: application/json" \
+  -d '{"repo_url": "https://github.com/example/myapp.git", "project_name": "myapp"}'
+
+# 2. Setup the project for development
+curl -X POST http://localhost:8000/repo/setup \
+  -H "Content-Type: application/json" \
+  -d '{"project_name": "myapp"}'
+
+# 3. Plan the work (optional - just analyze)
+curl -X POST http://localhost:8000/repo/plan \
+  -H "Content-Type: application/json" \
+  -d '{"project_name": "myapp", "goal": "Add user authentication with OAuth"}'
+
+# 4. Or start work directly with a goal
+curl -X POST http://localhost:8000/task/init \
+  -H "Content-Type: application/json" \
+  -d '{"project_dir": "~/workspace/claude-task-master/myapp", "goal": "Add user authentication with OAuth"}'
+```
+
+### Directory Structure
+
+When using the repo setup workflow, projects are organized as follows:
+
+```
+~/workspace/claude-task-master/
+├── my-project/
+│   ├── .git/
+│   ├── src/
+│   ├── .claude-task-master/      # State directory (auto-created by claudetm)
+│   │   ├── goal.txt
+│   │   ├── plan.md
+│   │   ├── state.json
+│   │   └── logs/
+│   └── ...
+├── another-project/
+│   └── ...
+```
+
+### Use Cases
+
+**1. Server-Based AI Development Platform**
+
+Deploy Claude Task Master to a server with git credentials and have it:
+- Clone repositories on demand
+- Setup development environments automatically
+- Execute work assignments from a job queue
+- Report results via webhooks
+
+```bash
+# Server startup
+docker run -d \
+  -p 8000:8000 \
+  -v ~/.claude:/root/.claude:ro \
+  -v ~/.gitconfig:/root/.gitconfig:ro \
+  -v ~/.config/gh:/root/.config/gh:ro \
+  -v ~/workspace:/root/workspace \
+  ghcr.io/developerz-ai/claude-task-master:latest
+
+# External system sends work
+curl http://ai-dev-server:8000/repo/clone -d '{"repo_url": "...", "project_name": "..."}'
+curl http://ai-dev-server:8000/repo/setup -d '{"project_name": "..."}'
+curl http://ai-dev-server:8000/task/init -d '{"project_dir": "...", "goal": "..."}'
+```
+
+**2. Local Development Workspace Management**
+
+Setup a local workspace where Claude helps manage multiple projects:
+
+```bash
+# Initialize workspace
+mkdir -p ~/workspace/claude-task-master
+cd ~/workspace/claude-task-master
+
+# Clone and setup multiple projects
+claudetm repo clone https://github.com/org/api-server api-server
+claudetm repo setup api-server
+
+claudetm repo clone https://github.com/org/web-client web-client
+claudetm repo setup web-client
+
+# Work on individual projects
+cd api-server
+claudetm start "Add rate limiting to API endpoints"
+
+cd ../web-client
+claudetm start "Implement dark mode toggle"
+```
+
+**3. Continuous Integration as AI Development**
+
+Integrate with CI/CD to have Claude automatically work on issues:
+
+```bash
+# GitHub Action or external trigger
+curl http://localhost:8000/repo/clone \
+  -d '{"repo_url": "'$GITHUB_REPOSITORY'", "project_name": "repo"}'
+
+curl http://localhost:8000/repo/setup \
+  -d '{"project_name": "repo"}'
+
+curl http://localhost:8000/task/init \
+  -d '{"project_dir": "~/workspace/claude-task-master/repo", "goal": "'$ISSUE_TITLE'"}'
+
+# Results reported via webhook callback
+```
+
 ## Troubleshooting
 
 ### Credentials & Setup
@@ -629,6 +847,7 @@ Each stage has specific handlers that determine when to transition to the next s
 ├── state.json            # Machine-readable state
 ├── progress.md           # Progress summary
 ├── context.md            # Accumulated learnings
+├── mailbox.json          # Pending messages for plan updates
 └── logs/
     └── run-{timestamp}.txt    # Full log (kept on success)
 ```

{claude_task_master-0.1.4 → claude_task_master-0.1.5}/README.md

@@ -113,9 +113,19 @@ Claude Task Master uses the Claude Agent SDK to autonomously work on complex tas
 4. **Handle CI** - Wait for checks, fix failures, address review comments
 5. **Merge** - Auto-merge when approved (configurable)
 6. **Verify** - Confirm all success criteria are met
+7. **Adapt** - Accept dynamic plan updates via mailbox while working
 
 **Core Philosophy**: Claude is smart enough to do the work AND verify it. Task Master keeps the loop going and persists state between sessions.
 
+### Key Features
+
+- **Autonomous Execution** - Runs until goal is achieved or needs human input
+- **PR-Based Workflow** - All work flows through pull requests for review
+- **CI Integration** - Handles CI failures and review comments together
+- **Mailbox System** - Receive dynamic plan updates while working (via REST API, MCP, or CLI)
+- **Multi-Instance Coordination** - Multiple instances can communicate via mailbox
+- **State Persistence** - Survives interruptions, resumes where it left off
+
 ## Workflow
 
 ```
@@ -300,6 +310,7 @@ Complete documentation for all features and deployment options:
 | **[Authentication](./docs/authentication.md)** | Password-based authentication for REST API, MCP server, and webhooks |
 | **[REST API Reference](./docs/api-reference.md)** | Complete REST API endpoint documentation with examples |
 | **[Webhooks](./docs/webhooks.md)** | Webhook events, payload formats, HMAC signature verification, and integration examples |
+| **[Mailbox System](./docs/mailbox.md)** | Inter-instance communication, dynamic plan updates, and multi-instance coordination |
 
 ## Usage
 
@@ -309,6 +320,7 @@ Complete documentation for all features and deployment options:
 |---------|-------------|
 | `claudetm start "goal"` | Start a new task |
 | `claudetm resume` | Resume a paused task |
+| `claudetm resume "message"` | Update plan with message, then resume |
 | `claudetm status` | Show current status |
 | `claudetm plan` | View task list |
 | `claudetm progress` | View progress summary |
@@ -318,6 +330,9 @@ Complete documentation for all features and deployment options:
 | `claudetm comments` | Show review comments |
 | `claudetm clean` | Clean up task state |
 | `claudetm doctor` | Verify system setup |
+| `claudetm mailbox` | Show mailbox status |
+| `claudetm mailbox send "msg"` | Send message to mailbox |
+| `claudetm mailbox clear` | Clear pending messages |
 
 ### Start Options
 
@@ -346,6 +361,14 @@ claudetm start "Fix bug in parser" --max-sessions 5
 
 # Monitor progress
 watch -n 5 'claudetm status'
+
+# Resume with a change request (updates plan first)
+claudetm resume "Also add input validation to the forms"
+
+# Send message to mailbox via REST API
+curl -X POST http://localhost:8000/mailbox/send \
+  -H "Content-Type: application/json" \
+  -d '{"content": "Prioritize security fixes", "priority": 2}'
 ```
 
 ## Examples & Use Cases
@@ -382,6 +405,202 @@ claudetm start "Add API documentation and examples"
 7. **[CI/CD Integration](./examples/07-cicd.md)** - GitHub Actions workflows
 8. **[Advanced Workflows](./examples/08-advanced-workflows.md)** - Complex scenarios
 
+## AI Developer Workflow
+
+Claude Task Master includes built-in support for repository cloning and setup, enabling an AI-driven development environment. This is particularly useful for:
+
+- **AI Server Deployments** - Deploy Claude Task Master to servers and have it autonomously clone and setup projects
+- **Development Environment Setup** - Automatically configure repositories for local development
+- **Multi-Project Coordination** - Manage multiple projects simultaneously, each in isolated directories
+- **Continuous AI Development** - Receive work requests, setup projects, implement tasks, all autonomously
+
+### Repo Setup Workflow
+
+The repo setup workflow consists of three phases:
+
+1. **Clone** - Clone a git repository to `~/workspace/claude-task-master/{project-name}`
+2. **Setup** - Automatically install dependencies, create virtual environments, run setup scripts
+3. **Plan or Work** - Either analyze the project and create a plan, or immediately start working on tasks
+
+### Clone a Repository
+
+**Via REST API:**
+```bash
+curl -X POST http://localhost:8000/repo/clone \
+  -H "Content-Type: application/json" \
+  -d '{
+    "repo_url": "https://github.com/example/my-project.git",
+    "project_name": "my-project"
+  }'
+```
+
+**Via MCP Tools (IDE Integration):**
+```
+Claude: Clone the repository https://github.com/example/my-project.git
+→ Uses clone_repo tool to clone to ~/workspace/claude-task-master/my-project
+```
+
+### Setup a Cloned Repository
+
+After cloning, setup installs dependencies and prepares the project for development:
+
+**Via REST API:**
+```bash
+curl -X POST http://localhost:8000/repo/setup \
+  -H "Content-Type: application/json" \
+  -d '{
+    "project_name": "my-project"
+  }'
+```
+
+**Via MCP Tools:**
+```
+Claude: Set up the project my-project for development
+→ Uses setup_repo tool to configure and prepare the repository
+```
+
+The setup phase:
+- Detects project type (Python, Node.js, Ruby, etc.)
+- Installs package manager if needed (uv, npm, pip, bundler, etc.)
+- Creates virtual environments (venv, node_modules, etc.)
+- Runs setup scripts if present (setup.sh, Makefile, scripts/setup-hooks.sh, etc.)
+- Installs dependencies from lock files (requirements.txt, package.json, Gemfile, etc.)
+
+### Plan a Repository (Analysis Only)
+
+Analyze a project and generate a task plan without executing work:
+
+**Via REST API:**
+```bash
+curl -X POST http://localhost:8000/repo/plan \
+  -H "Content-Type: application/json" \
+  -d '{
+    "project_name": "my-project",
+    "goal": "Add authentication to the application"
+  }'
+```
+
+**Via MCP Tools:**
+```
+Claude: Plan the task "Add authentication" for project my-project
+→ Uses plan_repo tool to analyze and generate a task plan
+```
+
+This phase creates a plan in `.claude-task-master/plan.md` without executing any tasks, allowing review before work begins.
+
+### Complete AI Developer Workflow Example
+
+A full end-to-end workflow:
+
+```bash
+# 1. Clone a repository
+curl -X POST http://localhost:8000/repo/clone \
+  -H "Content-Type: application/json" \
+  -d '{"repo_url": "https://github.com/example/myapp.git", "project_name": "myapp"}'
+
+# 2. Setup the project for development
+curl -X POST http://localhost:8000/repo/setup \
+  -H "Content-Type: application/json" \
+  -d '{"project_name": "myapp"}'
+
+# 3. Plan the work (optional - just analyze)
+curl -X POST http://localhost:8000/repo/plan \
+  -H "Content-Type: application/json" \
+  -d '{"project_name": "myapp", "goal": "Add user authentication with OAuth"}'
+
+# 4. Or start work directly with a goal
+curl -X POST http://localhost:8000/task/init \
+  -H "Content-Type: application/json" \
+  -d '{"project_dir": "~/workspace/claude-task-master/myapp", "goal": "Add user authentication with OAuth"}'
+```
+
+### Directory Structure
+
+When using the repo setup workflow, projects are organized as follows:
+
+```
+~/workspace/claude-task-master/
+├── my-project/
+│   ├── .git/
+│   ├── src/
+│   ├── .claude-task-master/      # State directory (auto-created by claudetm)
+│   │   ├── goal.txt
+│   │   ├── plan.md
+│   │   ├── state.json
+│   │   └── logs/
+│   └── ...
+├── another-project/
+│   └── ...
+```
+
+### Use Cases
+
+**1. Server-Based AI Development Platform**
+
+Deploy Claude Task Master to a server with git credentials and have it:
+- Clone repositories on demand
+- Setup development environments automatically
+- Execute work assignments from a job queue
+- Report results via webhooks
+
+```bash
+# Server startup
+docker run -d \
+  -p 8000:8000 \
+  -v ~/.claude:/root/.claude:ro \
+  -v ~/.gitconfig:/root/.gitconfig:ro \
+  -v ~/.config/gh:/root/.config/gh:ro \
+  -v ~/workspace:/root/workspace \
+  ghcr.io/developerz-ai/claude-task-master:latest
+
+# External system sends work
+curl http://ai-dev-server:8000/repo/clone -d '{"repo_url": "...", "project_name": "..."}'
+curl http://ai-dev-server:8000/repo/setup -d '{"project_name": "..."}'
+curl http://ai-dev-server:8000/task/init -d '{"project_dir": "...", "goal": "..."}'
+```
+
+**2. Local Development Workspace Management**
+
+Setup a local workspace where Claude helps manage multiple projects:
+
+```bash
+# Initialize workspace
+mkdir -p ~/workspace/claude-task-master
+cd ~/workspace/claude-task-master
+
+# Clone and setup multiple projects
+claudetm repo clone https://github.com/org/api-server api-server
+claudetm repo setup api-server
+
+claudetm repo clone https://github.com/org/web-client web-client
+claudetm repo setup web-client
+
+# Work on individual projects
+cd api-server
+claudetm start "Add rate limiting to API endpoints"
+
+cd ../web-client
+claudetm start "Implement dark mode toggle"
+```
+
+**3. Continuous Integration as AI Development**
+
+Integrate with CI/CD to have Claude automatically work on issues:
+
+```bash
+# GitHub Action or external trigger
+curl http://localhost:8000/repo/clone \
+  -d '{"repo_url": "'$GITHUB_REPOSITORY'", "project_name": "repo"}'
+
+curl http://localhost:8000/repo/setup \
+  -d '{"project_name": "repo"}'
+
+curl http://localhost:8000/task/init \
+  -d '{"project_dir": "~/workspace/claude-task-master/repo", "goal": "'$ISSUE_TITLE'"}'
+
+# Results reported via webhook callback
+```
+
 ## Troubleshooting
 
 ### Credentials & Setup
@@ -583,6 +802,7 @@ Each stage has specific handlers that determine when to transition to the next s
 ├── state.json            # Machine-readable state
 ├── progress.md           # Progress summary
 ├── context.md            # Accumulated learnings
+├── mailbox.json          # Pending messages for plan updates
 └── logs/
     └── run-{timestamp}.txt    # Full log (kept on success)
 ```

{claude_task_master-0.1.4 → claude_task_master-0.1.5}/pyproject.toml

@@ -4,10 +4,10 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "claude-task-master"
-version = "0.1.4"
+version = "0.1.5"
 description = "Autonomous task orchestration system that keeps Claude working until a goal is achieved"
 readme = "README.md"
-requires-python = ">=3.10"
+requires-python = ">=3.12"
 license = "MIT"
 authors = [
     {name = "Claude Task Master Team"}
@@ -17,8 +17,6 @@ classifiers = [
     "Development Status :: 3 - Alpha",
     "Intended Audience :: Developers",
     "Programming Language :: Python :: 3",
-    "Programming Language :: Python :: 3.10",
-    "Programming Language :: Python :: 3.11",
     "Programming Language :: Python :: 3.12",
     "Operating System :: OS Independent",
     "Topic :: Software Development :: Libraries :: Python Modules",
@@ -56,6 +54,7 @@ dev = [
     "pytest-cov>=4.1.0",
     "pytest-asyncio>=0.23.0",
     "pytest-timeout>=2.4.0",
+    "hypothesis>=6.100.0",
     "ruff>=0.3.0",
     "mypy>=1.9.0",
 ]
@@ -89,7 +88,7 @@ claude_task_master = ["bin/claudetm"]
 
 [tool.ruff]
 line-length = 100
-target-version = "py310"
+target-version = "py312"
 
 [tool.ruff.lint]
 select = [
@@ -110,7 +109,7 @@ quote-style = "double"
 indent-style = "space"
 
 [tool.mypy]
-python_version = "3.10"
+python_version = "3.12"
 warn_return_any = true
 warn_unused_configs = true
 disallow_untyped_defs = true
@@ -138,6 +137,10 @@ ignore_missing_imports = true
 module = "passlib.*"
 ignore_missing_imports = true
 
+[[tool.mypy.overrides]]
+module = "anthropic.*"
+ignore_missing_imports = true
+
 [[tool.mypy.overrides]]
 module = "tests.*"
 disallow_untyped_defs = false
@@ -155,7 +158,6 @@ addopts = [
     "--cov-report=term-missing",
     "--cov-report=html:coverage_html",
     "--cov-report=xml:coverage.xml",
-    "--cov-fail-under=50",
     "--timeout=2",
 ]
 asyncio_mode = "auto"
@@ -169,8 +171,16 @@ markers = [
     "slow: marks tests as slow (deselect with '-m \"not slow\"')",
     "integration: marks tests as integration tests (require external services)",
     "unit: marks tests as unit tests",
+    "property: marks tests as property-based tests using Hypothesis",
 ]
 
+# Hypothesis settings for property-based tests
+[tool.hypothesis]
+profile = "default"
+# Profiles available: default, ci, dev, quick, thorough
+# Set HYPOTHESIS_PROFILE environment variable to use a different profile
+# Example: HYPOTHESIS_PROFILE=ci pytest tests/property/
+
 [tool.coverage.run]
 source = ["src/claude_task_master"]
 branch = true

{claude_task_master-0.1.4 → claude_task_master-0.1.5}/src/claude_task_master/__init__.py

@@ -3,5 +3,5 @@
 Uses Claude Agent SDK to keep Claude working until a goal is achieved.
 """
 
-__version__ = "0.1.4"
+__version__ = "0.1.5"
 __all__ = ["__version__"]