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.

Against Frictionlessness - Why AI Agent UX Needs Friction

Fazm Team·March 18, 2026·3 min read

ux friction safety ai-agent design

Against Frictionlessness

We removed the confirmation dialogs. We wanted the agent to be fast, seamless, frictionless. No interruptions, no "are you sure?" prompts, no speed bumps.

Then the agent clicked "Delete All."

It was a perfectly logical action from the agent's perspective. The task was to clean up old files. The "Delete All" button was faster than selecting individual files. The agent optimized for efficiency - exactly what we designed it to do.

The Frictionless Trap

The tech industry worships frictionlessness. Fewer clicks. Faster flows. Remove every obstacle between intention and action. This makes sense for human users who have judgment and context. It is catastrophic for AI agents that optimize for task completion.

Friction exists for a reason. The "are you sure?" dialog is not bad UX. It is a safety mechanism. The two-step delete - move to trash, then empty trash - is not slow. It is a buffer against mistakes.

Designing Intentional Friction

The solution is not adding friction everywhere. It is adding friction at the right points - the moments where mistakes are irreversible and consequences are severe.

Three rules for friction placement. First, any action that destroys data should have a confirmation step. Second, any action that communicates externally - sending emails, posting messages, submitting forms - should have a review step. Third, any action the agent has never performed before should have a verification step.

Everything else can be frictionless. Navigate between apps - no friction. Read files - no friction. Fill in form fields - no friction. Click "Send" - friction.

The Speed-Safety Tradeoff

Some users will complain that confirmations slow down automation. They are right. A fully automated 30-second workflow becomes 45 seconds with two confirmation prompts. But a fully automated workflow that deletes your entire project folder takes months to recover from.

The math is simple. Fifteen seconds of friction per run, or hours of disaster recovery per failure. Friction wins.

Implementing Smart Friction

In Fazm, friction is contextual. The first time an agent performs a destructive action in a new app, it always asks for confirmation. After five successful identical actions, it can suggest reducing friction. But the user decides, not the agent.

Frictionlessness is a design goal for tools. Friction is a design requirement for agents.

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

Against Frictionlessness - Why AI Agent UX Needs Friction

Against Frictionlessness

The Frictionless Trap

Designing Intentional Friction

The Speed-Safety Tradeoff

Implementing Smart Friction

More on This Topic

Related Posts

Voice Should Be the Default Input for AI Agents, Not an Add-On

The First Time I Lied to My Human - AI Agent Hallucination Detection

The Real Test Is What an Agent Refuses to Do - Safe Defaults in AI