Skip to main content
Assistants are custom AI personas that you configure to behave in specific ways. Each assistant can have its own personality, instructions, knowledge sources, and model settings. Think of them as specialized team members — one might handle customer support, another might review code, and a third might help write marketing copy.

​
Creating an Assistant

1

Open the Assistants page

Click Assistants in the sidebar.
2

Create a new assistant

Click New Assistant to open the creation form.
3

Configure the assistant

Fill in the details described below, then save.

​
Configuration Options

  • Name — A clear, descriptive name (e.g., “Customer Support Bot” or “Code Reviewer”)
  • Description — A brief summary of what the assistant does, visible to workspace members
  • System Prompt — The instructions that define how the assistant behaves
  • Model — The AI model the assistant uses (e.g., Grok-2, GPT-4o)
  • Temperature — Controls creativity. Lower values produce more focused, deterministic responses. Higher values produce more creative, varied responses.
  • Max Tokens — The maximum length of responses the assistant can generate

​
Writing Effective System Prompts

The system prompt is the most important part of your assistant’s configuration.
Instead of “You are a helpful assistant,” try “You are a senior customer support agent for a SaaS company. You help users troubleshoot billing issues, account access problems, and feature questions.”
Specify whether the assistant should be formal or casual, concise or detailed. For example: “Respond in a friendly, professional tone. Keep answers under 200 words unless the user asks for more detail.”
Tell the assistant what it should and should not do. For example: “Never make up information. If you do not know the answer, say so and suggest the user contact support.”
Include example interactions in the system prompt to show the assistant exactly how you want it to respond.

​
Visibility Settings

Visibility controls who in your workspace can see and use the assistant.
VisibilityWho Can Access
PublicAll workspace members
WorkspaceActive workspace members only
PrivateCreator, admins, and explicitly granted users
Start with Workspace visibility while testing. Switch to Public once you are confident in the assistant’s performance.

​
Connecting to Knowledge

Assistants become much more useful with access to your organization’s knowledge:
  • Projects — Link one or more projects to give the assistant access to uploaded documents. The assistant searches these documents for relevant context when answering questions.
  • Knowledge Bases — Connect external knowledge bases for broader document retrieval.
See Projects and Knowledge Base for setup details.

​
Tool Configuration

Assistants can use external tools through MCP (Model Context Protocol) integrations:
  • Notion — Search and retrieve pages from your Notion workspace
  • GitHub — Search repositories, read issues and pull requests
  • More coming — Additional MCP providers are being added regularly
See Integrations for setup details.

​
Example Assistants

Customer Support Bot

Connect your FAQ documents and help articles. Set the system prompt to answer questions accurately and maintain a friendly tone.

Code Reviewer

Instruct the assistant to review code for bugs, security issues, and best practices. Use a lower temperature for consistent feedback.

Content Writer

Configure a higher temperature for creative responses. Provide brand guidelines in the system prompt.

Sales Assistant

Upload product documentation and pricing guides. The assistant can answer prospect questions and draft follow-up emails.
The number of assistants you can create and the models available may depend on your workspace plan.