This document details Lumo's web search capabilities and file handling system. These features enable Lumo to provide current information through web searches (when enabled) and process uploaded files with context-aware task suggestions. For general system overview and multi-model routing, see System Overview and Multi-Model Routing. For tier-based feature availability, see Product Tiers and Platform Availability.
This page documents two distinct but complementary capabilities in Lumo:
Both systems are designed to extend Lumo's capabilities while maintaining user control and providing contextually appropriate assistance.
Lumo's web search functionality is controlled by a user-facing toggle button, creating a binary state system that determines whether real-time information retrieval is available during a conversation.
Sources: Open Source prompts/Lumo/Prompt.txt171-172
The toggle state is exposed to Lumo through the system context as The user has access to a "Web Search" toggle button to enable web search. The current value is: OFF. or ON.
| Feature | Lumo Free ($0) | Lumo Plus ($12.99/mo) |
|---|---|---|
| Web Search Toggle | ❌ Not Available | ✓ Available |
Tool: web_search | ❌ Disabled | ✓ Enabled |
| Suggestion Behavior | Recommend upgrading | Suggest enabling toggle |
Sources: Open Source prompts/Lumo/Prompt.txt68-69
Lumo evaluates user queries against specific criteria to determine when web search tools should be invoked. This decision tree operates only when the toggle is enabled.
Sources: Open Source prompts/Lumo/Prompt.txt27-36
When the web_search tool is invoked, Lumo follows these operational requirements:
| Guideline | Implementation |
|---|---|
| Call Timing | Immediately when criteria are met |
| Query Formulation | Use specific, targeted queries |
| Source Attribution | Always cite sources in response |
| Technical Hiding | Never show technical details or JSON to users |
Sources: Open Source prompts/Lumo/Prompt.txt39-43
The system is designed with a principle of preferring tool calls over outdated information: "In case you are unsure, prefer calling a tool than giving outdated information."
Sources: Open Source prompts/Lumo/Prompt.txt162
Lumo's file handling begins with a specific recognition pattern that identifies uploaded files in the conversation context.
Files appear in Lumo's context using a structured format:
Filename: [filename] File contents: ----- BEGIN FILE CONTENTS ----- [content] ----- END FILE CONTENTS -----
Sources: Open Source prompts/Lumo/Prompt.txt48-49
This format provides clear delimiters that enable Lumo to distinguish file content from conversational text, preventing file content from being misinterpreted as user instructions.
Sources: Open Source prompts/Lumo/Prompt.txt54-57
Lumo provides context-aware task suggestions based on the detected file type, offering users immediate actionable options.
When a CSV file is detected, Lumo suggests tasks in the data analysis domain:
| Task Category | Specific Suggestions |
|---|---|
| Data Analysis | Statistical analysis of columns |
| Statistical Summaries | Mean, median, mode, standard deviation |
| Pattern Identification | Trend detection, correlation analysis |
| Anomaly Detection | Outlier identification, data quality checks |
Sources: Open Source prompts/Lumo/Prompt.txt55
For PDF and text documents, Lumo focuses on content understanding and transformation:
| Task Category | Specific Suggestions |
|---|---|
| Summarization | Executive summary, key points extraction |
| Information Extraction | Named entity recognition, data extraction |
| Q&A | Document-based question answering |
| Translation | Language translation of content |
| Action Items | Todo extraction, meeting notes processing |
Sources: Open Source prompts/Lumo/Prompt.txt56
Code files trigger software development-oriented task suggestions:
| Task Category | Specific Suggestions |
|---|---|
| Review | Code quality assessment, best practices |
| Explanation | Line-by-line or function-level explanation |
| Debugging | Error identification, fix suggestions |
| Improvement Suggestions | Performance optimization, refactoring |
| Documentation | Comment generation, README creation |
Sources: Open Source prompts/Lumo/Prompt.txt57
Lumo follows a structured four-step response pattern when a file is detected, ensuring consistent user experience and clear communication of capabilities.
Sources: Open Source prompts/Lumo/Prompt.txt59-63
The four-step pattern is defined as:
Acknowledge: "I can see you've uploaded [filename]..."
Describe observations including limitations
Offer 2-3 specific relevant tasks
Ask what they'd like to focus on
Sources: Open Source prompts/Lumo/Prompt.txt59-63
The system enforces several critical requirements for both web search and file handling:
Critical Note: "Web search only available when enabled by user. If disabled but needed, suggest: 'I'd recommend enabling Web Search for current information on this topic.'"
Sources: Open Source prompts/Lumo/Prompt.txt37-43
Critical Note: "Always acknowledge file detection and offer relevant tasks based on file type."
Sources: Open Source prompts/Lumo/Prompt.txt52
Both web search and file handling integrate with Lumo's broader tool architecture.
The system declares available tools in context:
The list of tools you can use is:
- "proton_info"
Do not attempt to call a tool that is not present on the list above!!!
Sources: Open Source prompts/Lumo/Prompt.txt164-167
Note that web_search is dynamically added to this list when the Web Search toggle is enabled and the user has Lumo Plus tier.
| Condition | Action |
|---|---|
| Query answerable without tools | Reply directly without calling tool |
| Query requires current information | Prefer calling tool over giving outdated information |
| Toggle OFF but needs web search | Suggest enabling toggle |
| Tool not in available list | Do not attempt to call |
| Uncertain about information | Prefer tool call |
Sources: Open Source prompts/Lumo/Prompt.txt160-172
Lumo's web search and file handling systems demonstrate a user-centric design philosophy:
Both systems prioritize user control (toggle for web search), transparency (four-step file response pattern), and appropriate tool usage (preferring current information when uncertain).
Refresh this wiki