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

AI Lets Everyone Ship Code - But Who Holds the Pager?

Fazm Team·March 11, 2026·2 min read

ai-codingdevopsengineering-cultureopinion

AI Lets Everyone Ship Code - But Who Holds the Pager?

Modern AI generates surprisingly decent code. That is not the problem.

The problem is what happens after the code ships. Non-engineer gets their win. Demo looks great. Everyone is excited. First incident hits and nobody is holding the pager. Nobody knows the blast radius.

Shadow IT, But It Ships 10x Faster

AI coding tools have basically reinvented shadow IT. Before, non-engineers would build spreadsheet macros and Access databases that slowly became load-bearing infrastructure. Now they build actual applications with actual dependencies that deploy to actual production environments. On the engineering side, tools like Claude Code are remarkably productive when paired with proper architecture - but the ownership question remains.

The difference is speed. A shadow IT spreadsheet took months to become critical. An AI-generated microservice can be in production by Friday.

The Ownership Gap

The code itself is almost never the problem. AI-generated code is fine for most use cases. The gap is in everything around the code:

Who debugs it at 3am? The person who generated the code might not know how to read a stack trace.
Who reviews the dependencies? AI tools pull in libraries without evaluating their security or maintenance status.
Who understands the blast radius? When this service goes down, what else breaks?
Who updates it when the API it depends on changes? The original author might have moved on to another project.

What This Means for Desktop Automation

This is one reason we believe in the desktop agent approach over the "generate code" approach. When an AI agent fills in a form or sends an email, there is no code to maintain. No deployment. No pager. The agent uses existing applications through their normal interfaces, handling exactly the kind of cross-app workflows that would otherwise require custom code.

If the workflow breaks, you adjust the agent's instructions. You do not debug a production service. For a sense of what this looks like in practice, our beginner's guide to AI agents shows how non-technical users can automate tasks without writing a single line of code.

Fazm takes the "use apps, do not build apps" approach to automation. Open source on GitHub. Based on discussions in r/devops.

AI Lets Everyone Ship Code - But Who Holds the Pager?

AI Lets Everyone Ship Code - But Who Holds the Pager?

Shadow IT, But It Ships 10x Faster

The Ownership Gap

What This Means for Desktop Automation

Related Posts

The AI Verification Paradox - We Code Faster But Ship Slower

What SaaS Ideas AI Cannot Replace - Always-On, Hardware Access, and Persistent State

Building a macOS Desktop Agent with Claude - How AI Wrote Most of Its Own Code