-
Notifications
You must be signed in to change notification settings - Fork 0
Agents Creating
This guide walks you through creating custom agents in GT AI OS step by step.
- You need appropriate permissions to create agents
- Understand what task the agent should accomplish
- Have a clear idea of the agent's personality and behavior
- Go to Agents in the sidebar
- Click the toggle to switch to Agent Configuration view (if in Favorites view)
- Click Create Agent
- The agent creation form opens
Fill in the required fields:
| Field | Required | Description | Example |
|---|---|---|---|
| Name | Yes | Clear, descriptive name | "Customer Support - Technical" |
| Description | Yes | What this agent does | "Helps users troubleshoot technical issues" |
| Category | Yes | Select or create a category | "Technical", "General", "Creative" |
| Tags | No | Keywords for filtering | "support", "technical", "help" |
Note: Categories are customizable - you can create new ones or use existing categories your organization has set up.
The system prompt is the most important part - it defines your agent's behavior.
Structure your prompt like this:
# Role
You are a helpful customer service agent for [Company].
# Responsibilities
- Answer questions about products and services
- Help resolve common technical issues
- Escalate complex problems to human support
# Communication Style
- Be professional and empathetic
- Use clear, simple language
- Provide step-by-step instructions when helpful
# Boundaries
- Don't make up information you don't know
- Don't discuss competitors negatively
- Redirect off-topic questions politely
Best practices for system prompts:
- Be specific about the agent's role and expertise
- Define the tone (formal, friendly, technical)
- List clear responsibilities
- Set boundaries on what the agent should and shouldn't do
- Include examples if helpful
Configure how the AI generates responses:
| Setting | Range | Description |
|---|---|---|
| Temperature | 0.0-2.0 | Controls creativity vs. consistency |
Temperature guide:
- 0.0-0.3: Consistent, factual responses (technical support, Q&A)
- 0.4-0.7: Balanced (general use, default is 0.7)
- 0.8-2.0: Creative, varied responses (brainstorming, writing)
Give your agent specialized knowledge:
- In the Datasets section, use the search box to find datasets
- Check the boxes next to datasets you want to attach
- Use Select All or Clear All for bulk selection
- Selected datasets appear as badges above the list
Tips:
- More datasets isn't always better - keep it focused
- Update dataset attachments when your documents change
- Test retrieval quality after attaching
Add quick-access conversation starters that appear as buttons in the chat:
- Find the Easy Buttons section
- Click Add Easy Button to create a new button
- Enter the prompt text that will be sent when clicked
- Add up to 10 easy buttons
Examples:
- "Summarize this document"
- "Explain this in simple terms"
- "Help me draft an email about..."
Control who can access your agent:
| Visibility | Who Can Access | Best For |
|---|---|---|
| Individual | Only you | Personal agents, development |
| Team | Selected team members | Team-specific workflows |
| Organization | All users in your organization | Company-wide tools |
Note: Only Tenant Admins can set Organization visibility. Once set, all users can access the agent. See Sharing Agents for details.
When selecting Team visibility:
- Choose which teams should have access
- Each team's members will see the agent
- Review all your settings
- Click Create Agent
- The agent is created and available immediately
- Click on the agent to start a test conversation
- Iterate based on results
After creating:
- Try the main use cases you designed for
- Test edge cases and unexpected inputs
- Verify the tone matches your intentions
- Check that datasets are being used correctly
- Note any issues in responses
- Edit the agent to adjust
- Test again
- Repeat until satisfied
Be explicit about:
- What the agent should do
- How it should communicate
- What it should avoid
- How to handle edge cases
- Begin with basic functionality
- Test thoroughly before adding complexity
- Iterate based on actual usage
- Attach only relevant datasets
- Keep dataset content focused
- Update datasets when information changes
- Try unexpected inputs
- Test boundary conditions
- Verify error handling
| Mistake | Problem | Solution |
|---|---|---|
| Vague system prompt | Inconsistent responses | Be specific about role and behavior |
| Too many datasets | Slow, unfocused retrieval | Only attach what's needed |
| Wrong temperature | Responses too rigid or chaotic | Match setting to use case |
| No testing | Sharing broken agents | Always test before sharing |
| No boundaries | Off-topic responses | Define what agent shouldn't do |
After creating your agent:
- Configure advanced settings
- Share with your team
- Monitor usage and gather feedback