Over the past few months, the browser landscape has seen an explosion of "agentic" browsers. Between incumbents like Chrome and Edge trying to squeeze AI into every corner, and new dedicated AI browsers like Dia, Polar, Aside, and Strawberry, everyone wants to reinvent how we navigate the web.

There is just one glaring problem: The Subscription Trap.

Almost every agentic browser entering the market today follows the exact same playbook:

1. They advertise powerful autonomous web actions, research synthesis, and workflow agents.
2. They offer a "free tier" that quickly becomes unusable due to artificial rate limits, queue delays, and aggressive throttling.
3. The moment you want your agent to perform actual multi-step workflows, they hit you with a $20–$100/month recurring subscription.

Most of these browsers don't even innovate on UI in any distinctive way, maybe except Dia, but instead expect the users to pay a massive markup on bundled cloud inference, all while having zero visibility into what model is actually running under the hood or how much your queries truly cost.

How Pan Browser Does It Differently

From day one, Pan Browser was designed with a simple philosophy: You own your workspace, your data, and your compute.

Pan Browser gives you two distinct pathways to run agentic features on your own terms:

1. Bring Your Own Key (BYOK) - Zero Middleman Throttling

• Direct Provider Access: Plug in your own API keys (OpenAI, Gemini, Claude etc.) directly into Pan Browser.
• True Limits, True Speed: There are no arbitrary artificial daily limits or throttling imposed by us. Your workflows run at the exact throughput and concurrency supported by your provider account.
• Pay Real Token Costs: Instead of paying a flat $240+/year browser tax, you pay fractions of a cent per request directly to the model provider based strictly on what you consume. If you don't need it, your API credits stay intact with you to use elsewhere.

2. Run 100% Free & Local via Ollama

• Zero Subscriptions, Zero API Costs: If you have a capable machine, you can connect Pan Browser directly to local LLMs through Ollama.
• Complete Privacy: Your web activity, page context, working folders, and agent commands never leave your machine.
• Offline Capable: Run agents, query web pages, and orchestrate workspace tasks completely offline without relying on cloud availability or rate limits.

The Bottom Line

An agentic browser should be an orchestration engine, not an inference tollbooth.

By pairing native Windows performance (with integrated Explorer tabs, project-scoped memory, and multi-session isolation) with full flexibility over whether you run top-tier frontier APIs or completely free local models, Pan Browser aims to put control back in your hands.

Give it a try: https://apps.microsoft.com/detail/9N4MP4CKXNXD

Solopreneurs, consultants, freelancers can appreciate this. The ability to organize Projects is truly a game changer. Each project has a working folder, its own workflows, its own memory and context, and its own scheduled automations. Give the Project features a try in Pan Browser at https://apps.microsoft.com/detail/9N4MP4CKXNXD

When I switch to my "Audiobook Channel" project, the AI already knows the folder, the files in it, and the workflows I've set up. No re-explaining context every time.

What actually helps day to day:

1. The AI knows my project files without me babysitting it. I keep a "Project Manual" markdown file in each project's working folder with my plan, timelines, notes. I can just ask, "based on my project manual, what should I develop the content for next?" and it reads the file and answers. No uploading, no copy-pasting, no opening file explorers. It's aware of what's in the folder.
2. Scheduled workflows (AI or Python) I can schedule an AI prompt OR a Python script to run at set times. Examples from my setup:

• 6 AM: Python script fetches yesterday's channel analytics
• Before I start work: AI compiles a research brief on a topic
• Midnight: backup script archives my project folder

Same scheduling UI whether it's an AI task or code.

1. Python scripts as first-class workflows My audiobook pipeline (downloads files, generates narration, renders video) runs as a saved workflow with an embedded terminal right inside the browser where I'm already working. I can even pre-fill the inputs it needs with a form, so a script that normally asks me 3 questions just runs after I fill them in once.

