Compare commits
1 Commits
feat-gener
...
docs/auto-
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
1cfdaa3a65 |
@@ -75,6 +75,7 @@ Taskmaster uses two primary methods for configuration:
|
|||||||
- `AZURE_OPENAI_API_KEY`: Your Azure OpenAI API key (also requires `AZURE_OPENAI_ENDPOINT`).
|
- `AZURE_OPENAI_API_KEY`: Your Azure OpenAI API key (also requires `AZURE_OPENAI_ENDPOINT`).
|
||||||
- `OPENROUTER_API_KEY`: Your OpenRouter API key.
|
- `OPENROUTER_API_KEY`: Your OpenRouter API key.
|
||||||
- `XAI_API_KEY`: Your X-AI API key.
|
- `XAI_API_KEY`: Your X-AI API key.
|
||||||
|
- `GROK_CLI_API_KEY`: Your Grok API key from console.x.ai.
|
||||||
- **Optional Endpoint Overrides:**
|
- **Optional Endpoint Overrides:**
|
||||||
- **Per-role `baseURL` in `.taskmasterconfig`:** You can add a `baseURL` property to any model role (`main`, `research`, `fallback`) to override the default API endpoint for that provider. If omitted, the provider's standard endpoint is used.
|
- **Per-role `baseURL` in `.taskmasterconfig`:** You can add a `baseURL` property to any model role (`main`, `research`, `fallback`) to override the default API endpoint for that provider. If omitted, the provider's standard endpoint is used.
|
||||||
- **Environment Variable Overrides (`<PROVIDER>_BASE_URL`):** For greater flexibility, especially with third-party services, you can set an environment variable like `OPENAI_BASE_URL` or `MISTRAL_BASE_URL`. This will override any `baseURL` set in the configuration file for that provider. This is the recommended way to connect to OpenAI-compatible APIs.
|
- **Environment Variable Overrides (`<PROVIDER>_BASE_URL`):** For greater flexibility, especially with third-party services, you can set an environment variable like `OPENAI_BASE_URL` or `MISTRAL_BASE_URL`. This will override any `baseURL` set in the configuration file for that provider. This is the recommended way to connect to OpenAI-compatible APIs.
|
||||||
@@ -316,4 +317,68 @@ Azure OpenAI provides enterprise-grade OpenAI models through Microsoft's Azure c
|
|||||||
- Confirm the model is deployed in your Azure OpenAI resource
|
- Confirm the model is deployed in your Azure OpenAI resource
|
||||||
- Verify the deployment name matches your configuration exactly (case-sensitive)
|
- Verify the deployment name matches your configuration exactly (case-sensitive)
|
||||||
- Ensure the model deployment is in a "Succeeded" state in Azure OpenAI Studio
|
- Ensure the model deployment is in a "Succeeded" state in Azure OpenAI Studio
|
||||||
- Ensure youre not getting rate limited by `maxTokens` maintain appropriate Tokens per Minute Rate Limit (TPM) in your deployment.
|
- Ensure youre not getting rate limited by `maxTokens` maintain appropriate Tokens per Minute Rate Limit (TPM) in your deployment.
|
||||||
|
|
||||||
|
### Grok AI Configuration
|
||||||
|
|
||||||
|
Grok AI provides access to xAI's Grok models with enhanced reasoning capabilities and requires minimal configuration:
|
||||||
|
|
||||||
|
1. **Prerequisites**:
|
||||||
|
- An xAI account with API access
|
||||||
|
- Grok API key from [console.x.ai](https://console.x.ai)
|
||||||
|
|
||||||
|
2. **Authentication**:
|
||||||
|
- Set the `GROK_CLI_API_KEY` environment variable with your Grok API key
|
||||||
|
|
||||||
|
3. **Available Models**:
|
||||||
|
- `grok-beta`: Latest Grok model with advanced reasoning
|
||||||
|
- `grok-vision-beta`: Grok with vision capabilities for image analysis
|
||||||
|
|
||||||
|
4. **Configuration Example**:
|
||||||
|
```json
|
||||||
|
// In .taskmaster/config.json
|
||||||
|
{
|
||||||
|
"models": {
|
||||||
|
"main": {
|
||||||
|
"provider": "grok-cli",
|
||||||
|
"modelId": "grok-beta",
|
||||||
|
"maxTokens": 131072,
|
||||||
|
"temperature": 0.3
|
||||||
|
},
|
||||||
|
"research": {
|
||||||
|
"provider": "grok-cli",
|
||||||
|
"modelId": "grok-vision-beta",
|
||||||
|
"maxTokens": 131072,
|
||||||
|
"temperature": 0.1
|
||||||
|
}
|
||||||
|
}
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
5. **Environment Variables**:
|
||||||
|
```bash
|
||||||
|
# In .env file
|
||||||
|
GROK_CLI_API_KEY=your-grok-api-key-here
|
||||||
|
```
|
||||||
|
|
||||||
|
6. **Setup Commands**:
|
||||||
|
```bash
|
||||||
|
# Set Grok as your main model
|
||||||
|
task-master models --set-main grok-beta
|
||||||
|
|
||||||
|
# Set Grok as your research model
|
||||||
|
task-master models --set-research grok-beta
|
||||||
|
|
||||||
|
# Set Grok as your fallback model
|
||||||
|
task-master models --set-fallback grok-beta
|
||||||
|
```
|
||||||
|
|
||||||
|
7. **Integration Features**:
|
||||||
|
- **Local Configuration Support**: The Grok CLI provider can use your local Grok CLI configuration file (`~/.grok/user-settings.json`) if available
|
||||||
|
- **Full Token Capacity**: Supports Grok's full 131K token capacity for large context operations
|
||||||
|
- **Built on Grok CLI**: Uses the [grok-cli](https://github.com/superagent-ai/grok-cli) by Superagent AI for reliable integration
|
||||||
|
|
||||||
|
8. **Troubleshooting**:
|
||||||
|
- **API Key Issues**: Verify your `GROK_CLI_API_KEY` is correctly set and valid
|
||||||
|
- **Model Availability**: Ensure you have access to the specified Grok model variant
|
||||||
|
- **Rate Limits**: Grok models have generous rate limits, but large contexts may take longer to process
|
||||||
@@ -38,6 +38,39 @@ sidebarTitle: "CLI Commands"
|
|||||||
```
|
```
|
||||||
</Accordion>
|
</Accordion>
|
||||||
|
|
||||||
|
<Accordion title="Start Working on a Task">
|
||||||
|
```bash
|
||||||
|
# Start working on a specific task with Claude Code
|
||||||
|
task-master start <id>
|
||||||
|
|
||||||
|
# Start the next available task automatically
|
||||||
|
task-master start
|
||||||
|
|
||||||
|
# Show what would be executed without launching Claude Code
|
||||||
|
task-master start <id> --dry-run
|
||||||
|
|
||||||
|
# Force start even if another task is in-progress
|
||||||
|
task-master start <id> --force
|
||||||
|
|
||||||
|
# Don't automatically update task status to in-progress
|
||||||
|
task-master start <id> --no-status-update
|
||||||
|
|
||||||
|
# Specify project root directory
|
||||||
|
task-master start <id> --project /path/to/project
|
||||||
|
|
||||||
|
# Get results in JSON format
|
||||||
|
task-master start <id> --format json
|
||||||
|
```
|
||||||
|
|
||||||
|
The `start` command automatically launches Claude Code with comprehensive context about the task, including:
|
||||||
|
- Task details and requirements
|
||||||
|
- Implementation guidelines
|
||||||
|
- Related subtasks and dependencies
|
||||||
|
- Project-specific context
|
||||||
|
|
||||||
|
When no task ID is provided, it automatically finds and starts the next available task based on dependencies and status.
|
||||||
|
</Accordion>
|
||||||
|
|
||||||
<Accordion title="Show Specific Task">
|
<Accordion title="Show Specific Task">
|
||||||
```bash
|
```bash
|
||||||
# Show details of a specific task
|
# Show details of a specific task
|
||||||
|
|||||||
@@ -16,6 +16,24 @@ Alternatively you can use the CLI to show the next task
|
|||||||
task-master next
|
task-master next
|
||||||
```
|
```
|
||||||
|
|
||||||
|
### Quick Start with `task-master start`
|
||||||
|
|
||||||
|
For immediate task execution, you can use the new `start` command to automatically launch Claude Code with full task context:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
# Start the next available task automatically
|
||||||
|
task-master start
|
||||||
|
|
||||||
|
# Or start a specific task
|
||||||
|
task-master start 1.2
|
||||||
|
```
|
||||||
|
|
||||||
|
This command will:
|
||||||
|
- Find the next available task (if no ID is provided)
|
||||||
|
- Update the task status to "in-progress"
|
||||||
|
- Launch Claude Code with comprehensive task context
|
||||||
|
- Provide all necessary implementation details and project context
|
||||||
|
|
||||||
## Discuss Task
|
## Discuss Task
|
||||||
When you know what task to work on next you can then start chatting with the agent to make sure it understands the plan of action.
|
When you know what task to work on next you can then start chatting with the agent to make sure it understands the plan of action.
|
||||||
|
|
||||||
|
|||||||
@@ -3,4 +3,70 @@ title: "What's New"
|
|||||||
sidebarTitle: "What's New"
|
sidebarTitle: "What's New"
|
||||||
---
|
---
|
||||||
|
|
||||||
|
## Latest Features (January 2025)
|
||||||
|
|
||||||
|
### 🚀 New `task-master start` Command
|
||||||
|
|
||||||
|
**Automated Task Execution with Claude Code Integration**
|
||||||
|
|
||||||
|
The new `start` command revolutionizes your development workflow by automatically launching Claude Code with comprehensive task context:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
# Start a specific task
|
||||||
|
task-master start 1.2
|
||||||
|
|
||||||
|
# Start the next available task automatically
|
||||||
|
task-master start
|
||||||
|
|
||||||
|
# Preview what would be executed without launching Claude Code
|
||||||
|
task-master start 1.2 --dry-run
|
||||||
|
```
|
||||||
|
|
||||||
|
**Key Features:**
|
||||||
|
- **Automatic Task Discovery** - When no ID is provided, finds the next available task based on dependencies and status
|
||||||
|
- **Rich Context Injection** - Provides Claude Code with task details, requirements, subtasks, and project context
|
||||||
|
- **Status Management** - Automatically updates task status to "in-progress" when starting
|
||||||
|
- **Flexible Options** - Support for dry-run, force mode, custom project paths, and JSON output
|
||||||
|
|
||||||
|
### 🤖 Grok AI Provider Support
|
||||||
|
|
||||||
|
**Enhanced AI Model Options**
|
||||||
|
|
||||||
|
Task Master now supports xAI's Grok models with full 131K token capacity:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
# Configure Grok as your main model
|
||||||
|
task-master models --set-main grok-beta
|
||||||
|
|
||||||
|
# Use Grok with vision capabilities
|
||||||
|
task-master models --set-research grok-vision-beta
|
||||||
|
```
|
||||||
|
|
||||||
|
**Setup:**
|
||||||
|
1. Get your API key from [console.x.ai](https://console.x.ai)
|
||||||
|
2. Set `GROK_CLI_API_KEY` environment variable
|
||||||
|
3. Configure using `task-master models --setup`
|
||||||
|
|
||||||
|
**Available Models:**
|
||||||
|
- `grok-beta` - Latest Grok model with advanced reasoning
|
||||||
|
- `grok-vision-beta` - Grok with vision capabilities
|
||||||
|
|
||||||
|
### 📱 VS Code Extension "Start Task" Button
|
||||||
|
|
||||||
|
**Seamless VS Code Integration**
|
||||||
|
|
||||||
|
The Task Master VS Code extension now includes a "Start Task" button for one-click task execution:
|
||||||
|
|
||||||
|
- **Direct Integration** - Launch Claude Code directly from task cards in VS Code
|
||||||
|
- **No Terminal Switching** - Automatic terminal management and command execution
|
||||||
|
- **Full Context** - Same rich context injection as the CLI command
|
||||||
|
- **Visual Workflow** - Seamless transition from task planning to implementation
|
||||||
|
|
||||||
|
### 🔧 Technical Improvements
|
||||||
|
|
||||||
|
- **TypeScript Migration** - Core components now use TypeScript for better type safety
|
||||||
|
- **Model Configuration Updates** - Upgraded fallback model to Claude Sonnet 4
|
||||||
|
- **Token Capacity Fixes** - Grok models now properly support their full 131K token capacity
|
||||||
|
- **Enhanced Error Handling** - Improved error messages and debugging capabilities
|
||||||
|
|
||||||
An easy way to see the latest releases
|
An easy way to see the latest releases
|
||||||
@@ -22,6 +22,7 @@ Taskmaster AI is an intelligent task management system designed for AI-assisted
|
|||||||

|

|
||||||
|
|
||||||
### 🤖 **AI-Powered Features**
|
### 🤖 **AI-Powered Features**
|
||||||
|
- **One-Click Task Start** - Launch Claude Code directly from task cards with full context
|
||||||
- **Task Content Generation** - Regenerate task descriptions using AI
|
- **Task Content Generation** - Regenerate task descriptions using AI
|
||||||
- **Smart Task Updates** - Append findings and progress notes automatically
|
- **Smart Task Updates** - Append findings and progress notes automatically
|
||||||
- **MCP Integration** - Seamless connection to Taskmaster AI via Model Context Protocol
|
- **MCP Integration** - Seamless connection to Taskmaster AI via Model Context Protocol
|
||||||
@@ -83,6 +84,7 @@ The extension automatically handles the Taskmaster MCP server connection:
|
|||||||
| **View Kanban Board** | `Ctrl/Cmd + Shift + P` → "Taskmaster: Show Board" |
|
| **View Kanban Board** | `Ctrl/Cmd + Shift + P` → "Taskmaster: Show Board" |
|
||||||
| **Change Task Status** | Drag task card to different column |
|
| **Change Task Status** | Drag task card to different column |
|
||||||
| **View Task Details** | Click on any task card |
|
| **View Task Details** | Click on any task card |
|
||||||
|
| **Start Working on Task** | Click "Start Task" button to launch Claude Code automatically |
|
||||||
| **Edit Task Content** | Click task → Use edit buttons in details panel |
|
| **Edit Task Content** | Click task → Use edit buttons in details panel |
|
||||||
| **Add Subtasks** | Click the + button on parent task cards |
|
| **Add Subtasks** | Click the + button on parent task cards |
|
||||||
| **Use AI Features** | Open task details → Click AI action buttons |
|
| **Use AI Features** | Open task details → Click AI action buttons |
|
||||||
|
|||||||
72
output.txt
Normal file
72
output.txt
Normal file
File diff suppressed because one or more lines are too long
Reference in New Issue
Block a user