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.

Is Claude Overkill? Adding Anti-Over-Engineering Directives to CLAUDE.md

Fazm Team·March 17, 2026·2 min read

claude-code claude-md over-engineering developer-workflow best-practices

Is Claude Overkill? Adding Anti-Over-Engineering Directives to CLAUDE.md

You ask Claude to add a button. It refactors your entire component hierarchy, introduces a new design pattern, adds three utility functions, and creates a constants file. The button works, but now you have 200 lines of changes to review instead of 10.

The Over-Engineering Problem

Claude Code has a tendency to "improve" things it was not asked to touch. This manifests in several ways:

Scope creep - fixing unrelated code while implementing your requested change
Premature abstraction - creating generic solutions for one-off problems
Refactoring without asking - restructuring working code because it could be "cleaner"
Adding error handling you did not request - wrapping everything in try/catch blocks

Each individual change might be reasonable in isolation. But combined, they make code review painful and introduce unnecessary risk. You asked for a button, not a framework.

The Fix That Works

Add this to your CLAUDE.md:

## Development Rules
- Avoid over-engineering. Only make changes that are directly requested.
- Do not refactor existing code unless explicitly asked.
- Prefer simple, direct solutions over abstract patterns.
- If a change requires touching more than the requested scope, ask first.

This simple directive dramatically changes Claude's behavior. It constrains the agent to your actual request and prevents the "while I am here, let me also..." pattern that creates sprawling diffs.

Why This Matters for Parallel Agents

When running multiple Claude agents in parallel, over-engineering compounds. Agent A refactors a shared module. Agent B refactors the same module differently. Now you have merge conflicts in code neither agent was asked to touch. Keeping each agent narrowly scoped prevents this.

The Right Balance

Claude's instinct to improve code is not always wrong. Sometimes you want it to notice a bug nearby or suggest a better pattern. The key is making improvement opt-in rather than the default. Your CLAUDE.md should make it clear: do what is asked, nothing more, and suggest improvements separately.

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

Is Claude Overkill? Adding Anti-Over-Engineering Directives to CLAUDE.md

Is Claude Overkill? Adding Anti-Over-Engineering Directives to CLAUDE.md

The Over-Engineering Problem

The Fix That Works

Why This Matters for Parallel Agents

The Right Balance

More on This Topic

Related Posts

Fixing AI Goldfish Memory with CLAUDE.md Constraints

Why CLAUDE.md Is the Entire Game for Parallel Claude Code Agents

Hitting Claude's Context Limit Mid-Build and How CLAUDE.md Fixes It