The lua 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.
lua features
New in v2.6.0: Centralized control over agent features with instant enable/disable and context customization!
# List all featureslua features list# Enable a featurelua features enable --feature-name rag# Disable a featurelua features disable --feature-name rag# View feature detailslua features view --feature-name webSearch
Real-time internet search capability for accessing current information. This feature uses Google Search to synthesize answers to queries and provide source links.
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.
Capabilities:
Search the web in real-time
Retrieve up-to-date information and current events
Access domain-specific data indexed by Google
Return synthesized answers with source citations
Best for: Research agents, information lookup, real-time data needsHow to Enable:
Enabled by default for all agents.
Can be toggled on or off by running lua features enable --feature-name webSearch or lua features disable --feature-name webSearch in the CLI.
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
Best for: Sales, lead capture, support intake, or any workflow that needs structured data from conversations
? What would you like to do? View feature details? Select feature: ✅ Knowledge Search (RAG)============================================================Feature: Knowledge Search (RAG)============================================================Name: ragStatus: ✅ ActiveContext/Instructions:Search the knowledge base for information.Use categories: FAQ, policies, instructions.Always cite sources when providing information.Press Enter to continue...
Use for: Understanding what a feature does before enabling
Enable, disable, or update a feature
? What would you like to do? Manage a feature? Select feature: ❌ WebSearch? What would you like to do with "WebSearch"? › Activate feature Update context/instructions Update both status and context Back to main menu
Use for: Changing feature settings
Reload features from server
? What would you like to do? Refresh list🔄 Refreshing features...✅ Features refreshed successfully
Use for: Getting latest feature status after external changes
$ lua features? What would you like to do? Manage a feature
2
Choose Feature
? Select feature: ❌ WebSearch
3
Activate
? What would you like to do? Activate feature⚠️ This will enable "WebSearch" for your agent.? Are you sure? Yes🔄 Updating feature...✅ Feature "WebSearch" activated successfully
$ lua features? What would you like to do? Manage a feature? Select feature: ✅ Knowledge Search (RAG)
2
Deactivate
? What would you like to do? Deactivate feature⚠️ This will disable "Knowledge Search (RAG)" for your agent.? Are you sure? Yes🔄 Updating feature...✅ Feature "Knowledge Search (RAG)" deactivated successfully
Customize how your agent uses a feature by editing its instructions.
1
Select Feature
$ lua features? What would you like to do? Manage a feature? Select feature: ✅ Knowledge Search (RAG)
2
Update Context
? What would you like to do? Update context/instructionsOpening editor to modify feature context...
Your system editor opens with the current context:
Search the knowledge base for information.Use categories: FAQ, policies, instructions.Always cite sources when providing information.
3
Edit and Save
Modify the instructions:
Search the knowledge base for product information.Categories available:- FAQ: Common customer questions- policies: Company policies and procedures- instructions: How-to guides and documentationGuidelines:- Always cite sources with document names- If information is not found, say so clearly- Suggest related topics when helpful- Keep responses concise but complete
Save and exit your editor.
4
Confirm
? Do you want to save these changes? Yes🔄 Updating feature context...✅ Context updated successfully
Update both feature status and context in one operation.
1
Select Feature
$ lua features? What would you like to do? Manage a feature? Select feature: ❌ Create Inquiry forms
2
Choose Batch Update
? What would you like to do? Update both status and context? New status for "Create Inquiry forms": › Enable Disable
3
Edit Context
Your editor opens for context editing…Save your changes.
4
Review and Confirm
Summary of changes:- Status: Inactive → Active- Context: Updated? Do you want to apply these changes? Yes🔄 Updating feature...✅ Feature "Create Inquiry forms" updated successfully
Enable features for internal knowledge and optional intake:
$ lua features# Enable Knowledge Search→ Manage: ❌ Knowledge Search → Activate✅ RAG enabled# Optional: inquiry forms for structured support intake (visible in Admin Dashboard)→ Manage: ❌ Inquiry Forms → Activate✅ Inquiry forms enabled# Disable Web Search if you only want org-approved sources→ Manage: ✅ WebSearch → Deactivate✅ WebSearch disabled# Result: Agent focused on your knowledge base (and optional forms)
Features Active:
✅ Knowledge Search - Access help docs and policies
✅ Inquiry Forms (optional) - Structured intake or follow-up
❌ Web Search - Not needed for internal-only support
$ lua features# Enable RAG as primary source→ Manage: ❌ Knowledge Search → Activate→ Update context: "Primary information source. Always check here first."✅ RAG enabled# Enable Web Search as backup→ Manage: ❌ Web Search → Activate→ Update context: "Use only when RAG doesn't have the answer."✅ WebSearch enabled# Disable inquiry if you only need read-only answers→ Manage: ✅ Inquiry Forms → Deactivate✅ Focused on information retrieval only
✅ Good:"Use this feature to search our internal knowledge basefor product documentation, FAQs, and policies."❌ Bad:"Search stuff."
When to Use
Specify appropriate situations:
✅ Good:"Use inquiry forms when:- You need structured lead or intake data- The user agrees to submit a form- Follow-up will happen in the Admin DashboardDo NOT use inquiry forms for:- Simple FAQs already in the knowledge base- One-off questions that RAG can answer"❌ Bad:"Use forms sometimes."
Guidelines and Rules
Set boundaries and expectations:
✅ Good:"When using web search:1. Use for current events and real-time data2. Verify information with multiple sources3. Cite sources in your response4. If search fails, inform user honestly5. Don't rely on search for company-specific info"❌ Bad:"Search the web when needed."
Examples
Provide concrete examples:
✅ Good:"Example inquiry form fields:- Name (required)- Email (required)- Company name- Company size (1-10, 11-50, 51-200, 201+)- Budget range- Timeline for decision- Additional notes"❌ Bad:"Collect customer information."
Search the internal knowledge base for information.Categories available:- FAQ: Frequently asked questions- policies: Company policies and procedures- instructions: Step-by-step guides- products: Product documentationSearch best practices:1. Try specific queries first2. Use category filters when possible3. Always cite the document source4. If not found, try broader terms5. Suggest related topics when helpfulWhen information is not found:- Say so clearly and honestly- Offer to escalate if needed- Suggest alternative resources
Use web search for real-time, current information.Appropriate for:- Current events and news- Real-time data (stock prices, weather)- Recent industry updates- Public information not in knowledge baseNot appropriate for:- Company-specific information (use RAG)- Customer data or internal systems- Proprietary information- Historical company informationAlways:- Verify information quality- Cite sources with URLs- Cross-reference when possible- Note the date of information
Create inquiry forms to collect lead information.Standard fields to include:- Full name (required)- Email address (required)- Phone number (optional)- Company name- Company size- Industry- Budget range- Timeline- Specific needs/requirementsQualification questions:- What problem are you trying to solve?- Have you used similar solutions?- What's your timeline for implementation?- Who else is involved in the decision?After form submission:- Thank the prospect- Set expectations for response time- Offer immediate resources if available
# 1. Configure features for your agent typelua features# 2. Enable necessary features→ Activate relevant features# 3. Customize each feature's context→ Update context for each enabled feature# 4. Test with chatlua chat# Test each feature's behavior# 5. Iterate based on resultslua features→ Adjust context as needed
# 1. Enable test featurelua features→ Activate feature→ Add initial context# 2. Test in sandboxlua chat# Try using the feature# 3. Review and refine# Based on test results# 4. Update contextlua features→ Update context with improvements# 5. Test againlua chat# Verify improvements# 6. Deploy when satisfiedlua push skilllua deploy
# 1. Review current featureslua features→ View all features and their usage# 2. Disable unused features→ Deactivate features not being used# Improves performance and reduces complexity# 3. Optimize active features→ Update context for better behavior→ Add examples and guidelines# 4. Test optimizationlua chat# Verify improvements# 5. Monitor results# Check conversations in admin dashboardlua admin
# 1. Enable featureslua features→ Enable: rag, inquiry# 2. Update persona to mention capabilitieslua persona sandbox# Add: "I can search our knowledge base and collect details via inquiry forms"# 3. Test togetherlua chat# 4. Deploy bothlua push personalua push skill
# 1. Enable features you need (e.g. RAG + inquiry)lua features→ Activate: rag# 2. Add or extend tools in your skill projectvim src/tools/MyTool.ts# 3. Testlua test# 4. Deploylua push skill
# Development: Enable all features for testinglua features→ Activate: All features# Production: Enable only needed featureslua features→ Activate: rag, inquiry→ Deactivate: webSearch
# ✅ Good: Start with essentialslua features→ Enable: rag only (add webSearch or inquiry when needed)# Test and add more as needed# ❌ Bad: Enable everything "just in case"→ Enable: All features# Adds complexity and potential confusion
Write Clear Context
Detailed instructions improve results:
# ✅ Good: Detailed context"Use inquiry forms for technical escalations.Include: problem summary, steps to reproduce,customer impact, and priority level."# ❌ Bad: Vague context"Use forms for problems."
Test After Changes
Always test feature changes:
lua features→ Update contextlua chat# Immediately test the changes# Verify behavior matches expectations
Document Your Setup
Keep notes on feature configuration:
# In README.md or docs## Active Features- Knowledge Search (rag): Internal docs only- Web Search: Disabled (use internal knowledge)- Inquiry Forms: Disabled (not collecting structured data)
Review Regularly
Audit features periodically:
# Monthly reviewlua features→ Check active features→ Disable unused features→ Update context based on learnings→ Test improvements