Maxclaw

Maxclaw

Free, open-source (MIT) desktop AI assistant that runs fully locally in Go, with browser automation, a real terminal, and multi-channel chat.

61/100MonitorFreeFree

Maxclaw is the right pick only if local execution is the whole point. For $0 under an MIT license you get browser automation with Chrome login reuse, a genuine node-pty/xterm terminal, inline preview of PDF/Word/Excel/images/code, and Cron/Every/Once scheduling — a feature set that cloud assistants like ChatGPT or Notion AI charge for or don't offer at all. The catch is the same thing that makes it private: you must supply and configure your own local model, and you need hardware that can run one. If you want a zero-setup assistant, Mathpix-free cloud tools or ChatGPT remain simpler choices.

Verified 5d ago · liveness 61/100 · cite: rightaichoice.com/tools/maxclaw

Best for
  • Privacy-conscious office workers who need offline AI automation
  • Developers who want a local agent with terminal and browser control
  • Teams self-hosting AI for sensitive data handling
  • Users who already run local models and want scheduling plus file previews
Not ideal for
  • Non-technical users who don't want to configure their own AI model
  • Buyers who want a plug-and-play cloud assistant with no local setup
  • Linux desktop users (no Linux build documented)
Visit Website

IntermediateInstall is a one-click download for macOS (Apple Silicon ARM64) or Windows 10/11 (x64). Developers and users who already run a local model should reach first value in roughly 15–30 minutes once the onboard command is configured. If you've never set up a local model, budget an hour or more for choosing a model that fits your hardware and getting inference working before Maxclaw is useful.DesktopNo public APIVerified 5d ago
Pricing
Free
FreeFree tier3 hidden costs
Learning curve
Intermediate
Install is a one-click download for macOS (Apple Silicon ARM64) or Windows 10/11 (x64). Developers and users who already run a local model should reach first value in roughly 15–30 minutes once the onboard command is configured. If you've never set up a local model, budget an hour or more for choosing a model that fits your hardware and getting inference working before Maxclaw is useful.
Runs on
Desktop
No public API · 7 integrations
Who it's for
Privacy-conscious office workerDeveloper running a local modelSmall team on self-hosted AI
Live sentiment
Is Maxclaw actually worth it?

We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.

  • Honest verdict, not marketing
  • Real pros & cons from real users
  • Attributed quotes with receipts
Run a free scan

3 free scans · no card needed

Skip it if

Skip Maxclaw if you want to install an assistant and start chatting without configuring a local AI model first, or if your daily machine is Linux or a phone — the documented builds are macOS Apple Silicon and Windows 10/11 x64 only.

The 30-second take
Biggest gripe

The app is free, but running the local model it depends on consumes your GPU/CPU and electricity — on a laptop that shows up as battery drain and heat during long agent runs.

Price reality

At $0 under an MIT license, Maxclaw costs nothing and competes with paid cloud agents like ChatGPT Plus and Notion AI that charge ongoing subscriptions — but that comparison only holds if you already own a machine that can run a local model. Budget for hardware, not licenses.

In short

Maxclaw — Free, open-source (MIT) desktop AI assistant that runs fully locally in Go, with browser automation, a real terminal, and multi-channel chat. Best for Privacy-conscious office workers who need offline AI automation, Developers who want a local agent with terminal and browser control, Teams self-hosting AI for sensitive data handling. Free to use.

What people actually say about Maxclaw — is it worth it?

We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.

3 mentions across 2 sources (Hacker News, GitHub) · researched Jul 3, 2026.

55% positive45% critical

Average across the 2 sources that answered — each source counts once, not each post.

Recurring strengths
  • +100% local-first with zero cloud dependency ensures full privacy.
  • +Low memory usage due to Go implementation and designed efficiency.
  • +Free and open-source (MIT) with no paid tiers or hidden fees.
  • +Supports browser automation: login, click, fill forms, screenshot.
  • +Built-in terminal and file preview for PDF, Word, Excel, code.
Recurring frustrations
  • −Almost no community feedback – adoption appears very low.
  • −Documentation quality unknown – no user guides or tutorials found.
  • −Uninstall may leave residue based on prior OpenClaw experience.
  • −Dependence on MiniMax models may limit model choice or privacy.
  • −No evidence of ongoing maintenance or updates since early 2026.
Patterns worth knowing
Privacy-focused local-first design is the main selling point
Seen on Hacker News, GitHub
Extremely low community engagement and lack of user reviews
Seen on Hacker News, GitHub
Association with MiniMax raises questions about true local-first
Seen on Hacker News
Learning curve
intermediateProductive in ~A few hours
Hidden costs people mention
  • • May require purchasing API keys or hosting for MiniMax models if used
  • • No paid tiers – but self-hosting has infrastructure costs

Viability Score

61/100
Monitor

How well maintained and how widely used is Maxclaw? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this

Recent activity
not measured
Traction
55
Site health
95
User sentiment
55
What the vendor publishes
40

Last calculated: October 2026

How we score →