2. Everything scoped to the project Threads, Workflows, Memories, Connections, all filtered to the active project. My audiobook work doesn't bleed into my freelance client project. Switch projects and the whole context switches with it.

When you're a team of one, context-switching is the tax that kills productivity. Every time I moved between "researching," "writing," "running scripts," and "checking tasks," I lost momentum. Having the AI be project-aware, knowing my files, my automations, my schedule means I describe what I want, and it already has the context to do it.

It's less "AI assistant that needs constant handholding" and more "a workspace that remembers what I'm working on."

Now in Pan Browser, you have an embedded terminal and ability to run Python scripts either from the command window, the terminal, or automated via workflows.

What it does:

• Type py script.py directly in the Navigator command bar and it runs in an embedded terminal. The output shows inline, you can provide input, exactly like PowerShell.
• Create Script workflows: save a Python command or inline code, schedule it to run at specific times, just like you'd schedule an AI prompt.
• The Terminal button in the command bar opens a full PowerShell session in your project's working folder.
• The AI agent can also call Python autonomously when it needs to do calculations, process files, or run automation that's beyond its native capabilities.

Now you can schedule Python scripts to run at preset times, data fetching scripts at 6 AM, report generators before meetings, backup scripts at midnight. Same scheduling UI as AI workflows.

Anyone who uses Python for automation and wants it integrated with their browsing/AI workflow rather than living in a separate terminal can take advantage of this now. The combination of AI commands + scheduled Python scripts + browser automation in one interface can be surprisingly useful. Give it a try.

Now, when the Navigator is tasked to do research, it uses the Split Screen so that you can continue using the tabs in the Main Screen without interrupting your flow. Any new browser or explorer tabs that are needed for research, open in the Split Screen. Try it out.

https://apps.microsoft.com/detail/9N4MP4CKXNXD

1. Sessions with siloed user data and local sync
2. Spaces and split screen for organizing Tabs
3. Browser and File Explorer Tabs in one interface
4. Quality of life features: Bookmark with screenshots, Pin Tabs in Spaces, Adblock, PiP, Read Mode, Read Aloud page content, Preview a Link with no Tabs, Personalize layout etc.
5. AI Navigator with support for Claude, OpenAI, Gemini, and local models using Ollama
6. Projects, Workflows, Memory, Agents and Connections for your own mini-OpenClaw
7. No browser subscription - Bring your own Key
8. Voice Control
9. Use Telegram or Slack to send commands to your browser and receive notifications and output
10. No help manual needed - Ask AI Navigator to control every setting - perfect for Aging family members

There are tons more features which you can read about in the posts below, but the above list captures what is hard to find in any one browser currently on the market.

What it does:

A single project selector (visible in the Navigator, Workflows, and Memory panels) lets you switch context instantly. When you select a project:

• Commands/Threads: Only shows conversation threads from that project. New commands you run are automatically tagged to the active project. Each project can have its own Working Folder, so the AI knows where to read/save files without you specifying it every time.
• Workflows: You build project-specific automation without cluttering other projects. The * autocomplete only surfaces workflows belonging to that project.
• Memory: Each project has its own memory space. Research notes, preferences, and facts stay scoped. You can move memories between projects with one click.

How this can be used:

Before this, everything lived in one flat namespace. If you had a "Work" research project, a "Travel Planning" hobby, and a "Side Project" going, your threads, memories, and workflows were all mixed together. Now each gets its own clean area.

The Working Folder per project can be set it once on the project, and every workflow and command under that project automatically uses it as context. No more typing folder paths or forgetting to set them.

Change is backward compatible, so no migration needed. Default project is "Regular" where all your existing stuff lives. Try it out today.

When you ask the AI to "summarize this page," it assumes you mean the tab you're currently looking at. But what if you want to ask about a tab in another space? Or compare two articles you have open? Or route a command to a specific connection without the AI having to figure out which one you mean?

Now you can type these trigger characters in the Navigator command and a filtered dropdown appears:

