Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.gainable.dev/llms.txt

Use this file to discover all available pages before exploring further.

​
What is the Copilot component?

The Copilot is rendered with the <wy-copilot> component. You can embed it on any page of a Gainable app. Each instance is linked to one configured Copilot, so you can place several across the app, each connected to a different one.
For example, a sales Copilot on the deals page and a support Copilot on the tickets page. They share the underlying chat component but have different names, instructions, knowledge, and data access.

​
Adding a Copilot to a page

Describe where you want the Copilot and which one it should use: 
Add the Sales Coach Copilot to the deals page.

Put a chat panel on the support dashboard
using the Support Assistant Copilot.

Add Copilots to each main page:
- Deals page: Sales Coach
- Support page: Support Assistant
- HR page: HR Helper

​
What users see

When a Copilot is placed on a page, users see:
  • Name and description in the chat header
  • Conversation starters as clickable buttons to begin
  • Message input for typing questions
  • Chat responses with formatted text, lists, and data from MCP and knowledge

​
Capabilities

The embedded Copilot inherits all capabilities from its configuration:
CapabilityDescription
ChatNatural language conversation
Data access (MCP)Read, update, and insert app data through the MCP Server
Knowledge queriesReference uploaded documents from the Copilot’s knowledge base
Web searchSearch the web if enabled
Conversation startersPre-defined prompts shown as buttons

​
Placement patterns

​
Specific page placement

Place a Copilot on the page where it’s most relevant: 
Add the Sales Coach Copilot to the deals page.

​
Multiple pages, same Copilot

Use the same Copilot on several pages: 
Add the Support Assistant Copilot to both the
tickets page and the customer detail page.

​
Different Copilots per page

Match the Copilot to the page context: 
Add Copilots:
- Deals page → Sales Coach
- Tickets page → Support Assistant
- Dashboard → Analytics Helper

​
Copilot vs team chat

The Copilot and team chat serve different purposes:
CopilotTeam chat
PurposeConversational assistant for usersHuman-to-human messaging
Powered byGaia CopilotWeavy collaboration
RespondsGaia, with data accessOther team members
Best forQuestions, lookups, guidanceDiscussions, decisions, updates
Data accessQueries app data via MCP ServerNo direct data access
You can have both on the same page. Use team chat for human collaboration and the Copilot for AI-assisted data lookups and guidance.

​
Copilot vs Autopilot

The Copilot is reactive. The user asks; it answers. Autopilot is the user-facing surface for Gaia Autopilot, which run on their own and draft work for approval. The two are designed to live side by side:
  • The Copilot answers a sales rep’s question in chat.
  • Autopilot lands the same rep’s “stalled deal” follow-up draft in their inbox before they ask.

​
Full end-to-end example

Here’s a complete prompt that builds an app, configures a Copilot, and embeds it: 
Build a CRM with:
- Companies (name, industry, size)
- Contacts (name, email, phone, linked to company)
- Deals (name, amount, status, linked to company and contact)
- Dashboard with pipeline value and deals by status chart

Create a Sales Coach Copilot that:
- Helps reps find deals and contacts
- Can query all CRM data
- Uses a friendly, encouraging tone
- Has conversation starters:
  "Show my open deals"
  "Deals closing this month"
  "Find contacts at a company"
  "Pipeline summary"

Add the Sales Coach Copilot to the deals page.
This single prompt creates the app, configures the Copilot with data access, and embeds it on the deals page.

​
Best practices

Put a Copilot on pages where users are likely to have questions or need to look up data. A deals page Copilot is more useful than one on a simple settings page.
If you have multiple Copilots, use ones that are relevant to each page. A sales Copilot on the deals page, a support Copilot on the tickets page.
Good conversation starters show users what the Copilot can do. Include starters that demonstrate its key capabilities.
Copilots work alongside team chat, kanban boards, dashboards, and other features. They add conversational AI without replacing existing collaboration tools.

​
Learn more

Configuring a Copilot

Set up the Copilot behind the chat

Data access

Connect to app data via MCP

Knowledge bases

Add document references

Collaboration

Team chat and other collaboration features

Autopilot

The proactive side, where Agents draft work for approval