Key Features

  • Local-first AI assistant with zero cloud dependency
  • Real-time streaming chat with typewriter effect and smart interruption
  • Dark and light themes with a modern rounded-card UI
  • Browser automation: multi-step login, click, form fill, screenshot
  • Reuses Chrome login state to reach authenticated sites without re-verification
  • File preview pane for PDF, Word, Excel, images, and code
  • Integrated terminal using node-pty and xterm, same stack as VS Code
  • Smart scheduling with Cron, Every, and Once triggers plus visual editing
  • Task execution history tracking for scheduled jobs
  • Multi-channel access: Telegram, Discord, WhatsApp, Slack, email, Feishu, QQ
  • Long-term memory: fact memory plus history summaries across sessions
  • Skill system using @skillname to load domain-specific knowledge
  • Per-task session isolation with artifacts auto-saved to disk
  • Offline capability: works without an internet connection after setup
  • Cross-platform support: macOS Apple Silicon (ARM64) and Windows 10/11 (x64)

About Maxclaw

FreeIntermediateNo APIDesktop

Maxclaw is a free, open-source (MIT licensed) desktop AI assistant built in Go that runs entirely on your own machine. You bring your own local model (configure it via the onboard command, e.g. through llama.cpp) and Maxclaw supplies the agent layer: multi-step browser automation that can log in, click, fill forms, and take screenshots while reusing your existing Chrome login state; an integrated terminal built on node-pty and xterm with task-isolated sessions; an inline file preview pane for PDF, Word, Excel, images, and code; and smart scheduling with Cron, Every, and Once triggers plus execution history. A long-term memory system keeps fact memory and history summaries across sessions, and a @skillname system loads domain-specific knowledge on demand. You can reach the agent from Telegram, Discord, WhatsApp, Slack, email, Feishu, and QQ. Because nothing leaves the device, Maxclaw works without an internet connection. It ships for macOS (Apple Silicon ARM64) and Windows 10/11 (x64) only. It is aimed at privacy-conscious office workers and developers willing to configure their own model, not at buyers who want a plug-and-play cloud chatbot.

Behind the Verdict

Maxclaw's pitch is unusually honest for this category: it does not pretend to be a model. You install the app, run the onboard command to point it at your local model, and the product you're actually buying (for $0) is the agent scaffolding around it. That scaffolding is where the value sits. Browser automation handles multi-step work — login, click, form fill, screenshot — and reuses your Chrome login state so it can reach pages behind authentication without re-verifying each time. The terminal is not a toy: it uses the same node-pty plus xterm stack as VS Code, sessions are isolated per task, and the theme follows the app. File preview keeps PDF, Word, Excel, images, and code visible in a right-hand pane, and session artifacts land on disk automatically, separated by task. Scheduling covers Cron, Every, and Once with visual editing and execution history, which is how the "7×24" claim in the marketing actually gets delivered — the agent runs on a timer, not because a cloud is always on. Memory is the second differentiator: fact memory plus history summaries carry context across sessions, and the @skillname system lets you load domain-specific knowledge instead of re-explaining your field every time. Multi-channel access to Telegram, Discord, WhatsApp, Slack, email, Feishu, and QQ means the same local agent answers wherever you already are. The weaknesses are structural, not cosmetic. Everything depends on you configuring a local model correctly, and the seed material is explicit that non-technical users will struggle here. Local inference needs a reasonably capable machine and there is no cloud fallback if yours can't keep up. Platforms are macOS (Apple Silicon ARM64) and Windows 10/11 (x64) only — no Linux build, no mobile app. And the project is young enough that "© 2025 maxClaw" is the only date on the site; there is no published changelog with dates, so you can't yet track release cadence. Where it fits: developers and privacy-first operators who already run local models, want terminal and browser control in one agent, and are comfortable living in configuration. Where it doesn't: teams that need multi-user management, anyone expecting to install and chat in five minutes, and anyone whose main machine is Linux or a phone.

Researching Maxclaw? Get your full AI stack in 60 seconds.

Free, no signup — tell us your goal and get tools matched to your budget & existing stack.

Real-world workflow fit

Concrete scenarios for the personas Maxclaw actually fits — and what changes day-one when you adopt it.

Privacy-conscious office worker

Install the macOS or Windows build, run the onboard command to point Maxclaw at a local model, then schedule a Once job that logs into an internal portal, fills a weekly report form, and saves a screenshot to the task's artifact folder.

Outcome: The recurring report is produced on-device without any document, credential, or screenshot leaving the machine, and the execution history confirms each run.

Developer running a local model

Ask the agent in a chat session to inspect a repo, then drop into the integrated node-pty/xterm terminal to run a build in a task-isolated session while previewing the generated config file in the right-hand pane.

Outcome: Code, model context, and build output all stay in one local workspace with no external API calls, and the session's artifacts are written to disk automatically.

Small team on self-hosted AI

Connect Maxclaw to a team Slack or Telegram channel and use @skillname skills to load a shared knowledge domain, so teammates can ask the local agent questions about sensitive internal material.

