BetaEditorial Listing

OpenHuman

TinyHumans · OpenHuman: Open-Source Desktop AI Agent with Local Memory, App Integrations, and Workflows

Open OpenHuman

OpenHuman is an open-source (GPL-3.0) personal AI agent for macOS, Windows, and Linux that syncs your email, chat, and work apps into a local, readable memory, then answers questions, runs workflows, and acts across those apps with your approval. It suits individuals who want a desktop agent that knows their context without wiring API keys or running a server.

PricingFreemium
Setupeasy
Runs onDesktop · Self-hosted
APIYes
Open sourceYes
DocsYes
CategoryProductivity
Open SourcePersonal AssistantDesktop AppLocal-FirstPersistent MemoryWorkflow AutomationMulti-AgentVoiceMCPBYOKLocal ModelsMeeting Notes

Best for

Individuals and solo operators on macOS, Windows, or Linux who want a desktop agent that keeps a local, readable memory of their email, chat, and work apps and can act across them, without wiring API keys or running a server

Not ideal for

Teams that need a supported, stable product today, people who want an assistant that lives only inside chat apps on a server, mobile-first users, and anyone who needs every byte, including voice, to stay on the device

Who it's for

Knowledge workers, founders, and technical individuals who want a personal desktop agent with persistent memory of their own apps and data

Capabilities

  • Memory Tree: connected sources are converted to Markdown chunks, scored, and folded into per-source, per-topic, and per-day summary trees stored in SQLite on your machine
  • Obsidian vault mirror of memory, so you can browse, edit, and link the agent's notes by hand and have edits picked up on the next ingest
  • Swappable memory engine: keep the local default, or switch to TinyHumans-hosted CortexDB or to Supermemory, Mem0, or Cognee with your own endpoint and key
  • 118+ third-party integrations (Gmail, Outlook, Google Calendar, Drive, Notion, GitHub, Linear, Jira, Slack, Salesforce, HubSpot, Stripe, Shopify, and more) through one-click OAuth brokered by Composio
  • Auto-fetch every 20 minutes pulls fresh data from supported connections into memory, and live app events can trigger agent actions
  • Agent-proposed workflows on the open-source tinyflows engine: describe an automation in chat, review the graph on a canvas, then save it to run on schedules or app events with approval steps
  • Orchestrator that spawns sub-agents up to three levels deep, with checkpointed runs that pause for your input and resume, and a circuit breaker that stops repeated-call loops
  • Built-in tools: web search, web scraper, coder toolset (filesystem, git, lint, test, grep), browser and mouse/keyboard control, cron scheduling, and memory tools
  • Voice: push-to-talk and toggle dictation with streaming transcription, spoken replies, and a Google Meet agent that transcribes calls into memory and can speak into the meeting
  • Approval gate that classifies tool calls (read, write, network, install, destructive) and holds side-effecting actions until you approve
  • Model choice: managed TinyHumans routing with automatic per-task model selection, 26 bring-your-own-key providers (OpenRouter, OpenAI, Anthropic, Google, Groq, Mistral, DeepSeek, and others), Claude Code or the Claude Agent SDK, or local runtimes (Ollama, LM Studio, MLX)
  • Privacy Mode with a local_only setting enforced in the Rust core that refuses cloud model calls, network tools, web search, integrations, and cloud embeddings
  • Two-way messaging channels including Telegram, Discord, iMessage, Slack, WhatsApp, Signal, email (IMAP/SMTP), Lark, and DingTalk; Telegram and Discord can be linked through OpenHuman, while most others use your own bot or account credentials
  • MCP server registry and a browsable catalog of about 90,000 SKILL.md skills
  • Headless core can run on a Linux server or VPS (Docker Compose, Fly.io, DigitalOcean) with the desktop app connecting to it, and an embeddable Rust library for other products

