Configuring Your Employee
After hiring an AI employee, you can fine-tune their configuration at any time. This guide covers all configuration options and best practices.
The employee configuration page with all settings sections
Accessing Configuration
- Navigate to Employees in the sidebar (or press
GthenE) - Click on the employee you want to configure
- Click Edit or Configure button
Click on an employee card to access its configuration
Configuration Sections
1. Basic Information
| Field | Description |
|---|---|
| Name | Display name for your employee |
| Status | Current state (Running, Paused, etc.) |
| Template | Original template used (for reference) |
2. Model Configuration
Select which AI model powers your employee.
Model selection in employee configuration
| Factor | Description |
|---|---|
| Speed | Faster models respond more quickly |
| Capability | More capable models handle complex tasks better |
| Cost | Different models consume tokens at different rates |
Tip: You can change the model anytime. The change takes effect on the next response.
3. API Key Configuration
Your employee uses your included AI credits or your own API key.
API key configuration
Using Included Credits
Each employee slot includes AI credits (~16 million tokens per month). These are used automatically.
Using Your Own API Key
If you prefer to use your own API key:
- Go to Settings → API Keys
- Add your API key
- Select it in the employee configuration
Select or add API keys for your employee
4. Channels Configuration
Configure communication channels
Configure how users communicate with your employee. See Employee Channels for detailed setup.
Active Channels:
- Toggle channels on/off
- Update credentials anytime
- Test connection before saving
5. Tools Configuration
Enable capabilities for your employee.
Built-in tools and MCP server configuration
Built-in Tools
Web Search
| Provider | Cost | Quality | Setup Required |
|---|---|---|---|
| DuckDuckGo | Free | Good | None |
| Brave Search | Paid | Better | API key |
| Tavily | Paid | Best | API key |
Execution Tools
| Tool | Description |
|---|---|
| Exec | Run terminal commands in workspace |
| Cron | Schedule recurring tasks |
MCP Tools (Marketplace & Custom)
Manage installed MCP tools
Browse and install additional tools that integrate with external services:
- Marketplace Tools — Pre-configured, one-click install
- Custom Tools — Your own MCP server configurations
See Tools, MCP Servers & Skills for complete MCP documentation.
6. Skills Configuration
Skills define your employee's knowledge and behavior through markdown instructions.
Manage and edit employee skills
Skill Types
| Type | Description | Editable |
|---|---|---|
| Custom Skills | Your own instructions | Yes |
| Template Skills | Came with template | Yes |
| Marketplace Skills | From skill marketplace | No (read-only) |
Writing Effective Skills
Writing a customer support skill
# Customer Support Skill
## Your Role
You are a friendly customer support agent for [Company Name].
## Guidelines
- Always greet customers warmly
- Ask clarifying questions before providing solutions
- Escalate billing issues to human support
- Never share internal information
## Common Issues
### Password Reset
1. Verify customer identity
2. Send reset link to registered email
3. Confirm they received it
### Refund Requests
1. Check order status
2. If within 30 days, process refund
3. Otherwise, explain policy politelyReal-Time Updates
Configuration changes take effect immediately:
| Change Type | Effect |
|---|---|
| Model changes | Next response uses new model |
| Channel changes | Reconnects to updated channels |
| Tool changes | New tools available immediately |
| Skill changes | Synced to employee workspace |
Configuration Best Practices
Do's
| Practice | Why |
|---|---|
| Start simple | Add complexity as needed |
| Test regularly | Verify changes work as expected |
| Document skills | Clear instructions = better responses |
| Use specific skills | Focused skills work better than generic ones |
Don'ts
| Avoid | Why |
|---|---|
| Over-configure | Too many tools can confuse the employee |
| Share tokens | Each employee needs unique channel tokens |
| Ignore errors | Fix configuration issues promptly |
Saving and Validation
When you save configuration:
Configuration validation in progress
- Validation runs — System checks all required fields
- Token verification — Confirms no duplicate bot tokens
- Connection test — Verifies channel connectivity
- Sync to employee — Updates the running container
Common Validation Errors
| Error | Solution |
|---|---|
| "Bot token already in use" | Each employee needs a unique token |
| "Invalid API key" | Check key in Settings → API Keys |
| "Missing required field" | Fill in all required channel fields |
| "SMTP connection failed" | Verify email server settings |
| "MCP tool needs configuration" | Configure or disable the tool |
Example of a validation error with suggested fix
Configuration Templates
Save your configurations as templates for quick reuse:
Save configuration as a reusable template
- Configure an employee exactly how you want
- Click Save as Template (if available)
- Use this template when hiring new employees
Quick Reference
| Section | What to Configure |
|---|---|
| Basic Info | Name and status |
| API Key | Use included credits or your own key |
| Channels | Telegram, Discord, Slack, WhatsApp, Email |
| Tools | Web search, Exec, Cron, MCP servers |
| Skills | Behavior instructions in markdown |
Next Steps
- Employee Channels — Detailed channel setup
- Tools, MCP Servers & Skills — Extend capabilities
- Managing Employees — Day-to-day management
What did you think of this content?