Outcome: Team queries are answered from the local agent and memory carries context between sessions, with sensitive documents never crossing a cloud boundary.

Use Cases

Limitations

  • Maxclaw ships no model — you must bring your own local model and configure it via the onboard command.
  • Local inference also means your hardware is the ceiling: a reasonably capable machine is required to run an LLM well, and there is no cloud fallback if yours can't.
  • Platform coverage is macOS (Apple Silicon ARM64) and Windows 10/11 (x64) only, with no documented Linux or mobile build.
  • The site also publishes no dated changelog, so release cadence and fix history aren't observable from the vendor pages.

as of 2026-10-04

Verification history

We have re-verified Maxclaw 7 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.

  1. — re-checked, vendor evidence unchanged
  2. — re-checked, vendor evidence unchanged
  3. — re-checked, vendor evidence unchanged
  4. — re-checked, vendor evidence unchanged
  5. — re-checked, vendor evidence unchanged
  6. — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it

Showing the 6 most recent of 7 verification passes.

Free to cite with attribution — this page re-verifies continuously.

12-month cost

Project the real annual outlay, including the implied monthly cost when only an annual tier is published.

Annual total
Free
Over 12 months
Effective monthly
Free
Billed monthly

Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.

Plans compared

For each published Maxclaw tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.

Free

$0/mo

Ideal for

Solo developers and privacy-conscious users who own a machine capable of running a local model and want browser automation plus a real terminal at no cost.

What this tier adds

Starting tier and the only tier: $0/mo, MIT-licensed, with browser automation, file preview, integrated terminal, scheduling, multi-channel access, and memory included.

Hidden costs & gotchas

What the public pricing page doesn't put in bold. Captured from pricing-page footnotes, contract terms, and recurring complaints.

  • The app is free, but running the local model it depends on consumes your GPU/CPU and electricity — on a laptop that shows up as battery drain and heat during long agent runs.
  • There is no cloud fallback when your hardware can't keep up with the local model, so weak machines pay in latency or become unusable rather than in dollars.
  • Scheduled Cron/Every/Once jobs run against your own machine, so an always-on agent implies leaving a capable desktop powered on rather than paying a small cloud bill.

Where the pricing makes sense

The company stage and team size where Maxclaw's pricing actually pencils out — and where peers do it cheaper.

At $0 under an MIT license, Maxclaw costs nothing and competes with paid cloud agents like ChatGPT Plus and Notion AI that charge ongoing subscriptions — but that comparison only holds if you already own a machine that can run a local model. Budget for hardware, not licenses.

Setup time & first value

How long it actually takes to get something useful out of Maxclaw — broken out by persona, not the marketing-page minute.

Install is a one-click download for macOS (Apple Silicon ARM64) or Windows 10/11 (x64). Developers and users who already run a local model should reach first value in roughly 15–30 minutes once the onboard command is configured. If you've never set up a local model, budget an hour or more for choosing a model that fits your hardware and getting inference working before Maxclaw is useful.

Switching to or from Maxclaw

How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.

Migrating in
  • →From ChatGPT or other cloud chat assistants: replicate your prompt habits in Maxclaw and route the same tasks through browser automation and the integrated terminal so the work stays on-device.
  • →From local llama.cpp or similar CLI setups: keep your existing model files, then run the onboard command so Maxclaw drives them with browser, terminal, scheduling, and memory layered on top.
  • →From generic cron or Task Scheduler scripts: move the jobs into Maxclaw's Cron/Every/Once scheduler to gain visual editing and execution history alongside the AI step.
Migrating out
  • ↗To a cloud assistant (for example ChatGPT): export notes from Maxclaw's fact memory and history summaries and paste the relevant context into your cloud account, accepting that processing leaves your device.
  • ↗To a raw llama.cpp or Python agent stack: keep the same local model files and rebuild the browser automation and scheduling steps as scripts, trading the GUI and memory system for full control.

Integrations

TelegramDiscordWhatsAppSlackFeishuQQEmail

Resources & Guides

Tutorials & Learning

YouTube returned 6 videos for “Maxclaw”, and we withheld 6: 6 could not be judged, because “Maxclaw” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about Maxclaw.

Tools that pair well with Maxclaw

Common stack mates teams adopt alongside Maxclaw, with the specific reason each pairing earns its keep.

Featured Head-to-Head Comparisons

Alternatives to Maxclaw

View all
Atomic Chat

Atomic Chat

Atomic Chat is a free, open-source desktop and mobile AI app that runs 1,000+ local LLMs on your own hardware, with no account and no rate limits.

FreeTry
Cortex.cpp

Cortex.cpp

Free, open-source desktop app to run 123 HuggingFace models locally or route prompts to Claude, GPT, Gemini and DeepSeek with your own API keys

FreeTry
Cherry Studio

Cherry Studio

Free open-source desktop AI workbench that runs 300+ cloud and local models in one app

FreeTry

Frequently Asked Questions

Used Maxclaw? Help shape our editorial sentiment research.