feat: Hamster Integration - Cloud Storage, Sentry Telemetry, and Major CLI UX Improvements (#1452)

Author: eyaltoledano

.changeset/crisp-zebras-spend.md

@@ -0,0 +1,28 @@
+---
+"task-master-ai": minor
+---
+
+Add Hamster integration for `parse-prd` command
+
+Your tasks are only as good as the context behind them. Now when you run `parse-prd`, you can choose to bring your PRD to Hamster instead of parsing locally.
+
+**New Workflow Choice**
+- **Parse locally**: PRD becomes a task list in a local JSON file - great for quick prototyping and vibing solo
+- **Bring it to Hamster**: PRD becomes a living brief connected to your team, codebase, and agents
+
+**Why Hamster?**
+- Tasks live in a central place with real-time sync across your team
+- Collaborate on your PRD/brief together, generate tasks on Hamster, bring them into Taskmaster
+- No API keys needed - Hamster handles all AI inference, just need a Hamster account
+
+**Hamster Integration**
+- OAuth login flow when choosing Hamster (same as export command)
+- Create brief directly from PRD content with auto-generated title/description
+- Progress bar showing task generation phases (analyzing → generating → processing)
+- Invite teammates during brief creation
+- Auto-set context to new brief when complete
+
+**Quality of Life**
+- Clickable brief URL and team invite URL in terminal
+- Shows task count as they're generated
+- Graceful fallback if generation takes longer than expected

.changeset/hot-icons-thank.md

@@ -0,0 +1,27 @@
+---
+"task-master-ai": minor
+---
+
+Redesign `tm init` with clearer workflow selection and reduced noise
+
+Choose how you want to plan: Solo with Taskmaster or Together with Hamster. The new init flow guides you through setup with context-appropriate options and cleaner output.
+
+**New Workflow Selection**
+- Clear framing: "You need a plan before you execute. How do you want to build it?"
+- **Solo (Taskmaster)**: Parse PRD → structured tasks → AI agent executes with control
+- **Together (Hamster)**: Team writes brief → Hamster refines → aligned execution with Taskmaster
+
+**Cleaner Experience**
+- Optional AI IDE rules setup (Y/n prompt instead of always showing)
+- 15+ log messages moved to debug level - much less noise
+- Skip Git prompts when using Hamster (not needed for cloud storage)
+- Skip AI model configuration for Hamster (uses Hamster's AI)
+
+**Hamster Integration**
+- OAuth login flow when choosing Hamster workflow
+- Context-aware guidance based on your workflow choice
+
+**Quality of Life**
+- Run `tm rules --setup` anytime if you declined during init
+- Use `--yes` flag for fully non-interactive setup
+- Use `--rules cursor,windsurf` to specify rules upfront

.changeset/red-buses-listen.md

@@ -0,0 +1,25 @@
+---
+"task-master-ai": minor
+---
+
+Introduce `tm export` command - bring Task Master to your team
+
+Share your task plans with teammates by exporting local tasks to collaborative briefs on Hamster. Select which tags to export, invite team members, and start collaborating instantly.
+
+**New `tm export` Command**
+- Export your local tasks to shareable team briefs
+- Hamster will reverse engineer your PRD based on your tasks (reverse parse prd!)
+- Select multiple tags to export in one go, import all tasks across tags to Hamster
+- Hamster will generate brief titles and descriptions from your task content
+- Automatically sets your CLI context to the new brief
+- All AI calls handled by Hamster, zero API keys needed - just a Hamster account!
+
+**Team Collaboration**
+- Invite teammates during export with `-I, --invite` flag
+- Add up to 10 team members by email
+- See invitation status: sent, already a member, or error
+
+**Quality of Life Improvements**
+- New `tm login` / `tm logout` shortcuts
+- Display ID shortcuts: `tm show ham31` now works (normalizes to HAM-31)
+- Better task rendering with proper HTML/Markdown support

.changeset/sentry-telemetry-integration.md

@@ -0,0 +1,14 @@
+---
+'task-master-ai': patch
+---
+
+Add Sentry integration for error tracking and AI telemetry monitoring
+
+- **Sentry Integration**: Added comprehensive error tracking and AI operation monitoring using Sentry with Vercel AI SDK integration
+- **AI Telemetry**: All AI operations (generateText, streamText, generateObject, streamObject) now automatically track spans, token usage, prompts, and responses
+- **MCP Server Instrumentation**: Wrapped FastMCP server with `Sentry.wrapMcpServerWithSentry()` to automatically capture spans for all MCP tool interactions
+- **Privacy Controls**: Added `anonymousTelemetry` config option (default: true) allowing local storage users to opt out of telemetry
+- **Complete Coverage**: Telemetry enabled for all AI commands including parse-prd, expand, update-task, analyze-complexity, and research
+- **Internal Telemetry**: Sentry DSN is hardcoded internally for Task Master's telemetry (not user-configurable)
+- **Dual Initialization**: Automatic Sentry initialization in both CLI (scripts/dev.js) and MCP Server (mcp-server/src/index.js) with full MCP instrumentation
+

.changeset/slow-grapes-do.md

@@ -0,0 +1,28 @@
+---
+"task-master-ai": minor
+---
+
+Add simpler positional syntax and Hamster-aware UI improvements
+
+- **Simpler command syntax**: Use positional arguments without flags
+  - `tm update-task 1 Added implementation` (no quotes needed for multi-word prompts)
+  - `tm status 1 done` (new alias for set-status) or `tm set-status 1,1.1,2 in-progress`
+  - `tm list done` or `tm list in-progress` or `tm list all` (shortcut for --with-subtasks)
+- **Hamster-aware help**: Context-specific command list when connected to Hamster
+  - Shows only relevant commands for Hamster workflow
+  - Beautiful boxed section headers with improved spacing
+  - Clear usage examples with new positional syntax
+  - Better visual alignment and cleaner formatting
+- **Progress indicators**: Added loading spinner to `update-task` when connected to Hamster
+  - Shows "Updating task X on Hamster..." during AI processing
+  - Cleaner, more responsive UX for long-running operations
+- **Improved context display**: Show 'Brief: [name]' instead of 'tag: [name]' when connected to Hamster
+- **Cleaner Hamster updates**: Simplified update display (removed redundant Mode/Prompt info)
+- **Smart messaging**: "NO TASKS AVAILABLE" warning only shows when literally no tasks exist
+  - Removed misleading messages when tasks are just completed/in-progress/blocked
+  - Better UX for filtered task lists
+- **Updated help everywhere**: Regular help menu now shows new positional argument syntax
+  - All suggested actions updated across commands
+  - Consistent syntax in all UI components
+- **Auto-detection**: Automatically detects Hamster connection for better UX
+- **Backward compatible**: All old flag syntax still works (`--id`, `--status`, etc.)

.claude/commands/go/ham.md

@@ -0,0 +1,139 @@
+# Hamster (Go ham!) Run Task Workflow
+
+This command initiates the HAM (Hamster Automated Management) workflow for task execution.
+
+## Usage
+
+```
+/go:ham [task-id]
+```
+
+- `task-id` (optional): Specific task identifier to work on (e.g., "1", "1.2", "2.3.1")
+  - If provided, start working on that specific task immediately
+  - If omitted, automatically identify the next available task
+
+## Process
+
+When the user invokes this command, follow these steps:
+
+### 1. Task Selection
+
+#### If task-id is provided ($ARGUMENTS is not empty):
+```bash
+tm show $ARGUMENTS
+```
+Start working on the specified task immediately, skipping to step 3.
+
+#### If no task-id is provided ($ARGUMENTS is empty):
+```bash
+tm list
+```
+Display all tasks with their current status to provide context.
+
+### 2. Identify Next Task (only if no task-id provided)
+Determine which task should be worked on next based on:
+- Dependencies
+- Priority
+- Current status (pending tasks only)
+
+### 3. Show Task Details (only if task wasn't specified in step 1)
+```bash
+tm show <task-id>
+```
+Display the full details of the identified task including:
+- Title and description
+- Dependencies
+- Test strategy
+- Subtasks (if any)
+
+### 4. Kickoff Workflow
+
+Based on the task type, follow the appropriate workflow:
+
+#### For Main Tasks (e.g., "1", "2", "3")
+- Review the task's subtasks
+- If no subtasks exist, suggest expanding the task first
+- Identify the first pending subtask
+- Begin implementation following the subtask's requirements
+
+#### For Subtasks (e.g., "1.1", "2.3")
+- Mark the subtask as in-progress:
+  ```bash
+  tm set-status --id=<subtask-id> --status=in-progress
+  ```
+- Review the task details and requirements
+- Check for related code files or dependencies
+- Create an implementation plan
+- Begin implementation following project conventions
+
+### 5. Implementation Guidelines
+
+Follow these principles during implementation:
+
+1. **Understand First**: Read related files and understand the current architecture
+2. **Plan**: Create a mental model or brief plan before coding
+3. **Follow Conventions**: Adhere to project structure and coding standards
+4. **Test As You Go**: Validate changes incrementally
+5. **Stay Focused**: Complete the current subtask before moving to the next
+
+### 6. Task Completion
+
+When the subtask is complete:
+```bash
+tm set-status --id=<subtask-id> --status=done
+```
+
+Then automatically check for the next available task by repeating from step 2.
+
+## Example Flows
+
+### With Specific Task ID
+```
+User: "/go:ham 1.2"
+
+1. Claude runs: tm show 1.2
+   → Displays full task details
+2. Claude analyzes the task and creates an implementation plan
+3. Claude marks task in-progress: tm set-status --id=1.2 --status=in-progress
+4. Claude begins implementation following the task requirements
+5. Upon completion, Claude runs: tm set-status --id=1.2 --status=done
+6. Claude automatically identifies next task with tm list
+```
+
+### Without Specific Task ID (Auto-discovery)
+```
+User: "/go:ham"
+
+1. Claude runs: tm list
+2. Claude identifies next available task (e.g., 1.2)
+3. Claude runs: tm show 1.2
+   → Displays full task details
+4. Claude analyzes the task and creates an implementation plan
+5. Claude marks task in-progress: tm set-status --id=1.2 --status=in-progress
+6. Claude begins implementation following the task requirements
+7. Upon completion, Claude runs: tm set-status --id=1.2 --status=done
+8. Claude automatically identifies next task with tm list
+```
+
+## Notes
+
+- Always verify task dependencies are complete before starting
+- If a task is blocked, mark it as such and move to the next available task
+- Keep the user informed of progress at each major step
+- Ask for clarification if task requirements are unclear
+- Follow the project's CLAUDE.md and .cursor/rules/* guidelines at all times
+- Unlike the usual Taskmaster process, do not bother using update-task nor update-subtask as they do not work with Hamster tasks yet.
+
+- Use only `tm list`, `tm show <sub/task id>` and `tm set status` - other commands don't yet work with it.
+- Do not use the MCP tools when connected with Hamster briefs - that is not yet up to date.
+- Use `.cursor/rules/git_workflow.mdc` as a guide for the workflow
+- When starting a task, mark it as in-progress. You can mark multiple task statuses at once with comma separation (i.e. `tm set-status -i 1,1.1 -s in-progress`)
+- Read the task, then if it has subtasks, begin implementing the subtasks one at a time.
+- When the subtask is done, run lint and typecheck, mark the task as done if it passes, and commit.
+- Continue until all subtasks are done, then run a final lint and typecheck (`npm lint` and `npm typecheck`) and create a PR using `gh` cli for that Task.
+- Keep committing to the same PR as long as the scope is maintained. An entire task list (brief) might fit into a single PR but not if it ends up being huge. It is preferred for everything to land in one PR if it is possible, otherwise commit to different PRs that build on top of the previous ones. Confirm with the human when doing this.
+- When the parent task is completed, ensure you mark is as done.
+- When the first task is done, repeat this process for all tasks until all tasks are done.
+- If you run into an issue where the JWT seems expired or commands don't work, ensure you use `tm auth refresh` to refresh the token and if that does not work, use `tm context <brief url>` to reconnect the context. If you do not have the brief url, ask the user for it (perhaps use it at the beginning)
+
+You're a fast hamster. Go go go.