Limitations

  • Labelled early beta by its developers, who warn users to expect rough edges
  • The default setup routes sign-in, model calls, managed integrations, and web search through TinyHumans' hosted backend; hosted features such as the meeting agent and real-time integration triggers still need it even when you use your own or local models
  • Voice is not covered by local-only Privacy Mode: there is no local speech-to-text engine, so dictation and meeting transcription still go to the hosted proxy or a third-party provider
  • Not every integration feeds memory: only services with native providers (such as Gmail) are ingested automatically, while others are callable as tools only
  • Meeting support is documented for Google Meet only; the README's mention of Zoom, Teams, and Webex is not backed by the feature docs
  • The iOS companion app is experimental and not part of the shipped product, so there is no supported mobile client
  • A remotely hosted core does not serve the full app as a web UI; desktop features still need the Tauri app
  • Licensed GPL-3.0, which matters if you plan to embed or redistribute the core inside your own product
  • The Linux build is x64 only, and the AppImage can fail on some newer distributions, where the .deb package is recommended

Use cases

  • Asking for a morning briefing of what changed across Gmail, Slack, and Calendar in the last 12 hours
  • Querying everything a colleague said about a project across email and chat
  • Having the agent draft a workflow that summarizes new customer emails and posts them to Slack, then reviewing and saving it
  • Sending an agent into a Google Meet call to transcribe it into memory and answer questions afterward
  • Running a private assistant on a local Ollama model with Privacy Mode set to local-only
  • Letting the agent tidy and rename a project folder inside a boundary you set, with each change approved

Our take

OpenHuman's pitch is that a personal agent is only as useful as what it already knows, so it does the ingestion for you: connect Gmail and Slack once and a local, readable memory fills itself every 20 minutes. That, plus a real desktop UI, agent-drafted workflows you approve on a canvas, and a default managed account that hides API keys, is what separates it from OpenClaw and Hermes Agent, which are built around chat apps or a terminal and are usually run on your own model keys. The convenience has a cost: the easy path runs inference and integrations through TinyHumans' backend, so 'local-first' describes where memory is stored more than where your data is processed, unless you switch to local models and Privacy Mode and accept fewer features. It is also early beta with a very fast release pace, so it suits people comfortable with change more than teams that need stability.

Who should use it

Individuals who live in Gmail, Slack, Notion, and GitHub and want an agent that already has that context, people who prefer a desktop UI over configuring an assistant in a terminal, and privacy-minded users willing to run local models with Privacy Mode.

Who should skip it

Teams that need vendor support and a stable release, users who want a chat-app-only assistant on an always-on server (OpenClaw or Hermes Agent fit better), people who need a mobile app, and companies that cannot accept GPL-3.0 for embedding.

Strengths

  • Memory fills itself from connected apps and stays on your machine as Markdown and SQLite you can read in Obsidian
  • Desktop app with one-click OAuth integrations, so no API keys are needed on the default path
  • Agent-drafted workflows that you review and approve before they run
  • Choice of managed models, your own keys, or local runtimes, with an enforced local-only mode
  • Approval gate on side-effecting actions by default
  • Open source under GPL-3.0 with very active development

Weaknesses

  • Early beta with frequent releases and rough edges
  • Default path sends inference and integration calls through TinyHumans' servers
  • Voice and some triggers still depend on hosted services
  • No supported mobile app yet

OpenHuman pricing

Open source / pay as you go

Free

  • OpenHuman software is free under GPL-3.0
  • Bring your own provider keys or run local models at no TinyHumans cost
  • Managed usage billed from a credit balance topped up from $5
  • Optional auto-recharge when the balance runs low

Basic

$20 ($200/year)

Billed monthly

  • $21 of credits every month
  • LLM, embeddings, voice, and OAuth APIs through one TinyHumans key

Pro

$200 ($2,000/year)

Billed monthly

  • $210 of credits every month
  • Higher rate limits

Enterprise

Custom

  • Custom usage
  • On-premise deployment
  • SSO / SAML, dedicated onboarding, and priority support

Free tier limits: No subscription is required. The app runs free with your own keys or local models; managed inference and services draw from a prepaid credit balance.