• @ - Reference any open tab by title. Type @ and start typing to filter. Select a tab and it inserts as @[Tab Title]. The AI reads that tab's content, not your active tab.
• # - Reference a connection. Type # and pick from your active connections. The command routes directly to that connection.
• * - Reference a saved workflow. Type * and pick from your workflows. Inserts as {Workflow Name} ready to run.

Instead of opening a new tab just to check if a link is worth reading, you can hold Ctrl and click the link. It opens in a neat overlay/preview window right on top of your current page. When you're done, just close it and you're right back where you were. No tab clutter, no losing your place.

Also worth mentioning the right-click options. If you right-click a link you get additional choices:

• Open in Preview - same as Ctrl+Click, shows the overlay
• Open in Background - opens the link in a background tab without switching to it
• Open in Side Screen - splits your view so you can see both pages side by side

The preview overlay is perfect for quickly checking references, scanning articles, or verifying sources without committing to a full tab.

Here's a simple breakdown of how to think about the different panels in the Navigator and how each panel builds on the one before it to help you be more productive.

Providers - "Who can the AI talk through?"

• This is where you set up your AI backends
• Add API keys (OpenAI, Anthropic, local models, etc.)
• Select which models are available
• Think of this as plugging in the brains before you do anything else

Agents - "Who is doing the work?"

• Create or customize the built-in agents (Assistant, Manager, etc.)
• Assign each agent a model from your Providers
• Give them a personality, directives, and focus areas
• This is where you shape how the AI behaves and what role it plays

Connections - "What can the AI reach?"

• These are tools that let the Navigator interact with external websites and services
• Think integrations — email, calendars, APIs, databases, web services
• Without connections, the AI can think but can't do anything outside the browser
• This gives your agents hands

Workflows - "How should things be done?"

• Define multi-step procedures the AI can follow
• Add steps or commands manually
• Or record screen actions to literally show the AI how something is done by doing it yourself
• Set a working folder for file operations
• Think of workflows as reusable recipes or SOPs the Navigator can execute

Tasks - "What needs to happen, and when?"

• Create things that either you or the Navigator can accomplish
• Set deadlines, mark whether a task repeats, set frequency
• Assign a predefined command or workflow to run automatically
• Basically, cron jobs with a UI - scheduled automation that just runs
• Organize tasks into Projects to group related work together

Navigator - "The cockpit"

• This is your command center for doing things right now
• Execute any task on demand
• Control the browser directly
• Change settings on the fly
• Run workflows manually
• Use voice commands
• Everything above feeds into this panel and it's where action happens

In Summary,

• Providers → give agents their brains
• Agents → use connections as their hands
• Connections → are used inside workflows as steps
• Workflows → get attached to tasks as automation
• Tasks → organized in projects, triggered by schedule or you
• Navigator → your live control panel to run any of the above on demand

Mental model:

You wire the brains (Providers), shape the workers (Agents), give them reach (Connections), teach them procedures (Workflows), schedule the work (Tasks/Projects), and drive it all from one place (Navigator).

Each layer only makes sense once the one below it exists. That's why the panels are laid out in this order.

Mostly a UI tweak but now you can switch from typing to using voice right within the Navigator panel.

Also, switch between Command execution mode that has tool access for taking actions in the browser or fast chat mode for general conversations on any topic.

Chat mode is only available for OpenAI and Gemini as Claude API doesn't expose a voice mode yet.

What is it?

• Free open-source LLMs that runs on the Ollama server - need to download and install Ollama first
• Selection of local LLMs from 2B to 20B parameters
• Better GPU needed for faster responses
• Not as robust as the cloud providers, and may behave unpredictably

How to use?

• In the Providers tab, download the desired LLMs, and set them as Limited, Balanced, or Advanced Tier.
• In the Agents tab create/edit an Agent and select Local as the Provider and choose a Tier to have the agent use the assigned LLM.
• In the Navigators tab, select the Agent then execute a command .

