On This Page8 sections
Editorial snapshot from September 2026. Prices, models and interface labels may change; this is a practical guide, not a live product feed.
How to check model availability, plan access and usage in TraeCode and TraeWork.
Use the model picker as the source of truth
A model announcement is not a guarantee of access on every account. Check the model picker in the product you use, then confirm your region, plan and available usage. The official model documentation is dynamically rendered; we have not verified a complete current roster and do not republish the old Claude 3.5 / DeepSeek list as current.
Check access before changing your workflow
The international Free plan currently lists Auto mode only. Paid plans list access to all models, subject to the product’s availability. A model family, an exact version and an agent are different choices.
- Update the client from the official download center.
- Open the model picker and record the exact model name.
- Check your subscription and usage balance.
- Try a small task before running a long agent session.
When a model disappears
Record the client version, region, account plan and error text. Check the official documentation or support before repeatedly retrying. A missing model may reflect account eligibility, a rollout or a service issue; it does not by itself mean your installation is broken.
A complete first task: change, verify and review
-
Choose a small repository that already builds. Save a clean Git checkpoint and write down the command that currently passes. This gives you a baseline for distinguishing an existing problem from a generated regression.
-
Describe one observable result: for example, add a required field to an existing form and show an error without submitting invalid data. Include the relevant files, existing validation helper and the behavior that must stay unchanged.
-
Ask for a short plan before editing. Check that it names the affected components, data flow and verification command. Resolve missing context before allowing a broad refactor.
-
Review the diff in small batches. Check dependencies, generated files, environment variables and error handling as well as the visible result. Run the project checks and exercise both the successful and failing paths.
-
Inspect the usage record after the task. Record the accepted outcome, review time and usage consumed. Repeat on a second representative task before choosing a paid plan or moving a team workflow.
A task brief you can adapt
Goal: describe the user-visible change.
Context: list the relevant files and existing implementation.
Constraints: keep the public API and use the existing dependencies.
Verification: run the repository's documented checks and test the failure path.
Completion: summarize changed files, checks performed and remaining limitations.When the result is not usable
A successful request does not prove the code works. If the agent edits the wrong files, reduce the scope and supply the entry point explicitly. If a command fails, reproduce it in the same terminal environment before changing the prompt. If an MCP connection fails, separate server startup, credentials and client configuration. If usage is exhausted, check the account balance and selected model before repeating the same request. Keep a failed patch small enough to revert without losing unrelated work.
Common questions before you switch
Does a paid subscription mean unlimited agent work?
No. Subscription price, included usage, model access and additional usage are different things. A plan with unlimited autocomplete does not imply unlimited model requests or cloud tasks.
Should I connect every MCP server at once?
Start with the one integration needed by your current task. Confirm that it starts, exposes the expected tools and receives only the intended project context before adding another.
How should I compare two AI editors?
Use the same repository, task and acceptance checks. Compare correct changes, review effort, setup friction and recorded usage. A long feature list does not establish which editor produces better code for your project.
Related TRAE guides
Continue Reading
More articles connected to the same themes, protocols, and tools.
Referenced Tools
Browse entries that are adjacent to the topics covered in this article.
