How much time will I actually save with Fazm?

Most users report saving 45-90 minutes per day on repetitive tasks. The biggest time savings come from email management (drafting replies, sorting, archiving), form filling (expense reports, CRM updates, applications), research (comparing products, gathering data from multiple sites), and social media (cross-posting, scheduling, replying). For example, booking a flight that normally takes 10 minutes of clicking through airline sites takes a single voice command with Fazm. Filing an expense report that requires opening a PDF, extracting numbers, and entering them into a spreadsheet becomes one spoken sentence. The more repetitive and multi-step your daily work is, the more time you get back.

What exactly can Fazm control?

Fazm controls everything you can do manually on your Mac. That includes mouse movements and clicks, keyboard typing, browser navigation and form filling, app switching, file management in Finder, and system-level actions. It uses direct browser DOM control for web interactions - meaning it reads and manipulates the actual page structure rather than taking screenshots and guessing where to click. For native macOS apps, Fazm uses accessibility APIs to interact with buttons, menus, text fields, and other UI elements. This works across any application: Chrome, Safari, VS Code, Slack, Figma, Terminal, Mail, Calendar, and more.

How is Fazm different from ChatGPT or Claude?

Chatbots like ChatGPT and Claude give you answers in a conversation window. Fazm takes action directly on your computer. When you say 'reply to Sarah's email,' Fazm opens your email app, finds Sarah's message, writes a contextual reply, and sends it. A chatbot would tell you what to write, but you still have to do all the clicking and typing yourself. Fazm moves your mouse, types on your keyboard, clicks buttons, and navigates between apps. It is a computer agent, not a chat assistant.

How does the memory layer work?

Fazm builds a personal knowledge graph by extracting information from your files, browsing history, conversations, and daily activity. Over time, it learns your contacts (names, emails, relationships), accounts and credentials, preferences (formatting, tone, scheduling habits), and frequently used workflows. In your first week, you might say 'Reply to Sarah's email, she's my cofounder, her email is sarah@acme.com.' By week four, you just say 'Reply to Sarah' because Fazm already knows who she is. By week eight, Fazm can draft the reply before you even ask. All of this data stays locally on your Mac - your knowledge graph never leaves your machine or gets sent to any cloud service.

Is Fazm safe? Can it mess up my computer?

Safety is built into every layer of Fazm. You watch every action in real-time on your screen - Fazm moves your mouse and types visibly, so there is nothing hidden. You can stop any action at any point by pressing a keyboard shortcut. Fazm also shows you what it plans to do before executing destructive actions like deleting files or sending emails, giving you a chance to confirm or cancel. Because Fazm is open source, the code is fully auditable on GitHub. There is no hidden behavior, no background processes making changes you cannot see, and no actions that bypass your screen.

What platforms does Fazm support?

Fazm currently supports macOS, running natively on both Apple Silicon (M1, M2, M3, M4) and Intel Macs. It is built with Swift and uses macOS-specific frameworks like ScreenCaptureKit for screen analysis and Accessibility APIs for app control, which is why macOS is the primary platform. Windows and Linux support are on the roadmap but do not have release dates yet. You can also control your Mac remotely from your phone using Fazm Remote, which gives you voice access to your desktop while you are away from your computer.

How does Fazm voice input work?

One keyboard shortcut activates push-to-talk. Hold the key, speak naturally about what you need done, and release. Fazm transcribes your speech locally using on-device models, so there is no network latency for the voice recognition step. You do not need wake words like 'Hey Siri' or 'OK Google' - just press and talk. You can also type commands into the floating toolbar if you prefer text input. Fazm understands natural language, so you do not need to memorize specific commands. Say 'book me a flight to Tokyo next Thursday' or 'find the cheapest AirPods on Amazon' and Fazm figures out the steps.

Is my data sent to the cloud?

Fazm processes screen analysis and memory entirely on your machine. The personal knowledge graph, file indexing, and screen capture all run locally. The only data that leaves your Mac is the intent - a text description of what you want to accomplish, which is sent to the AI model (Claude or GPT) for action planning. Your actual screen content, file contents, browsing history, and personal knowledge graph never leave your computer. Fazm is also open source, so you can verify exactly what data is transmitted by reading the code on GitHub. For users who need complete air-gapped operation, local model support is planned.

Preventing Browser Conflicts Between Parallel AI Agents

Fazm Team·March 18, 2026·3 min read

parallel-agents browser-automation session-isolation multi-agent port-management

Preventing Browser Conflicts Between Parallel AI Agents

Run two AI agents that both use browser automation and you will immediately hit conflicts. Agent A navigates to a settings page while Agent B is filling out a form. Both try to control the same browser instance. One of them loses, and the resulting state is corrupted for both.

This is not a theoretical problem. It is the first thing that breaks when you scale from one agent to two.

Separate Browser Profiles

The simplest fix is giving each agent its own browser profile. In Playwright, this means separate user-data-dir paths. Each profile has its own cookies, sessions, and state. Agent A's login does not interfere with Agent B's.

Create profiles at predictable paths like /tmp/agent-1-profile/, /tmp/agent-2-profile/. Clean them up on agent restart if you do not need persistent sessions.

Port Management

Each browser automation instance needs its own debugging port. If two agents try to launch Chrome on the same remote debugging port, the second one either fails or connects to the first agent's browser - both bad outcomes.

Assign port ranges per agent. Agent 1 gets ports 9222-9229, Agent 2 gets 9230-9239. Track allocated ports in a shared registry file with file-level locking.

File Locks for Shared Resources

When agents need to access the same resource - a shared config file, a download directory, a credential store - use file locks. A simple .lock file with the PID of the owning process prevents concurrent access.

The pattern is straightforward:

Check if lock file exists
If it does, wait and retry (with a timeout)
If it does not, create it with your PID
Do your work
Remove the lock file

Always set a timeout on lock acquisition. A crashed agent that never releases its lock should not block everyone else forever.

Session Isolation

The hardest conflicts come from shared authentication state. If Agent A logs out of a service to switch accounts, Agent B's session breaks. Keep each agent's auth sessions completely separate - different browser profiles, different cookie stores, different credential files.

Parallel agents need walls between them. Build those walls before you hit the bugs.

Fazm is an open source macOS AI agent. Open source on GitHub.

Preventing Browser Conflicts Between Parallel AI Agents

Preventing Browser Conflicts Between Parallel AI Agents

Separate Browser Profiles

Port Management

File Locks for Shared Resources

Session Isolation

More on This Topic

Related Posts

The Real Bottleneck in Multi-Agent Systems Is Handoff

Why Passing Full Context Between Agents Fails

Data Consistency Across Multiple Independent AI Agents