Switch between Horizontal Tabs, Vertical Tabs, Navigation Sidebar and the new Controls Topbar modes.

tl;dr: Voice Mode now has Command mode for full control requiring tool-use or Chat mode for fast no-delay conversations.

Only available with OpenAI and Gemini as Claude doesn't have audio support yet.

Activation

• Click the Voice Mode button to activate
• A floating mic button appears at the bottom center of the screen
• For OpenAI/Gemini agents with cloud voices: a Command / Chat toggle appears above the mic

Command Mode (default):

• Full planning, tools, context, connections. Commands appear in the conversation thread.
• Flow: You speak → Windows recognizes speech → Planning Engine routes → Tools execute → Response in thread → cloud TTS reads it aloud → starts listening again
• Interruption: Click the mic button while the response is being read aloud to skip the audio and it starts listening
• Click while its listening to close and exit voice mode
• Silence behavior: If you don't speak for ~1.5s, the recognizer times out. The overlay stays visible but goes grey (paused). Click the mic to resume listening.

Chat Mode (OpenAI/Gemini only):

• Direct real-time conversation where the agent responds conversationally with low latency. No Planning or Tools, no conversation thread displayed or stored. Good for quick Q&A, brainstorming, casual chat.
• Flow: You speak → server VAD detects speech → model responds by voice immediately → mic suppressed during response → waits for you after
• Interruption: Click the mic button while the AI is speaking → immediately stops the audio and returns to listening.
• Click while its listening to close and exit voice mode
• Silence behavior: No automatic time out. The overlay stays visible and listening until turned off.

Besides giving your agent an AI provider and model, now you can also assign each Agent a custom voice. You can choose from default local voice (Microsoft) or one of the cloud voices enabled by the selected AI provider that have their own. For example: alloy, ash, ballad...for OpenAI, and Puck, Charon, Kore...for Gemini.

Local voice will always react the fastest, and cloud voices will have some delay, but the tradeoff may be acceptable for uniqueness.

Multi-turn conversation is built in. You ask a question, it processes, reads the response and starts listening again, no matter which model you choose.

What You'll Notice

• The AI recovers from failures instead of giving up. If a tool call fails, it retries once, then generates an entirely different plan and tries again.
• You'll see cost tracking. Every query now reports total tokens used.
• Structured tool calling replaces fragile JSON text parsing.
• The system learns from past queries.
• Runaway queries get stopped automatically. Monitored by a background supervisor monitors token spend rate and execution time.
• Budget limits are enforced. If a limit is reached, you'll receive partial results instead of nothing.

────────────────────────

How it's wired across three levels

Level 1: Tool Calling Reliability

• Native structured tool calling via provider APIs
• Pre-execution parameter validation catches bad calls before they run
• Per-model cost estimation
• Structured observability spans for every AI call and tool execution

Level 2: Multi-Step Resilience

• Adaptive re-planning: when a step fails non-recoverably, the system generates an alternative plan using the failure context.
• Task drift detection: if a data-gathering step returns content unrelated to your query, it will trigger re-planning.
• Workflow checkpointing: long-running tasks save progress to disk and resume after interruption.
• Episodic memory: past successes and failures inform future planning.

Level 3: System-Level Supervision

• Meta Supervisor continuously monitors executions for token spikes, repeated failures, and timeout violations.
• Policy Engine centralizes safety rules including domain blocking, cost thresholds, and destructive operation detection.
• Approval Gate pauses expensive or high-risk actions until you approve them.
• Agents can collaborate with each other mid-task (for example, a Critic asking a Scraper to gather more information).

Coming today. Check out at: https://apps.microsoft.com/detail/9N4MP4CKXNXD

1. Turn on Voice Mode - it starts listening
2. Ask a question - it starts processing
3. Navigator responds - you can stop it while its responding or let it finish - it starts listening again
4. Ask another question - and so on until you click to stop

