95c299df64
* move claude rules and commands to assets/claude * update claude profile to copy assets/claude to .claude * fix formatting * feat(profiles): Implement unified profile system - Convert Claude and Codex profiles to use createProfile() factory - Remove simple vs complex profile distinction in rule transformer - Unify convertAllRulesToProfileRules() to handle all profiles consistently - Fix mcpConfigPath construction in base-profile.js for null mcpConfigName - Update terminology from 'simpleProfiles' to 'assetOnlyProfiles' throughout - Ensure Claude .claude directory copying works in both CLI and MCP contexts - All profiles now follow same execution flow with proper lifecycle functions Changes: - src/profiles/claude.js: Convert to createProfile() factory pattern - src/profiles/codex.js: Convert to createProfile() factory pattern - src/utils/rule-transformer.js: Unified profile handling logic - src/utils/profiles.js: Remove simple profile categorization - src/profiles/base-profile.js: Fix mcpConfigPath construction - scripts/modules/commands.js: Update variable naming - tests/: Update all tests for unified system and terminology Fixes Claude profile asset copying issue in MCP context. All tests passing (617 passed, 11 skipped). * re-checkin claude files * fix formatting * chore: clean up test Claude rules files * chore: add changeset for unified profile system * add claude files back * add changeset * restore proper gitignore * remove claude agents file from root * remove incorrect doc * simplify profiles and update tests * update changeset * update changeset * remove profile specific code * streamline profiles with defaults and update tests * update changeset * add newline at end of gitignore * restore changes * streamline profiles with defaults; update tests and add vscode test * update rule profile tests * update wording for clearer profile management * refactor and clarify terminology * use original projectRoot var name * revert param desc * use updated claude assets from neno * add "YOUR_" before api key here * streamline codex profile * add gemini profile * update gemini profile * update tests * relocate function * update rules interactive setup Gemini desc * remove duplicative code * add comma
51 lines
1.1 KiB
Markdown
51 lines
1.1 KiB
Markdown
Run interactive setup to configure AI models.
|
|
|
|
## Interactive Model Configuration
|
|
|
|
Guides you through setting up AI providers for Task Master.
|
|
|
|
## Execution
|
|
|
|
```bash
|
|
task-master models --setup
|
|
```
|
|
|
|
## Setup Process
|
|
|
|
1. **Environment Check**
|
|
- Detect existing API keys
|
|
- Show current configuration
|
|
- Identify missing providers
|
|
|
|
2. **Provider Selection**
|
|
- Choose main provider (required)
|
|
- Select research provider (recommended)
|
|
- Configure fallback (optional)
|
|
|
|
3. **API Key Configuration**
|
|
- Prompt for missing keys
|
|
- Validate key format
|
|
- Test connectivity
|
|
- Save configuration
|
|
|
|
## Smart Recommendations
|
|
|
|
Based on your needs:
|
|
- **For best results**: Claude + Perplexity
|
|
- **Budget conscious**: GPT-3.5 + Perplexity
|
|
- **Maximum capability**: GPT-4 + Perplexity + Claude fallback
|
|
|
|
## Configuration Storage
|
|
|
|
Keys can be stored in:
|
|
1. Environment variables (recommended)
|
|
2. `.env` file in project
|
|
3. Global `.taskmaster/config`
|
|
|
|
## Post-Setup
|
|
|
|
After configuration:
|
|
- Test each provider
|
|
- Show usage examples
|
|
- Suggest next steps
|
|
- Verify parse-prd works |