Overview
Thelua features command provides an interactive interface for managing your AI agent’s capabilities: Knowledge Search (rag), Web Search (webSearch), and Inquiry Forms (inquiry).
For what each feature does and how it fits with resources and the Admin Dashboard, see Features.
Centralized control over agent features with instant enable/disable and context customization!
Non-Interactive Mode
View Features
See all available features and their status
Enable/Disable
Activate or deactivate features instantly
Update Context
Customize feature instructions
Batch Updates
Update status and context together
Available Features
Knowledge Search (rag)
RAG-based knowledge base search for retrieving information from your documentation.
Capabilities:
- Semantic search across knowledge base
- Category-based search (FAQ, policies, instructions)
- Document retrieval with citations
- Contextual information retrieval
Web Search (webSearch)
Real-time internet search capability for accessing current information, with source links attached to the response.
Search runs one of two ways depending on your agent’s model:
- Native search — models with a built-in, cited web search path (OpenAI, Anthropic, Google/Gemini, xAI, and Zhipu AI’s GLM models) use the provider’s own search tool.
- Assisted search — every other model falls back to Lua’s own web-search tool.
Important: The Web Search feature is not a web scraper. It cannot navigate to or read specific URLs directly, and it does not scrape content from individual or bulk pages.
- Search the web in real-time
- Retrieve up-to-date information and current events
- Return synthesized answers with source citations
- Enabled by default for new agents, like the other built-in features. Native search can add latency and per-search cost on some models, so disable it if your agent doesn’t need it.
- Can be toggled on or off by running
lua features enable --feature-name webSearchorlua features disable --feature-name webSearchin the CLI.
Inquiry Forms (inquiry)
Define conversational forms so the agent can collect structured answers from users. Submissions are visible in the Admin Dashboard. Inquiry forms are general-purpose (leads, intake, feedback, or support-style flows)—they replaced the older standalone “support tickets” feature.
Capabilities:
- Generate inquiry forms from your form definitions
- Collect and track submissions
- Add comments and manage follow-up in the dashboard
Quick Start
1
Run Command
2
View Features
See all available features with their current status:
3
Manage Features
Select what you want to do:
- View feature details
- Manage a feature (enable/disable/update)
- Refresh list
Main Menu Actions
- View Feature Details
- Manage a Feature
- Refresh List
See complete information about a featureUse for: Understanding what a feature does before enabling
Managing Features
Enable a Feature
1
Select Manage
2
Choose Feature
3
Activate
Disable a Feature
1
Select Feature
2
Deactivate
Update Feature Context
Customize how your agent uses a feature by editing its instructions.1
Select Feature
2
Update Context
3
Edit and Save
Modify the instructions:Save and exit your editor.
4
Confirm
Batch Update (Status + Context)
Update both feature status and context in one operation.1
Select Feature
2
Choose Batch Update
3
Edit Context
Your editor opens for context editing…Save your changes.
4
Review and Confirm
Use Cases
Customer Support Agent
Enable features for internal knowledge and optional intake:- ✅ Knowledge Search - Access help docs and policies
- ✅ Inquiry Forms (optional) - Structured intake or follow-up
- ❌ Web Search - Not needed for internal-only support
Sales Agent
Configure for lead generation and product information:- ✅ Inquiry Forms - Lead generation
- ✅ Knowledge Search - Product information
- ✅ Web Search - Market research
Information Agent
Optimize for information retrieval:- ✅ Knowledge Search - Primary source
- ✅ Web Search - Supplementary data
- ❌ Inquiry Forms - No data collection needed
Customizing Feature Context
Writing Effective Context
Good feature context should include:Clear Purpose
Clear Purpose
Explain what the feature is for:
When to Use
When to Use
Specify appropriate situations:
Guidelines and Rules
Guidelines and Rules
Set boundaries and expectations:
Examples
Examples
Provide concrete examples:
Context Templates
Knowledge Search Template
Web Search Template
Inquiry Forms Template
Complete Workflows
Initial Agent Setup
Feature Testing Workflow
Feature Optimization
Integration with Other Commands
Features + Persona
Coordinate features with persona:Features + Skills
Build skills that use platform features:Features + Environment
Different features per environment:Best Practices
Start Minimal
Start Minimal
Enable only features you need:
Write Clear Context
Write Clear Context
Detailed instructions improve results:
Test After Changes
Test After Changes
Always test feature changes:
Document Your Setup
Document Your Setup
Keep notes on feature configuration:
Review Regularly
Review Regularly
Audit features periodically:
Troubleshooting
Features not loading
Features not loading
Error: “Failed to fetch features”Solutions:
-
Verify authentication:
-
Check lua.skill.yaml has agentId:
-
Test API connection:
Context not saving
Context not saving
Problem: Editor opens but changes don’t saveSolutions:
- Make sure you save in editor (
:wqfor vim) - Confirm when prompted after editing
- Check for error messages
- Try again with refresh:
Feature not appearing in agent
Feature not appearing in agent
Problem: Enabled feature not available in chatSolutions:
-
Verify feature is active:
-
Refresh agent session:
- Check feature context is not empty
-
Redeploy if needed:
Cannot enable feature
Cannot enable feature
Error: “Feature update failed”Solutions:
- Check agentId is correct
- Verify API key has permissions
- Ensure feature name is valid
- Check network connection
- Try refreshing features list first
Editor not opening
Editor not opening
Problem: Context update doesn’t open editorSolutions:
-
Set EDITOR environment variable:
-
Add to shell config (~/.bashrc or ~/.zshrc):
-
Try different editor:
Requirements
- Authentication: Valid API key (
lua auth configure) - Project: Must be in skill directory with
lua.skill.yaml - Agent ID: Configuration must contain
agent.agentId - Permissions: API key must have agent management permissions
Related Commands
lua persona
Configure agent personality to work with features
lua chat
Test features in conversation
lua admin
View feature usage in admin dashboard
lua push skill
Deploy skills that use features
Next Steps
Features overview
What each feature does (rag, webSearch, inquiry)
Test Features
Use lua chat to test feature behavior
Build Skills
Create tools that leverage features
Configure Persona
Update persona to mention capabilities
Admin Dashboard
Monitor feature usage