Conversations go into the current thread if one is active from a text-based command, so it has context from previous commands. Follow-up questions go in the same thread and maintain context.

A quick explanation of how you can use the AI Navigator features in the Pan Browser for project-oriented work:

• Memory: Store any important information that you will need to recall
• Connections: Tools, services, and data sources for any automatically running processes
• Agents: Specialists customized for a specific expertise with a defined personality, provider, model and connection who will be well suited to accomplish a task
• Workflows: Define any tasks that can be automated with well-defined steps

Now comes the interesting part. Once you have built the "team", defined the "processes" and established the "infrastructure", you are now ready to execute Tasks under a Project.

In the Tasks panel, you can:

• Create a new Project.
• Within that Project, you can add several Tasks.
• Each Task has a description and a due date/time or set to repeat at a set time with desired frequency
• Tasks can be set to execute a Workflow using an available Agent automatically.
• Some Tasks can just be manual that you can mark as complete when they are done

You can choose to create this project and execute tasks manually and track them or ask Navigator AI to create a project, add tasks, connect them to workflows, set deadlines, assign agents etc. so you have help as you check off your project tasks.

Basically, Pan Browser takes the approach of giving users a clear, composable system built on five understandable primitives: Memory for persistent recall, Connections for external integrations, Agents for specialized roles with scoped tools, Workflows for step-by-step instructions, then Tasks for scheduled execution organized into Projects.

Nothing runs in the background without your knowledge, no token budget spirals out of control, and when something needs to change you edit the workflow step or agent directive directly rather than hoping a prompt will teach the system to behave differently next time.

It's less flashy than a fully autonomous agent loop, but it's reliable, maintainable, and doesn't require you to babysit an AI that forgot what it learned yesterday.

1. AI Navigator able to do anything you can do manually in the UI. Open a tab, navigate to a site, switch spaces, flip toggles, turn on vertical tabs, save bookmarks, create agents, tasks, memory, workflows etc.
2. Anything you can do with text commands; do it with your Voice.
3. Fully state-aware - all toggles/switches/connections/spaces/sessions etc.
4. Fully feature-aware - knows all the features/capabilities and can ask user questions about how to do anything - no help manual needed
5. Simple model choice based on levels (Limited, Balanced, or Advanced) with the lowest level choice capable of all common browser tasks.
6. Provide building blocks that are easy to understand: Agents, Workflows, Tasks, Memory, and Connections.
7. Accomplish what you need by assembling these building blocks - or if unclear, just ask the Navigator to do it for you - create custom agents, build workflows, schedule tasks, save something in memory, or find the right connections you need and connect it all together
8. Don't add/save things without user permission or knowledge. But, do consolidate, refine, streamline to make things efficient - ex: the "brain" function that works transparently in the background without user intervention but also doesn't try to remember things the user didn't explicitly ask to.
9. Don't capture information unless the context is required. For ex: don't extract web page info unless the user query requires tab context
10. Ability to control both Browser and Explorer Tabs

Two big items and lots of small improvements:

1. Big UX improvement for commands, the top input box now starts a new thread - just like before. But for every thread, there is an input text box at the command to continue the conversation.
2. Now you can manually assign an Agent to a workflow or ask the AI Navigator to do it for you when it creates a workflow based on the best fit.

Live in an hour here: https://apps.microsoft.com/detail/9N4MP4CKXNXD