Note: Plans are TinyHumans account plans shared across its products and are sold as credits, where one credit is one dollar of metered usage; the pricing page describes them mainly in terms of TinyHumans' OpenCompany, Medulla, and API products, and OpenHuman's managed services run on the same TinyHumans key. OpenHuman's own billing documentation lists Basic at $19.99 a month ($199 a year) and Pro at $199.99 a month ($1,799.99 a year) with per-call discounts instead of bonus credits, so confirm the current terms on TinyHumans' pricing page. Calls made with your own provider keys are billed by that provider. TinyHumans states that subscription and credit purchases are non-refundable.

Technical specs

Modalities

Text, Voice, Vision, Browser automation, Computer use

Available models

TinyHumans managed routing (automatic per-task model selection)26 BYOK providers including OpenRouter, OpenAI, Anthropic, Google, Groq, Mistral, DeepSeek, Together, and FireworksClaude Code / Claude Agent SDKOllama, LM Studio, MLX, and local OpenAI-compatible servers

Where OpenHuman excels

A daily briefing across inbox and chat

Because auto-fetch keeps Gmail, Slack, and Calendar synced into memory, a question like "what do I need to know from the last 12 hours?" can be answered from your own data without copying anything in.

Turning a repeated chore into a workflow

You describe the automation in chat, the agent drafts a workflow graph, and nothing runs until you save it on the canvas. Runs can pause at approval steps and resume, with step-by-step history.

Meeting notes that feed long-term memory

The Google Meet agent transcribes the call into the Memory Tree, so later questions can draw on what was said alongside email and chat.

A private assistant on local models

With Ollama, LM Studio, or MLX and Privacy Mode set to local-only, the core refuses cloud model, search, and integration calls, which suits sensitive personal or client material (voice excepted).

OpenHuman vs. competitors

OpenHuman vs. OpenClaw

OpenClaw is an MIT-licensed assistant that routes messages from 20+ chat apps to agents you configure with your own model keys or local models, with skills and cron. OpenHuman is a GUI-first desktop app that ingests your connected apps into a local memory, adds agent-proposed workflows and an approval gate, and defaults to a managed TinyHumans account. OpenClaw fits people who want an assistant inside their chat apps under full self-managed control, and OpenHuman fits people who want app context and automations without configuring providers.

OpenHuman vs. Hermes Agent

Hermes Agent is an MIT-licensed agent you run on your own machine or server with any model, building memory and skills from its own sessions and reachable from 20+ messaging platforms. OpenHuman builds memory from your connected apps rather than mainly from its own sessions, is designed around a desktop GUI with visual, agent-proposed workflows, and uses managed TinyHumans inference by default. Hermes suits developers who want a long-running server agent they control end to end, and OpenHuman suits individuals who want a desktop agent that already knows their inbox and tools.

OpenHuman vs. Claude Cowork

Claude Cowork is Anthropic's proprietary agent inside the Claude app that completes multi-step work across your files and connected tools on Claude models. OpenHuman is open source, keeps its memory locally as Markdown, lets you choose managed, bring-your-own, or local models, and adds scheduled ingestion and saved workflows. Cowork suits people already on a Claude plan who want a polished, supported product, and OpenHuman suits people who want an open, model-flexible agent with local memory.

Frequently asked questions

What is OpenHuman?

OpenHuman is an open-source personal AI agent from TinyHumans that runs as a desktop app on macOS, Windows, and Linux. It syncs connected apps such as Gmail, Slack, and Notion into a local memory, answers questions across them, runs workflows, and takes actions with your approval.

Is OpenHuman free and open source?

The software is free and open source under GPL-3.0. Managed model inference, web search, voice, and integrations on the default path draw on a TinyHumans account, which has pay-as-you-go credits and paid plans. You can also bring your own provider keys or run local models.

How much does OpenHuman cost?

