Profile and response style
Save lasting collaboration preferences, set the AI's communication tendencies, and choose a style with the right scope. These controls manage background, expression, and adaptation separately; the current task can still give specific instructions.
Choose the right place
Open Settings > Personalization to view Collaboration profile, Style presets, and Adaptive response.
| What you want to change | Where to do it | Effect |
|---|---|---|
| Preferred name, background, and lasting reply preferences | Memory-page entry in Collaboration profile | Edit the conversation profile; the profile tab summarizes text fields |
| The AI's lasting communication tendencies | Personality axes in Collaboration profile | Adjust the AI's own profile |
| Naming, reply tone, deliverable titles and summaries | Style presets | Apply expression requirements within selected scopes |
| State-based response adaptation and related tool-risk decisions | Adaptive response | Set the adaptation switch and tool-risk mode separately |
| Deliverable requirements for one project | Project working rules | Apply within the owning project |
| Format and content requirements for this task | The current task | Give explicit requirements for this work |
For example, “Give the conclusion first, then explain the evidence” suits a lasting reply preference. “Use a formal tone and four sections in this report” can go directly in the current task.
Maintain the collaboration profile
View recorded names, background, and reply preferences in Collaboration profile. To edit text, follow its entry to the conversation-profile area on the Memory page, edit and save, then return to check the result.
Start with a preference you can verify:
Begin with a short conclusion, then explain the evidence. State uncertainty when evidence is missing. Use tables when comparing options.
Put project-specific terminology, checks, and deliverable requirements in Project working rules. Manage past decisions and experiences as memory entries, recalled according to relevance.
How language preferences apply
The profile language is normally a fallback when input language cannot be determined. To use a chosen language regardless of your input language, enable “Always reply in this language.”
Change the interface language in Desktop settings. A menu-language change alone does not establish that profile language preferences failed.
Adjust the AI's personality axes
Personality axes set the AI's lasting communication tendencies. They are not a personality test for you or a capability score for the model.
There are five axes: introversion–extraversion, sensing–intuition, thinking–feeling, judging–perceiving, and assertive–turbulent. A value of 50 is neutral. Saving recalculates the MBTI letters from these values.
Keep the midpoint if you are unsure. To adjust:
- Change one axis according to the communication tendency you want.
- Save and confirm the saved acknowledgement. “Not saved yet” after moving a slider is not a completed change.
- Compare replies to the same task.
- Adjust and save again if needed. Use the revert action to discard unsaved changes.
These tendencies do not add model capabilities or tool permissions, and cannot guarantee factual accuracy or a fixed form for every response. State exact formatting requirements in the task.
Create and activate a style preset
Under Style presets, choose an existing preset or create one. A new preset has separate fields:
| Field | What to write |
|---|---|
| Name | A recognizable name, such as “Concise project updates” |
| Naming style | How titles and task names should read, such as “Use concrete topics; avoid slogans” |
| Reply tone | How replies should read, such as “Lead with the conclusion, use direct language, and explain key evidence” |
A name is required, along with at least one of naming style or reply tone. The name allows up to 30 characters; each instruction field allows up to 800.
After saving, activate the preset and choose its scopes. Saving a preset, activating it, and applying it to the running service are separate states to confirm. If the panel says it was saved but not applied, use Retry or View service status. Appearing in the preset list alone does not prove it is active.
The AI-generation entry can help draft a style. It takes you to a conversation for authoring. Review the result, remove unsuitable lasting instructions, and confirm saving and activation.
Choose application scopes
| Scope | Changes | Does not change |
|---|---|---|
| Conversation titles | Automatic names for new sessions; Cowork task names follow the session title | Conversation content |
| Scheduled task names | Names proposed by the AI | Schedule times or scheduling rules |
| Reply tone | AI expression, taking precedence over reply style saved in Memory; also applies in connected Feishu and WeChat channels | Tool permissions or task authorization |
| Cowork deliverable copy | Deliverable titles and summaries | The deliverable's content |
To make a report's body more formal, state that requirement in the task. Enabling Cowork deliverable copy alone will not do it. Enable Reply tone as well if you also want formal conversation replies.
Style can reach beyond the conversation you are viewing on desktop. Consider connected messaging channels before enabling Reply tone.
Choose “No preset” when you no longer want one. Some built-in styles require Reply tone and explain their reach before activation; deactivation restores saved scope settings. An existing conversation may still echo its historical tone, so use a new conversation to check deactivation.
Adaptive response and tool-risk modes
Adaptive response lets EvoX adjust replies to match your state. Its enable switch and tool-risk mode are separate controls.
When enabled, each reply consumes a little additional model quota. The extra analysis does not read conversation content or use tools; if it fails, the normal reply is unaffected. Decide based on whether you want this adaptation and accept the additional usage.
| Tool-risk mode | Meaning | When to choose it |
|---|---|---|
| Off | Does not participate in tool-risk decisions | You do not need this additional risk assessment |
| Observe | Records signals without automatically upgrading approvals; the default | You want to observe its effect first |
| Ask | High-risk actions such as deletion or command-line operations ask first | You want additional confirmation for high-risk actions |
Analysis and risk-mode changes apply to new conversations. Use “Start new conversation” after saving rather than judging the saved configuration from an old conversation.
The panel explains when organization policy or environment configuration locks the switch. You cannot override it here. Risk mode does not replace existing Permissions and approvals or authorize an otherwise unauthorized action.
Verify with the same task
Use fixed input to reduce differences caused by task content:
Turn these notes into a project update: retrieval is complete; connection testing is unfinished; the release date is undecided. Lead with the conclusion and do not invent a date.
Check the conclusion and uncertainty, then inspect conversation naming and deliverable titles and summaries separately. Content changes and naming changes need separate checks.
| Symptom | Check |
|---|---|
| Titles change but reply tone does not | Whether the preset has tone instructions and Reply tone is enabled |
| Deliverable title changes but its body does not | Expected for deliverable copy; put body requirements in the task |
| Replies differ from the profile's style | Active Reply tone preset and current task instructions |
| An old conversation does not change after an adaptation update | Verify in a new conversation |
| A change reverts after refreshing | Save errors; an unsaved preview is not the final configuration |
| Background or preferred name is incorrect | Edit the conversation profile in Memory and confirm saving |
Begin with one preference, one preset, and one short task. Add more requirements once you have verified the scopes.