PersonalClaw

One agentic OS.
Your machine.
Your rules.

Chat, autonomous goals, memory, knowledge, and automation behind one gateway you own.

Watch the tour
Local
Home view in the PersonalClaw dashboard

See what waits on you

Approvals, ready tasks, current work, and recent conversations stay visible from one home.

Check it before you trust it.

Each claim names its evidence and the release it was last checked against.

  • The release attaches SBOMs for the wheel and both container images.

    EvidenceRelease assets: The v0.3.9 release

    Last verifiedv0.3.9

  • A threat model maps each control to the OWASP Agentic Top 10.

    EvidenceThreat model: The OWASP mapping

    Last verifiedv0.3.9

  • Zero telemetry. Narrower than it sounds.

    EvidenceComparison row: The telemetry row

    Last verifiedv0.3.9

  • The code is under a permissive open-source license. Holds.

    EvidenceLicense file: LICENSE

    Last verifiedv0.3.9

Hand off the work. Keep the controls.

Delegate a goal, not a prompt.

A goal loop plans, works cycle by cycle under a deterministic supervisor, and reports against the goal. It runs without constant prompting, and never behind a spinner.

  • Pause, nudge, or stop a loop
  • Inspect every cycle and result
A finished PersonalClaw goal loop: its goal, its six cycles and the findings it recorded

Approve from the keyboard.

When an agent wants a tool that needs your say, the request waits in the chat and in your inbox. Cmd Enter (Ctrl Enter off a Mac) approves the request that has keyboard focus. A delete, a change outside the chat's folder, a send to other people, spending, or a tool that doesn't say what it does asks once more first.

Every key, in the keyboard guide
Needs you in PersonalClaw: an approval, a workflow's choice, a learned template and a skill proposal waiting, one answered on its card, and the panel open on the template

Your state stays home.

Everything PersonalClaw keeps lives in one folder on your machine. A model, a search engine or a channel is reached through something you add.

On your machine: ~/.personalclaw

  • Memorymemory.db, learning.db, lessons.jsonl
  • Knowledgeknowledge.db, sources, research_reports.json
  • Worksessions, projects, loop/loops.db, artifacts
  • Automationtriggers.json, crons.json, workflows
  • Platformapps, agents, skills, inbox
  • Configconfig.json, active_models.json, mcp.json
  • Securitycredentials, grants, security_events.jsonl

Across the network, when you add it

  • A model provider app you bind
  • A search provider app you bind
  • A channel app you connect
  • An MCP server you add

The one call it makes on its own, the update check, is on /compare, with how to turn it off.

The domains and stores are core's own list, from durability/inventory.py at v0.3.9. A snapshot is made of exactly these domains.

Every vendor is an app.

Models, search, speech, channels, tools and agent runtimes are apps you install and uninstall, each one a bundle with its own permissions. 69 first-party apps ship at this release.

Build on it.

An app is a folder with an app.json. When someone installs it, it lands in quarantine, a scan gives it a verdict, and it waits for their consent before it runs.

The app creation guide
web-tools/app.json, a first-party app at the pinned apps commit
{
  "name": "web-tools",
  "version": "0.1.6",
  "displayName": "Web Tools",
  "description": "General web primitives the agent can call: web_search, web_fetch, and web_extract. web_search runs over the search provider you bind in Settings \u2192 Search, web_fetch is an SSRF-guarded page fetch + extraction, and web_extract does structured extraction. No key of its own \u2014 it uses the bound search provider's.",
  "icon": "Globe",
  "author": "PersonalClaw",
  "license": "MIT",
  "minPersonalClawVersion": "0.2.3",
  "tags": [
    "tool",
    "web"
  ],
  "prompts": [
    "prompts/web-extract.yaml"
  ],
  "permissions": {
    "network": true
  },
  "provider": {
    "id": "tools",
    "label": "Search, fetch and extract web pages",
    "type": "tool",
    "implementation": "provider:create_provider",
    "capabilities": [
      "web"
    ]
  }
}

The model proposes; deterministic controls outside it decide what reaches your shell, your network and your apps. An app gets a scoped gateway token, and its own code still runs as you. How the boundary holds

Early, and honest about it.

PersonalClaw is pre-1.0: a release can change how your data is stored, with no automatic migration. Run personalclaw snapshot before you update, and personalclaw restore brings it back. What holds and what doesn't, row by row