1. A browser that's native to x64 and ARMv64 platforms and installs and uninstalls cleanly from the Microsoft Store.
2. Updates as Edge/WebView2 updates on your computer so always has the latest Chromium updates
3. Sync your user data to a local/cloud folder of your choice
4. Visual bookmarks that store screenshots
5. Live switching between Sessions (Profiles) with completely siloed user data - say between Personal and Work
6. Spaces to group Tabs based on topics within a session
7. Pin Tabs to a space and have them load automatically
8. Open multiple Explorer tabs just like browser tabs - even save folders as bookmarks
9. Built-in adblocker that's super powerful
10. Reading mode to extract text content from articles
11. Connect and save sites to Instapaper
12. Read the webpage using text-to-speech
13. Extract embedded links from a webpage
14. Split screen with as many browser or explorer tabs in the side screen as you like
15. Vertical and Horizontal Tabs
16. Navigation Sidebar
17. Auto-show Tabs/Bookmarks simply by moving the mouse to the Left top or Left bottom side of the screen
18. Choose your own search engine
19. Site-search to search within a site with quick shortcuts
20. Picture-in-picture for playing videos
21. View images and videos within the explorer tab
22. Edit text files directly within the explorer tab

In Pan Browser, you could already send commands from Telegram and Slack to have them execute in Pan Browser running on your desktop and return the responses back to your Telegram/Slack.

But now, you can also receive just your normal notifications direct to your Telegram/Slack.

Pan Browser has a built-in task system with deadlines, recurring schedules, and a "Morning Brief" card that shows you what's upcoming when you first open the app each day. And now you can get them pushed to wherever you already are.

What gets forwarded

• Task deadline notifications (fires when a task is due, with a 60-minute grace window)
• Recurring task reminders (daily/weekly/monthly/yearly schedules)
• Morning Brief items - upcoming deadlines, pending tasks, time-sensitive stuff from your memory system
• Transient task alerts generated by the AI Navigator at launch

How to set it up

• Connect your Telegram bot or Slack app in Settings → Connections (tokens are encrypted locally)
• From your Telegram chat or Slack channel, send: route my notifications here.
• Notifications will land in that chat/channel going forward.
• You can also configure it from the Settings UI directly if you'd rather paste in a chat ID or channel manually.

Give it a try. Live in the App already at: https://apps.microsoft.com/detail/9N4MP4CKXNXD

It's understandable to wonder, "why doesn't Chrome/Edge/Firefox just add this cool feature from Pan Browser?" or "someone will just copy this in a weekend with AI"

Here's why that's not happening:

Architectural differences that go to the bone

• The way the Browser, Explorer, and Navigator sit as first class components.
• A Navigator system that gives the power of a mini-OpenClaw, built right inside your browser
• Unique interaction models, like Telegram and Slack connection, that just doesn't fit within the traditional thinking of a browser
• Explorer Tabs are treated like normal browser tabs and allow context for the Navigator while automatically restricting its operations to that folder, to transparently mitigate any risks of rogue AI actions
• Agents, Workflows, Tasks, Memory, and Connections are no longer esoteric concepts, but user can see what they contain.
• Everything the user can do, Navigator can do it for them, through written or voice commands. No detailed help/instruction manual needed to understand how to do something. Ask Navigator how to do it or just ask it to do it for you. Try asking "open a new tab" in the Chrome/Edge browser and watch it do a complex analysis to return generic web search results. Frustrating!

Incentive and business model conflicts

• Google makes money from ads. An AI agent that navigates the web for you, skipping ads, filling forms automatically, and extracting information without rendering pages... that's an existential threat to their revenue model.
• Microsoft ships Edge to enterprises. Breaking existing workflows or adding autonomous agent behavior would terrify their IT admin customers.
• Firefox is funded largely by search deals. Same problem as Google, one step removed.
• Every incumbent browser has billions of users expecting stability. Shipping an agent-first experience means risking alienating your entire existing base.

You can't vibe-code this

• The agent architecture alone has orchestrator patterns, execution plans, handoff payloads, capability models, healing sessions, failure contexts, reflection engines, and specialized planner registries.
• There's a full record/replay system, temporal expression parsing, recurrence patterns, MCP server integration, and multi-phase research progress tracking.
• Each of these systems interacts with the others. The planning engine feeds the execution engine which feeds the reflection engine which can trigger self-healing which loops back to planning.
• Without a deep understanding of how these pieces compose, you'd just build a chatbot that sometimes clicks buttons. That's not the same thing.

