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.

Using Claude Code Hooks for Native macOS Swift Development

Fazm Team·March 17, 2026·3 min read

claude-code hooks swift macos development workflow

Using Claude Code Hooks for Native macOS Swift Development

Building a native macOS app in Swift with Claude Code, the single thing that changed my workflow the most was hooks. Not a new model, not a better prompt technique - hooks. The ability to run custom scripts before and after Claude Code actions transforms how you develop.

What Hooks Do

Claude Code hooks are scripts that execute automatically at specific points in the workflow. Before a file is saved, after a commit is created, when a new session starts - you define triggers and Claude Code runs your scripts at those moments. For Swift development, this is transformative.

The Game-Changing Hooks

Pre-save formatting. Every time Claude Code writes a Swift file, a hook runs swift-format on it before the save completes. No more inconsistent formatting across agent-generated code. Every file matches your project style, automatically.

Build validation. After any Swift file changes, a hook triggers xcodebuild to verify the project still compiles. Claude Code gets immediate feedback if its changes broke something, before you even look at the output. The agent can self-correct without you intervening.

Test runner. Before any commit, hooks run your test suite. If tests fail, the commit is blocked and Claude Code sees the failures. It fixes the issues and tries again. You get commits that always pass tests.

Session initialization. When a new Claude Code session starts, a hook reads your Xcode project structure and injects the current build target, scheme, and recent build errors into the context. The agent starts every session aware of your project state.

Why This Matters for Swift

Swift development has more ceremony than scripting languages. You need to manage Xcode project files, provisioning profiles, build schemes, and framework dependencies. Hooks automate the ceremony so you can focus on the logic.

Without hooks, you constantly interrupt Claude Code to say "now build it" or "run the tests." With hooks, these steps happen automatically. The development loop tightens from minutes to seconds.

Setting It Up

Define hooks in your .claude/hooks.json file. Start with just the build validation hook - it provides the most immediate value. Add formatting and testing hooks once the basic loop is working. Keep hook scripts fast - anything over a few seconds breaks the flow.

Using Claude Code Hooks for Native macOS Swift Development

Using Claude Code Hooks for Native macOS Swift Development

What Hooks Do

The Game-Changing Hooks

Why This Matters for Swift

Setting It Up

More on This Topic

Related Posts

Best Practices for Shipping iOS and macOS Apps with Claude Code

Claude Code for Swift/macOS Development - ScreenCaptureKit and Deprecated APIs

Codex vs Claude Code for macOS Desktop Development