Personalization settings
Personalize Bravo at /app/personalization. Settings apply across all conversations after you save them.
- Nickname — how Bravo addresses you
- Company — where you work, for more relevant framing
- Custom instructions — persistent communication preferences that Bravo should use across conversations
Custom instructions
Custom instructions are account-level guidance for how Bravo should communicate with you. They are saved in Personalization and apply across conversations after you save them. Use them for standing preferences you want Bravo to remember, not for one-time instructions that only apply to the current chat.
The custom instructions field accepts up to 1,500 characters. Changes affect future responses; they do not rewrite earlier messages. To remove custom instructions, clear the field and save.
What custom instructions can guide
- Language: ask Bravo to always respond in a specific language, switch languages only when asked, translate terms, or preserve quoted text in its original language.
- Regional style: prefer British English or American English, use local date formats, prefer metric or imperial units, or avoid region-specific idioms.
- Tone and voice: be blunt, formal, casual, warm, skeptical, concise, dry, plainspoken, low-fluff, or more conversational.
- Response structure: use bullets, numbered lists, headings, tables, concise sections, checklists, a TL;DR, a final recommendation, or downloadable files for longer outputs.
- Length and density: keep answers under a set length, lead with the answer, expand thoroughly by default, avoid long intros, or include only the decision-relevant detail.
- Assumed expertise: skip basic explanations, assume you know a language or domain, define jargon, include beginner context, or explain tradeoffs at an expert level.
- Clarifying questions: ask before making major assumptions, state assumptions and proceed, ask at most one question, or only stop for true blockers.
- Pushback and critique: challenge weak reasoning, call out missing evidence, identify risks first, be candid about uncertainty, or avoid agreeable phrasing.
- Answer ordering: give yes/no first, put the recommendation before the rationale, list caveats last, or summarize concrete outcomes instead of process.
- Writing preferences: use a house style for emails, memos, documents, proposals, summaries, release notes, or other text Bravo drafts for you.
Examples
- Always respond in Spanish unless I ask for another language.
- Use British English. Prefer day-month-year dates and metric units.
- Be blunt and direct. Skip praise and keep the first sentence actionable.
- Use dry humor sparingly. Do not use exclamation points.
- Keep routine answers under three sentences. Use bullets for lists of three or more.
- Skip basic explanations. Assume I know Python, TypeScript, and AWS.
- Ask before making major assumptions, but do not ask questions for discoverable facts.
- Challenge my reasoning when I make an unsupported claim.
- When comparing options, give a recommendation first, then tradeoffs.
- For external facts, cite sources and say when something is an inference.
- Put long report drafts, proposals, or polished memos in a downloadable DOCX file.
- Create downloadable CSV files for tables, lists, exports, or structured data.
- Put reusable checklists, templates, or meeting agendas in a downloadable Markdown file.
- For data cleanup or analysis, summarize the result inline and attach the cleaned data as CSV.
- For slide outlines, give the short version inline and put the full outline in a downloadable document.
- For code-heavy answers, keep the explanation inline and put complete files or scripts in downloadable files.
- For long research summaries, answer inline first and attach a longer source-by-source brief when useful.
Good custom instructions are specific
Prefer concrete, testable instructions over vague descriptions. “Keep answers under three sentences unless I ask for detail” is clearer than “be concise.” “Lead with the answer, then explain the reasoning” is clearer than “be helpful.”
If you have several preferences, put the most important ones first. If two preferences can conflict, explain the priority. For example: “Usually keep answers short, but be thorough for legal, financial, medical, or engineering risk.”
Use the current chat for one-time needs
Custom instructions act like persistent defaults. A specific request in the current message is the right place for temporary needs, such as “for this answer, use a table,” “draft this in a friendlier tone,” or “ignore my usual brevity preference and be exhaustive.”
How Bravo applies custom instructions
Custom instructions are preferences, not a separate mode or a replacement for the current request. Bravo applies them when they fit the task, and prioritizes the current message when you ask for something different in a specific conversation.
- They guide how answers are written, organized, and delivered. They do not change what your account can access or which features are available.
- They work best for stable preferences: tone, language, depth, formatting, file output, and how much context Bravo should assume.
- They are applied alongside normal quality requirements. Bravo still needs to be accurate, clear about uncertainty, and careful with time-sensitive or source-dependent claims.
- They may be set aside when following them would make an answer misleading, incomplete, or incompatible with the task.
- Keep sensitive or one-time details out of custom instructions. Put temporary requirements in the current chat instead.
Suggested template
Use this as a starting point, then delete anything that does not match your preferences.
Language and region: Use American English. Use MM/DD/YYYY dates. Tone: Be direct, low-fluff, and candid. Skip praise unless it is substantively useful. Response structure: Lead with the answer. Use bullets for comparisons and numbered lists for steps. Use tables when comparing 3+ options. Files: Put long drafts, reusable templates, cleaned datasets, or large tables in downloadable files. Depth: Assume I know TypeScript and AWS. Skip beginner explanations. Interaction: State assumptions and proceed unless the decision is genuinely blocked. When unsure: Say what you know, what you are assuming, and what would change your answer. Sources: Cite sources for factual claims when you look things up or use provided documents. Quality bar: Challenge weak reasoning and call out uncertainty clearly.
Theme color
You can change the app's accent color in Personalization. Pick from nine preset colors — the change applies instantly across the entire UI and syncs across tabs.
Changing font size
Open the menu (three-dot icon, top right) → “Zoom” row → pick 75% to 150%.
