Alex Models and Limits
Alex supports multiple AI models for different kinds of work. Some are optimized for quick answers, others for coding, deep analysis, or complex decisions. The selected model affects response quality, speed, and credit consumption.
Exact model availability depends on your tariff and the current service configuration. In chat, you only see models available to your account.
How Models Affect Consumption
Consumption is mainly affected by:
| Factor | Impact |
|---|---|
| Model complexity | Stronger models consume more credits but handle complex tasks better |
| Conversation length | A long thread may require more context |
| Amount of loaded data | Logs, files, command output, or web content increase the amount of work |
| Tools used | Diagnostics, sub-agents, and multi-step actions can add consumption |
| Cache | Repeated context can be processed more efficiently on supported models |
Alex calculates consumption automatically. The panel shows your limit state and consumption history without requiring you to manage technical details.
Model Groups
Standard model
The standard model is suitable for everyday use:
- quick questions,
- server status checks,
- simple configuration,
- error explanations,
- regular file edits,
- continuing from an existing plan.
For most tasks, this is the best starting point because it balances quality, speed, and consumption.
Coding and analytical models
These models are useful when Alex works with code, logs, or multiple files:
- application debugging,
- configuration review,
- refactoring,
- root cause analysis,
- comparing multiple solution options.
Consumption can be higher especially when the task requires a larger amount of context.
Premium models
Premium models are best for complex or higher-risk situations:
- production incidents,
- architecture decisions,
- larger migrations,
- deep debugging,
- security review,
- problems where the standard model repeatedly does not provide a good enough result.
Premium models usually consume more credits. Use them where higher quality is worth the additional consumption.
Cache on Models
Some models support prompt cache. If Alex repeatedly works with the same or similar context, part of that context may be processed more efficiently.
Cache helps most when you continue:
- in the same conversation,
- on the same server or project,
- after a previous log analysis,
- from an existing plan,
- through iterations on the same files.
For best results, continue in the same thread and avoid resending content Alex has already read.
When To Use Which Model
| Situation | Recommendation |
|---|---|
| Quick question or explanation | Standard model |
| Simple server management | Standard model |
| Installation or configuration with clear instructions | Standard or coding model |
| Debugging an error from logs | Coding or analytical model |
| Unclear incident with unknown cause | Planning Mode + suitable stronger model |
| Architecture, migration, security | Premium model when available |
Tip: Start with the standard model. If Alex reaches a complex part of the task, switch to a stronger model only for that part.
How To Save Credits When Choosing Models
- Do not use premium models for routine questions. Stronger models are most useful for complex work.
- Use Planning Mode before large changes. Get the approach first, then execute actions.
- Keep one thread per problem. This helps context and cache.
- State the goal clearly. Fewer corrective follow-ups means less unnecessary consumption.
- After a long analysis, name the next step. For example: “Continue from the plan and execute only step 1.”
Limit Indicator in Chat
The chat shows your limit state and warnings when you are getting close to exhaustion. Colors provide a quick orientation:
| Color | State |
|---|---|
| Green | Enough room for more work |
| Yellow | Consumption is growing; consider task scope |
| Orange | You are getting close to the limit |
| Red | Limit is exhausted or very close |
When a limit is exhausted, Alex shows the next available options.
Switching Models
- In chat, click the settings icon in the header.
- Select the desired model.
- The change applies to future messages.
If you are unsure, keep the default model. Alex is designed to work well for regular tasks without manual tuning.
Next Steps
- Credits and Limits - Cache, PAYG, and practical credit saving
- Best Practices - How to write effective prompts
- Alex Memory - How Alex remembers preferences
- FAQ - Frequently asked questions
Need help choosing a model? Open a support ticket or ask Alex in your panel.