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

Session State Management for AI Agents - Why Agents Forget and How to Fix It

Fazm Team·March 16, 2026·2 min read

session-managementstateagentmcppersistence

Session State Management for AI Agents

A post in r/ClaudeAI described "a coding agent session manager that manages itself via its own MCP" and it highlighted a fundamental problem with AI agents today: they have terrible memory.

Start a conversation with an agent, ask it to do something complex across multiple apps, and it works great. Close the session, open a new one, and the agent has no idea what happened before. It does not remember the files it edited, the APIs it called, or the decisions it made. You start from scratch every time.

Why This Matters for Desktop Agents

For a desktop automation agent, session state is critical. If you ask the agent to "continue organizing my files like yesterday," it needs to remember what it did yesterday - which folders it processed, what naming convention it used, which files it skipped. Without persistent state, you have to re-explain everything.

The web solved this problem decades ago with sessions, cookies, and databases. AI agents need the same infrastructure. The Reddit thread proposed using MCP itself as the session storage layer - the agent writes its own state to an MCP server and reads it back when a new session starts.

What Good Session Management Looks Like

A well-designed agent session system tracks three things. First, the tool call chain - every action the agent took, in order, with inputs and outputs. This is your audit trail and your replay mechanism. Second, the decision context - why the agent chose one action over another. Third, the working set - which files, apps, and data sources were involved.

With all three persisted, you can do more than just resume where you left off. You can replay past workflows, debug failures by examining the full action history, and let the agent learn from patterns across sessions.

The knowledge graph approach to agent memory takes this further by building a structured model of the user's habits and preferences over time. But even basic session persistence - just saving the last 10 conversations with their tool calls - is a massive improvement over the current default of amnesia.

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

Session State Management for AI Agents - Why Agents Forget and How to Fix It

Session State Management for AI Agents

Why This Matters for Desktop Agents

What Good Session Management Looks Like

Related Posts

MCP Config Management Is Broken - Why We Need an App Store for AI Integrations

You Do Not Need an MCP Server for Every Mac App - Accessibility APIs as a Universal Interface

Using Claude as an Execution Layer - Markdown Specs, MCP Tools, No Traditional Code