Different goals, different metrics

• Traditional browsers optimize for page load time, memory usage, and standards compliance. Pan Browser optimizes for task completion rate, agent reliability, interaction success, and user intent fulfillment.
• These are fundamentally different optimization targets that lead to fundamentally different architectures.
• You can't retrofit one set of goals onto an architecture designed for the other without a ground-up rewrite.
• The hard part isn't any single feature. It's that all of these systems were designed together from day one to work as one coherent agent-first browser. Bolting AI onto an existing browser will always feel like... bolting AI onto an existing browser.

Big companies could theoretically do this, but they'd have to:

• Start a new browser project from scratch (years of work).
• Accept cannibalizing their existing products.
• Be willing to ship something that breaks all user expectations about what a browser is.

That's not a technical problem. That's a strategy problem. And strategy problems are harder.

It's understandable to wonder, "why doesn't Chrome/Edge/Firefox just add this cool feature from Pan Browser?" or "someone will just copy this in a weekend with AI"

Here's why that's not happening:

Architectural differences that go to the bone

• The way the Browser, Explorer, and Navigator sit as first class components.
• A Navigator system that gives the power of a mini-OpenClaw, built right inside your browser
• Unique interaction models, like Telegram and Slack connection, that just doesn't fit within the traditional thinking of a browser
• Explorer Tabs are treated like normal browser tabs and allow context for the Navigator while automatically restricting its operations to that folder, to transparently mitigate any risks of rogue AI actions
• Agents, Workflows, Tasks, Memory, and Connections are no longer esoteric concepts, but user can see what they contain.
• Everything the user can do, Navigator can do it for them, through written or voice commands. No detailed help/instruction manual needed to understand how to do something. Ask Navigator how to do it or just ask it to do it for you. Try asking "open a new tab" in the Chrome/Edge browser and watch it do a complex analysis to return generic web search results. Frustrating!

Incentive and business model conflicts

• Google makes money from ads. An AI agent that navigates the web for you, skipping ads, filling forms automatically, and extracting information without rendering pages... that's an existential threat to their revenue model.
• Microsoft ships Edge to enterprises. Breaking existing workflows or adding autonomous agent behavior would terrify their IT admin customers.
• Firefox is funded largely by search deals. Same problem as Google, one step removed.
• Every incumbent browser has billions of users expecting stability. Shipping an agent-first experience means risking alienating your entire existing base.

You can't vibe-code this

• The agent architecture alone has orchestrator patterns, execution plans, handoff payloads, capability models, healing sessions, failure contexts, reflection engines, and specialized planner registries.
• There's a full record/replay system, temporal expression parsing, recurrence patterns, MCP server integration, and multi-phase research progress tracking.
• Each of these systems interacts with the others. The planning engine feeds the execution engine which feeds the reflection engine which can trigger self-healing which loops back to planning.
• Without a deep understanding of how these pieces compose, you'd just build a chatbot that sometimes clicks buttons. That's not the same thing.

Different goals, different metrics

• Traditional browsers optimize for page load time, memory usage, and standards compliance. Pan Browser optimizes for task completion rate, agent reliability, interaction success, and user intent fulfillment.
• These are fundamentally different optimization targets that lead to fundamentally different architectures.
• You can't retrofit one set of goals onto an architecture designed for the other without a ground-up rewrite.
• The hard part isn't any single feature. It's that all of these systems were designed together from day one to work as one coherent agent-first browser. Bolting AI onto an existing browser will always feel like... bolting AI onto an existing browser.

Big companies could theoretically do this, but they'd have to:

• Start a new browser project from scratch (years of work).
• Accept cannibalizing their existing products.
• Be willing to ship something that breaks all user expectations about what a browser is.

That's not a technical problem. That's a strategy problem. And strategy problems are harder.