Overview
Praxos provides two levels of web browsing capabilities: simple HTML reading for static sites and AI-powered browsing for JavaScript-heavy dynamic sites.Simple Web Reading
read_webpage_content
Fast, efficient reading of static HTML pages. Use Cases:- News articles
- Blog posts
- Documentation pages
- Simple product pages
- Any content-first website
- Speed: 2-5 seconds
- Cost: Minimal (no LLM calls)
- JavaScript: Not supported
- Interaction: Read-only
AI-Powered Browsing
browse_website_with_ai
Intelligent browser automation using Playwright and AI. Use Cases:- JavaScript-rendered content
- Dynamic web applications
- Form submissions
- Multi-step navigation
- Complex site interactions
- Content behind interactions
- Speed: 30-60 seconds
- Cost: ~$0.01-0.05 per task
- JavaScript: Full support
- Interaction: Clicks, forms, navigation
How AI Browsing Works
User Experience Pattern
Praxos ALWAYS sends an intermediate message before starting AI browsing to set expectations.
- User makes request involving browsing
- Praxos: “I’m browsing that website now, about 30 seconds…”
- [Browser automation happens]
- Praxos: [Final response with information]
Capabilities
Navigation
- Load pages - Go to any URL
- Click links - Follow links and buttons
- Form submission - Fill forms and submit
- Scrolling - Scroll to load more content
- Back/Forward - Navigate history
Interaction
- Input fields - Type into text boxes
- Dropdowns - Select from menus
- Checkboxes - Toggle options
- Buttons - Click any clickable element
- Hover - Trigger hover effects
Data Extraction
- Text content - Extract visible text
- Structured data - Parse tables, lists
- Metadata - Titles, descriptions, prices
- Images - Alt text and descriptions
- Links - Extract URLs
Multi-Step Tasks
Configuration
Tool Parameters
Environment Setup
Resource Requirements
- Memory: ~200-500MB per execution
- CPU: Moderate usage
- Network: Required
- Time: 30-60 seconds average
Comparison
| Feature | read_webpage_content | browse_website_with_ai |
|---|---|---|
| Speed | 2-5 seconds | 30-60 seconds |
| JavaScript | ❌ No | ✅ Yes |
| Forms/Interaction | ❌ No | ✅ Yes |
| Multi-page | ❌ No | ✅ Yes |
| Cost | Free | ~$0.01-0.05 |
| User notification | Not needed | Required |
| Use case | Static sites | Dynamic sites |
Best Practices
When to Use Simple Reading
- Static content sites
- Speed is priority
- No interaction needed
- Content loads without JavaScript
When to Use AI Browsing
- JavaScript-rendered content
- Need to interact with forms
- Multi-step navigation required
- Content behind clicks/scrolls
Task Descriptions
Write clear, specific tasks: Good:Limitations
Website Restrictions
Some sites block automation:- CAPTCHAs
- Bot detection systems
- Rate limiting
- Cloudflare protection
Performance
- Not suitable for real-time needs
- Resource intensive
- May timeout on very slow sites
Accuracy
- AI may misinterpret complex layouts
- Depends on clear task descriptions
- May need multiple attempts
Troubleshooting
Browser Timeout
Problem: Task takes too long Solutions:- Increase
max_stepsparameter - Simplify the task
- Try a more specific URL
- Check site isn’t blocking automation
Playwright Not Found
Problem:playwright executable not found
Solution:
Memory Issues
Problem: Out of memory errors Solutions:- Increase pod/container memory
- Limit concurrent browsing tasks
- Use simple reading when possible
Navigation Failures
Problem: Can’t find elements or navigate Solutions:- Check URL is correct
- Verify site structure hasn’t changed
- Try more specific task description
- Check site isn’t behind login
Advanced Usage
Screenshots (Future)
Vision model integration for:- Visual verification
- Layout understanding
- Image-based navigation
Session Persistence (Future)
Maintain browser sessions:- Stay logged in
- Persist cookies
- Continue from previous state
Parallel Browsing (Future)
Multiple browser instances:- Research across sites
- Price comparisons
- Data aggregation
Security
Privacy
- Each user gets isolated browser
- No session sharing
- Cookies cleared after task
- No tracking
Safety
- No credential storage in browser
- HTTPS enforced where possible
- No arbitrary code execution
- Sandboxed environment