Personalize EvoX
Set preferences and carry useful context across conversations.
Personalize EvoX so its responses and ways of working better match your preferences. You can adjust the collaboration profile, response style, and adaptive responses at any time in desktop settings.
Tell EvoX how you collaborate
The collaboration profile summarizes your name, reply language, and durable working preferences. Edit its text in Memory. The five preference axes tune the AI’s communication style; they are not a personality test of you.
Keep stable background
If you maintain product documentation for general readers, retain that audience and your regular communication preferences. For an engineering review, state the task-specific audience and deliverable without replacing your lasting background.
Explore communication tendencies
The five axes below preview AI communication tendencies, not your personality. Change one to explore proactive explanations, factual emphasis, or tone. Configuration guides own the actual settings and application rules.
MBTI preference axes
Move the sliders to preview EvoX's long-term communication profile.
Make expression preferences concrete
“Be more professional” has no clear acceptance criterion. “Lead with the conclusion, then evidence; explain each new term in one sentence” is easier to follow and verify. Save lasting expression preferences as a style preset.
Decide which kind of expression you want to improve:
- Conversation titles: identify the work being done.
- Scheduled task names: make the goal recognizable and easy to find.
- Reply tone: direct and concise, or with fuller explanations.
- Deliverable titles and summaries: specify these separately from document-body requirements.
Style settings affect presentation and wording. They do not expand permissions or replace explicit task requirements.
Understand adaptive replies
Adaptive replies use state signals to adjust responses; risk adaptation handles tool-risk signals. They are configured separately from fixed style presets and do not replace task-specific requirements.
Preferences do not authorize actions
Asking EvoX to be proactive does not authorize deleting files, sending messages, or publishing. State the goal, allowed operations, and confirmation points rather than using “be bold” as an access scope.
Understand additional analysis
Adaptive analysis uses additional model quota, does not read conversation content, and does not call tools. Configuration covers activation, risk modes, and new-session application rules.
Carry context forward with memory
Memory suits stable preferences and background, such as “I maintain product documentation for nontechnical readers.” Put standing project requirements in project rules and repeatable steps in skills, rather than using memory as a substitute for either.
Memory is separate from explicit instructions in the current task. State any different tone, format, or behavior directly in the prompt; task-specific requirements take priority.
Continue to usage and configuration
Try a familiar task and check the expression against your expectations. Read Long-term memory for using lasting context, or Profile and response style to configure presets, language, and adaptation.