The app is free. TinyHumans' pricing page lists pay-as-you-go credit top-ups from $5, Basic at $20 a month ($200 a year) with $21 of monthly credits, Pro at $200 a month ($2,000 a year) with $210 of monthly credits, and custom Enterprise plans. OpenHuman's own billing documentation lists slightly different prices and says every tier includes all features, with paid tiers mainly lowering per-call cost, so check the current pricing page before buying.

Can OpenHuman run fully locally?

Mostly. Memory is stored on your machine, and Privacy Mode's local_only setting refuses cloud model calls, web search, integrations, and cloud embeddings, allowing only local runtimes such as Ollama, LM Studio, and MLX. Voice is the exception: there is no local speech-to-text engine, so dictation still leaves the device. Sign-in and billing calls also continue.

OpenHuman vs OpenClaw: what is the difference?

OpenClaw is an MIT-licensed assistant that runs locally and works mainly through chat apps, using model keys or local models you configure. OpenHuman is a GPL-3.0 desktop app that ingests your connected apps into a local memory every 20 minutes, adds agent-proposed visual workflows, and by default uses a managed TinyHumans account for models and integrations.

Which models does OpenHuman support?

By default it uses TinyHumans' managed routing, which picks a model per task. You can also connect 26 bring-your-own-key providers including OpenRouter, OpenAI, Anthropic, Google, Groq, Mistral, and DeepSeek, use Claude Code or the Claude Agent SDK, or point it at Ollama, LM Studio, MLX, or another local OpenAI-compatible server.

Integrations & fit

GmailOutlookGoogle CalendarGoogle DriveGoogle DocsNotionGitHubLinearJiraSlackDiscordMicrosoft TeamsTelegramWhatsAppiMessageSignalSalesforceHubSpotStripeShopifyObsidianComposioOpenRouterOpenAIAnthropicGoogle GeminiOllamaLM StudioMLXMCP servers
Good fit forSolo / individual, Startup / small team
Pricing modelFreemium· Free tier available
See pricing on OpenHuman →

Alternatives to consider

About OpenHuman

OpenHuman, built by TinyHumans, is a Tauri desktop app around a Rust core. After sign-in you connect services such as Gmail, Slack, GitHub, Notion, or Google Calendar through one-click OAuth (118+ services, brokered through Composio), and every 20 minutes OpenHuman pulls fresh data from supported connections (those with native ingest, such as Gmail) into a Memory Tree: Markdown chunks, scored and folded into per-source, per-topic, and per-day summaries, stored in SQLite on your machine and mirrored as an Obsidian vault you can read and edit. That lets you ask things like "what's waiting on me?" or "what did Sarah say about the project across email and chat?" without pasting context in. On top of memory sit an orchestrator that spawns sub-agents with checkpointed, resumable runs, agent-proposed workflows that you review on a visual canvas before saving, a built-in toolbelt (web search, scraper, coder tools, browser and computer control, cron), voice dictation and spoken replies, and a Google Meet agent that transcribes calls into memory and can speak in them. Side-effecting actions such as sending an email or running a shell command go through an approval gate by default. The difference from OpenClaw and Hermes Agent is mostly about where your context comes from and who supplies the services: those are built around chat apps or a terminal and are usually set up with your own model keys, while OpenHuman is a GUI-first desktop app that builds memory from your connected apps and, by default, routes models, search, voice, and integrations through a TinyHumans account, with bring-your-own-key, local models (Ollama, LM Studio, MLX), and an enforced local-only Privacy Mode as options. The same core also ships as a terminal client and an embeddable Rust library. The tradeoffs: it is labelled early beta, the easy path depends on TinyHumans' backend, voice still leaves the device even in local-only mode, and the project is GPL-3.0 rather than MIT.

Updates from OpenHuman

New Featurev0.64.0 "The Intelligence Upgrade"

OpenHuman v0.64.0 merged 674 pull requests, adding always-on listening and global push-to-talk for hands-free desktop control, faster command routing, and upgrades to memory sync, ingest, and retrieval. Point releases continued through v0.64.10 on September 30.

Are you the founder? Claim this listing →