Release notes
Use release notes as a checklist, not a promise that your workspace has every feature mentioned.
Coldtea features can depend on app version, build channel, feature flags, TeaHouse setup, and connected providers. If a note mentions a surface you cannot see, check those before debugging the local repo.
What to scan after an update
| Area | What to check |
|---|---|
| Agents | New or changed launch args, permission defaults, MCP attachment, or session resume behavior. |
| Worktrees | Changes to setup, run, teardown, delete, branch cleanup, or local-file copying. |
| Tasks | Board behavior, task detail fields, plans, logs, labels, or Linear sync. |
| Editor | Shortcut handling, file navigation, selections, annotations, or embedded editor startup. |
| Integrations | GitHub, Linear, Matcha QA, cloud runs, monitoring, or provider auth changes. |
| Security | Any change to local API, MCP tokens, permissions, cloud features, or shared surfaces. |
Update habits
Before updating a team workflow, pick one repo and one normal task first. Confirm the path that matters:
- Open the repo.
- Start the usual agent.
- Run a small task or inspection prompt.
- Check task links, plans, and logs if your team uses them.
- Create or open a worktree if parallel work is part of your workflow.
- Run the checks your repo normally requires.
That finds workflow breaks faster than clicking through every surface.
When a feature looks missing
Check in this order:
- You are on the expected app build or channel.
- You are signed in to the expected TeaHouse.
- The feature is enabled for that workspace.
- The connected provider is authorized for the right account, repo, team, or issue.
- The local CLI or project setup still works outside Coldtea.
A release can add a feature without enabling it for every workspace on the same day.
What to include in a bug report
Include facts that help someone reproduce the issue:
- Coldtea app version or build channel.
- Operating system.
- Project path shape, without private customer names if needed.
- Agent and launch args.
- TeaHouse/team or integration involved.
- The exact action that failed.
- The visible error message or terminal output.
- Whether the same command works in a normal terminal.
Do not include API keys, MCP tokens, provider auth files, customer data, or private repo contents unless your team has approved that support path.
Next: troubleshooting or config reference.