From d5ac1af36a83b0c86df00e0101f6cb9a2c6f224c Mon Sep 17 00:00:00 2001 From: Joe Danziger Date: Fri, 23 May 2025 18:20:23 -0400 Subject: [PATCH] update var name --- assets/rules/dev_workflow.mdc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/assets/rules/dev_workflow.mdc b/assets/rules/dev_workflow.mdc index 4d430323..003251d8 100644 --- a/assets/rules/dev_workflow.mdc +++ b/assets/rules/dev_workflow.mdc @@ -116,7 +116,7 @@ Taskmaster configuration is managed through two main mechanisms: * For MCP/Cursor integration, configure these keys in the `env` section of `.cursor/mcp.json`. * Available keys/variables: See `assets/env.example` or the Configuration section in the command reference (previously linked to `taskmaster.mdc`). -**Important:** Non-API key settings (like model selections, `MAX_TOKENS`, `LOG_LEVEL`) are **no longer configured via environment variables**. Use the `task-master models` command (or `--setup` for interactive configuration) or the `models` MCP tool. +**Important:** Non-API key settings (like model selections, `MAX_TOKENS`, `TASKMASTER_LOG_LEVEL`) are **no longer configured via environment variables**. Use the `task-master models` command (or `--setup` for interactive configuration) or the `models` MCP tool. **If AI commands FAIL in MCP** verify that the API key for the selected provider is present in the `env` section of `.cursor/mcp.json`. **If AI commands FAIL in CLI** verify that the API key for the selected provider is present in the `.env` file in the root of the project.