The latest releases

  1. v0.3.9

    A command prints only what it makes now, and a check exits 1 when it finds what it checks for, so read getting-started's Updating before you update a script that reads one. Five parts of the app are redesigned. Needs you is one list of what waits on your answer: each card leads with what it asks and answers it there, and its panel shows the proposal itself. Library is one page of everything you keep, with a preview beside it. The Projects page says what needs you and what is running in each project, and a project's page opens on a box to start a chat there. A plan step is approved only as you read it, and a change to it after you read it is put to you again. The agent orb shows each state in a form of its own, from a still ring when it is ready to the claw mark when a turn is done.

  2. v0.3.8

    A workflow reads its secrets from Settings → Secrets alone now, so save any secret that only the gateway's starting environment held in Settings → Secrets before you update, then take it out of that environment. Chat preferences, the gear on the chat box, holds a chat's explanations, reply style and Optimize; how replies explain things is a setting in Agent defaults that reaches every chat, asked once in a small window; and the sidebar's chat history is one list, with a search and a Sort and filter menu. Home's Overview shows your agents and what they did today, and tasks, Home and notifications render what agents wrote. The desktop app updates an older gateway it found and uses one only at its own version or newer, its sidebar paints the web UI's colours, and a theme switch reaches the whole window at once. Hands-free voice explains itself, sends only when a confirmation phrase ends what you said, and keeps what you typed. Stopping a workflow run ends the agents and runs its steps started, and skipping a step inside a loop skips it in every cycle. The web image runs nginx 1.31.8, and the gateway image's agent CLIs run on Node 24.22.2.

  3. v0.3.7

    A browser's sign-in needs more than its cookie now, so every browser and paired device signs in once after this update, and the desktop app needs 0.3.7 or newer to open this gateway. A widget's action waits for you to send it, a project's secret file opens only for a chat you allow, computer use refuses a click that moves the real pointer until it can be held to the app it names, and an image from another site loads only when you press Load. The desktop app starts its own gateway when it opens, can use the one already serving its home, and updates itself when you press for it, and a gateway refuses a home a newer PersonalClaw has used. Home's Overview shows your agents' day, its Desktop and Browse live views show only while an agent drives this computer or a browse runs, and a page's controls sit in its header, in one order. Stop stops only the turn you pressed it for, renaming or pinning a chat no longer rewrites its transcript, a gateway on Linux no longer stops answering when the loop list and a background read meet, an MCP server's paged tool list is read to its end, and quiet hours keep the configured timezone.

Questions

Does it phone home?

No analytics, no crash reporting and no usage reporting of any kind - nothing about how you use it is sent anywhere. But the claim as stated is wider than the truth: by default PersonalClaw asks GitHub whether a newer release exists when it starts and then every twelve hours, identifying itself with a `personalclaw-update-check` user agent, and the desktop app asks too, a minute after it starts, at once when it finds a newer gateway running, and then once a day, with the same user agent. You did not ask it to. Since v0.2.0 a setting turns those automatic checks off (the row below), but they are on out of the box. If you grep the tree you will also find a `telemetry_salt` and a hashed owner id; at this release both stay on this machine - the salt is kept out of packs, exports and sync, the hash is shown only by the gateway's own status endpoint - and nothing transmits either.

`updates.check_enabled` (Automatic Update Checks, in Settings under Updates) turns it off. Every check PersonalClaw makes on its own - at start, on the interval, when a page showing update status finds one due, and before a staged install - asks that setting first, read fresh each time, so switching it off stops the next check without a restart, and the desktop app's own checks read the same setting. With it off, PersonalClaw reaches GitHub for updates only when you ask: Check now, an Update you press, the desktop app's Check for Updates, or `personalclaw update`. It is on by default.

The telemetry row and the update check row

What runs locally?

The gateway, the dashboard and everything under ~/.personalclaw. A local-model contract ships and is live: the model download and model-registry handlers list, fetch and remove models through it. A bundled chat app built on it lets a fresh install hold a conversation on this machine with no provider bound - a small model, downloaded once when you click for it, then run offline on the CPU. It is a floor, not a recommendation: bind a real model, local or hosted, for real work.

The local models row

Which models work?

Any model a Models app connects, hosted or on your own machine. 18 Models apps ship at this release.

The Models apps

Do I need Docker?

No. The installer uses uv and brings its own Python. Docker Compose is one of the other ways to run it.

The install guide

What can break between releases?

This is a 0.x release under a clean-break doctrine: when a design is replaced the old path is removed in the same change. The release's own README says the next few 0.x releases may introduce breaking changes with no automatic migration, that sessions, memory, knowledge, config and app state may need to be recreated after an update, and that you should not make this your only system of record yet. Run `personalclaw snapshot` before every update.

`personalclaw snapshot` and `restore` ship as CLI commands, and Settings > Backups & Data > Backups runs them too: by default a nightly snapshot and a monthly restore drill that restores the newest one into a temporary directory to prove it reads. A snapshot holds every store whole, each database copied through SQLite's backup API, and carries no credential value. `backup export` is a different thing - a deterministic, SHA-256-manifested export of your records, which the gateway also takes every hour, that sync carries and nothing restores from.

The data stability row and the backup row

How do approvals work?

A tool that needs your say waits for it: Allow or Deny on the approval, or Cmd Enter (Ctrl Enter off a Mac) on the one that has keyboard focus, and the riskiest actions ask once more.

The security model

Run it on your machine.

Read the docs