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

Accessibility APIs Are the Cheat Code for Computer Control

Fazm Team·March 16, 2026·2 min read

accessibility-apicomputer-controlvision-modelautomationmacos

Accessibility APIs Are the Cheat Code for Computer Control

Most AI computer control tools work like this: capture a screenshot, send it to a vision model, get back pixel coordinates, simulate a click at those coordinates. It works, technically. But it is slow, expensive, and breaks constantly.

There is a better way that almost nobody in the AI agent space talks about: accessibility APIs.

How Screenshot-Based Control Actually Works

The typical loop for screenshot-based agents goes: take screenshot (200ms), encode and send to vision model (500-2000ms), parse response, move mouse, click. That is 1-3 seconds per single interaction. If the UI changes between the screenshot and the click - and it often does - the agent clicks the wrong thing and has to retry.

Vision models also struggle with similar-looking buttons, dropdown menus that overlay other elements, and dark mode vs light mode differences. Every pixel matters, and pixels are unreliable.

What Accessibility APIs Give You

macOS has a powerful accessibility framework originally built for screen readers and assistive technology. It exposes the entire UI tree of every application - every button, text field, menu item, checkbox, and label. Each element comes with its role (button, text field, menu), its label ("Save", "Cancel"), its value, and the actions you can perform on it ("press", "increment", "pick").

Instead of "click at coordinates (423, 187) and hope the Save button is still there," you say "find the button labeled Save and press it." This is deterministic. It works regardless of screen resolution, window position, or theme.

Why This Matters for AI Agents

An AI agent using accessibility APIs can read a UI faster, act on it more reliably, and recover from errors more gracefully than any screenshot-based approach. The agent gets structured data instead of pixels. It can enumerate all available actions instead of guessing from an image.

On macOS, this is built into the system. No special drivers, no browser extensions, no injected code. Just the same APIs that VoiceOver and other assistive technologies use every day.

The AI agent space is slowly catching on, but accessibility APIs remain underutilized. They are the foundation of reliable desktop automation.

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

Accessibility APIs Are the Cheat Code for Computer Control

Accessibility APIs Are the Cheat Code for Computer Control

How Screenshot-Based Control Actually Works

What Accessibility APIs Give You

Why This Matters for AI Agents

Related Posts

AppleScript and Finder Automation - macOS Power You Are Not Using

What We Learned Building a macOS AI Agent in Swift (ScreenCaptureKit, Accessibility APIs, Async Pipelines)

Keeping Your Mac Always-On for AI Agent Automation - Caffeinate and Beyond