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.

Back to Blog

ChatGPT Can Use Your Computer Now - But Screenshot-Based Control Is Still Fragile

Fazm Team·March 17, 2026·3 min read

chatgptcomputer-useaccessibility-apiscreenshotautomation

ChatGPT Can Use Your Computer Now - But Screenshot-Based Control Is Still Fragile

ChatGPT can now see your screen and click things. It takes a screenshot, feeds it to a vision model, identifies UI elements, and clicks coordinates. Impressive demo. Terrible in practice.

The problem is fundamental. Screenshots are pixels. Pixels change constantly. A button that was at coordinates (340, 220) moves to (340, 280) when a notification banner appears. A dropdown menu overlaps the element you wanted to click. Dark mode changes the visual appearance of everything. The vision model has to re-identify every element from scratch each time.

Why This Breaks

Screenshot-based control has a cascading failure mode. The agent takes a screenshot, identifies a button, clicks slightly wrong, gets a different screen than expected, takes another screenshot, and now it is completely lost. Each step compounds the error.

We have seen this happen with form filling - the agent clicks a text field, starts typing, but a tooltip appears and shifts the field down by 20 pixels. The next click lands on the wrong element. The agent does not know it clicked the wrong thing because the screenshot looks "close enough" to what it expected.

Accessibility APIs Solve This Differently

macOS provides an accessibility API that gives you the actual UI tree. Every button, text field, menu item, and label has a programmatic identity. You do not need to visually locate a "Save" button - you ask the system for the button with the role "AXButton" and title "Save" and it gives you a direct reference.

This approach does not care about:

Screen resolution or scaling
Dark mode vs light mode
Overlapping windows or tooltips
Where elements are positioned on screen

The API returns structured data with roles, labels, values, and available actions. You interact with the element directly rather than clicking coordinates.

The Practical Difference

Screenshot-based agents need retries, error recovery, and visual verification at every step. Accessibility-based agents just ask for the element and interact with it. One approach fights the UI. The other works with it.

The screenshot approach will keep improving as vision models get better. But accessibility APIs already work reliably today - no vision model needed.

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

ChatGPT Can Use Your Computer Now - But Screenshot-Based Control Is Still Fragile

ChatGPT Can Use Your Computer Now - But Screenshot-Based Control Is Still Fragile

Why This Breaks

Accessibility APIs Solve This Differently

The Practical Difference

You Might Also Like

Related Posts

Accessibility APIs vs OCR - Two Approaches to Desktop Agent Vision

Accessibility APIs vs Pixel Matching - Why Screenshots Miss So Much Context

Why Every Powerful AI Agent Runs on Mac - It's the Accessibility APIs