РусскийRUEnglishEN

User Context

User context is background information about you that you set once in the dashboard. The assistant takes it into account for every response throughout the session.

Why it matters

Without context the assistant answers "in a vacuum": if you haven't told it that you're a mid-level Python developer currently interviewing at a FAANG company, it won't tailor the response to your level and goal.

Context lets you:

  • Reference facts about yourself without repeating them in every question.
  • Set the style and depth of answers for your role.
  • Store key facts about your product, team, or project.

Where to configure it

Open the web dashboard → Profile → User context.

📸 [Screenshot: "User context" field in profile settings]

What to write

Context is free-form text. Write only what is useful for the assistant to know:

Examples of good context:

I'm a Senior Python developer, 7 years in the industry.
Currently interviewing for a position at an overseas company.
Focus: backend, microservices, Kubernetes.
Answer in English; technical terms can stay in English.

I'm a sales manager for a SaaS product targeting small businesses.
Product: CRM system, ~$500/month.
Target clients: small teams of 5–50, non-technical.
Answer concisely and with concrete arguments.

Difference from role prompt (Prompt Studio)

User context Role prompt (Prompt Studio)
Describes Who you are and your facts How the assistant should respond
Set in Profile Prompt Studio
Applied In all sessions In sessions with the selected template

Use both together: context supplies facts, the template sets style.

Common issues

Issue Recommendation
Context too long (thousands of words) Trim to 200–400 words — only the essentials
Trying to issue commands through context Context is facts, not instructions; use the template for commands
Outdated information Update the context when your role or project changes

Best practices

  • Write in first or third person — both work; pick whichever is more natural.
  • Specify the response language if it matters: "Answer in English" or "Отвечай по-русски".
  • Don't duplicate in context what's already in the knowledge base — it's stored more fully there.
  • Update the context when switching meeting types: one version for interviews, another for client calls.

Related articles