Built-in Search Engines
Ora Browser comes with pre-configured search engines, each with multiple aliases for quick access.General Search Engines
Aliases:
google, goo, g, searchDefault search engine with auto-suggestionsDuckDuckGo
Aliases:
duckduckgo, ddg, duckPrivacy-focused searchBing
Aliases:
bing, b, microsoftMicrosoft’s search engineKagi
Aliases:
kagi, kgPremium ad-free searchAI Chat Engines
ChatGPT
Aliases:
chat, chatgpt, gpt, cgpt, openai, chaOpenAI’s ChatGPTClaude
Aliases:
claude, cl, cla, anthropicAnthropic’s Claude AIGemini
Aliases:
gemini, gem, bard, google ai, gaiGoogle’s Gemini AIPerplexity
Aliases:
perplexity, perplex, pplx, ppl, perAI-powered answer engineGrok
Aliases:
grok, gr, groX’s AI assistantMeta AI
Aliases:
meta ai, meta, llama, facebook ai, maiMeta’s AI assistantCopilot
Aliases:
copilot, microsoft copilot, bing chat, ms copilotMicrosoft CopilotGitHub Copilot
Aliases:
github copilot, gh copilot, github ai, ghcGitHub’s AI assistantSpecialized Search
YouTube
Aliases:
youtube, you, youtu, yo, ytSearch YouTube videosAliases:
reddit, r, rd, rdit, redSearch Reddit discussionsX (Twitter)
Aliases:
x, x.com, twitter, tw, twtr, twit, twitt, twitteSearch posts on XT3Chat
Aliases:
t3chat, t3, t3c, tchatT3 AI Chat platformUsing Search Aliases
Search aliases allow you to quickly switch between search engines without changing your default.Examples
- AI Search
- Traditional Search
Search Engine Configuration
The search engine system is built with flexibility in mind:Setting Default Search Engine
You can set different default search engines for different containers (like Personal, Work, etc.)
Custom Search Engines
Add your own custom search engines with personalized aliases.Adding a Custom Engine
Configure Engine
Fill in the required fields:
- Name: Display name for the engine
- Search URL: URL with
{query}placeholder - Aliases: Space-separated list of shortcuts
- Is AI Chat: Mark if it’s an AI chat service
Custom Engine Example
URL Template Format
When creating custom search engines, use{query} as the placeholder:
{query} placeholder is automatically replaced with URL-encoded search terms:
Auto-Suggestions
Some search engines support auto-suggestions as you type.Enabled Engines
Currently, Google provides auto-suggestions:How Suggestions Work
Container-Specific Search Engines
Ora Browser supports different default search engines per container.Use Cases
Personal Container
Use Google or DuckDuckGo for general web searches
Work Container
Use Perplexity for research-oriented queries
Development Container
Set Google as default with quick access to docs
Creative Container
Use AI chats like Claude or ChatGPT for creative work
Configuration
Container-specific settings override the global default. This allows you to have different search behaviors in different browsing contexts.
AI Chat Engines
AI chat engines are specially marked and can have separate defaults:AI vs Traditional Search
| Feature | Traditional Search | AI Chat |
|---|---|---|
| Purpose | Find existing web pages | Generate responses |
| Results | Links to websites | Conversational answers |
| Use Case | Research, navigation | Questions, creative tasks |
| Examples | Google, DuckDuckGo | ChatGPT, Claude |
Search Engine Management
Editing Custom Engines
- Navigate to Settings → Search → Custom Engines
- Click on the engine you want to edit
- Modify the fields
- Click Save Changes
Deleting Custom Engines
- Open Settings → Search → Custom Engines
- Find the engine you want to remove
- Click the Delete button
- Confirm the deletion
Tips & Best Practices
Use Short Aliases
Use Short Aliases
Create memorable 2-3 character aliases for frequently used engines:
gfor Googlegptfor ChatGPTytfor YouTubeghfor GitHub search
Organize by Context
Organize by Context
Set different default engines per container:
- Work: Perplexity for research
- Personal: Google for general use
- Development: GitHub Copilot for coding questions
Leverage AI Engines
Leverage AI Engines
Use AI chat engines for:
- Explaining complex topics
- Generating content
- Coding assistance
- Creative brainstorming
Test Custom Engines
Test Custom Engines
After adding a custom engine:
- Test it with a simple query
- Verify the URL format is correct
- Check that aliases work as expected
Troubleshooting
Alias Not Working
- Ensure the alias doesn’t conflict with existing ones
- Check for typos in the alias spelling
- Restart Ora Browser if needed
Custom Engine Not Appearing
- Verify the search URL includes
{query}placeholder - Check that the engine was saved successfully
- Look for error messages in Settings
Wrong Search Results
- Confirm the correct engine is being used
- Check container-specific settings
- Verify the search URL is properly formatted
