Profiles and Models
Configure agent personalities, model providers, thinking levels, and per-profile behavior for different workflows.
Profiles and model settings let you adapt the agent to different types of work. A support triage agent, a design reviewer, and a coding agent should not need the same personality, tools, or model behavior.
Agent Profiles
Agent profiles define how an agent behaves. A profile can include:
- Name and role
- Communication style
- Expertise
- Boundaries
- Preferred tools
- Memory scope
- Channel behavior
Use profiles when different work streams need different defaults.
Create a Profile
- Open the profile area or profile settings
- Click Create profile
- Choose a name and role
- Add instructions for tone, expertise, and boundaries
- Save the profile
- Select it before starting a matching task
Keep profile instructions specific. A useful profile says what the agent should optimize for and what it should not do without confirmation.
Thinking and Reasoning Controls
Some runtimes and providers expose reasoning or thinking levels. Higher reasoning can improve complex planning, but it can also increase latency and cost.
Use this guide:
| Work Type | Suggested Setting |
|---|---|
| Simple edits or summaries | Low or default |
| Coding tasks with known scope | Medium |
| Architecture, debugging, or design critique | High |
| Risky refactors or ambiguous product work | Highest available level with approvals |
If a runtime does not support reasoning controls, the app hides or disables that option.
Model Providers
The app can work with local CLIs and configured API providers. Model availability depends on the selected runtime, installed CLI version, and configured credentials.
When choosing a model, consider:
- Context size
- Tool-use reliability
- Cost
- Latency
- Coding strength
- Multimodal support
- Provider policy constraints
For recurring work, save the model choice in a profile or runtime setting instead of choosing it manually each time.
Profiles in Channels
Channels can use profile identity and access rules so the same desktop app can serve different users or workspaces. This is especially important when a bot participates in shared Slack, Discord, Telegram, or Lark spaces.
Use separate profiles when:
- Teams need different tone or escalation behavior
- A channel should only access a narrow workspace
- A customer-facing bot should avoid internal-only details
- A workflow needs different tools from your default desktop agent
Maintenance
Review profiles after major workflow changes. Update instructions when the agent repeatedly asks for the same clarification or when a new feature changes how the profile should work.