A self-hosted personal assistant. It reads the messages you send it, works on them, and answers back on the chat apps you already use. This instance runs on hardware I own, in the Czech Republic, and is operated by me alone.
NanoClaw is not a hosted service and there is no sign-up. Each installation is a copy running on its owner's own machine, holding its own data and its own credentials. This page describes the installation that operates under the OAuth client named NanoClaw.
Every morning it prepares a briefing and delivers it to a private Discord channel and, as a PDF, to a reMarkable tablet. To do that it:
The rest of the day it answers questions in chat — on WhatsApp, Discord and GitHub — looks things up, drafts documents, checks web pages in a real browser, and keeps notes in a private wiki.
The briefing needs access to a calendar and a task list, so this installation requests those permissions from Google. Mail is read over IMAP with a mailbox-specific password, not through a Google permission.
Nothing is sold, shared or advertised against. The privacy policy sets out exactly which permissions are requested, what each one is for, where the data goes and how to revoke access.
NanoClaw is open source. Each agent runs in its own container with its own workspace, its own conversation history and its own credentials, so one agent cannot read another's data. Credentials live in a local vault and are injected per request — they are never placed in chat, in environment variables, or in the agent's context.
I build and maintain these for other people. A typical engagement is: install NanoClaw on your own machine or a small server you control, connect the chat channels you actually use, wire up the accounts it should work with, write the instructions that make it useful for your work, and keep it running.
Things I have built and run in production: WhatsApp, Discord and GitHub channels; scheduled daily briefings across three mailboxes, a calendar and two task systems; a bridge that reads handwriting off a reMarkable tablet and sends documents back to it; a stakeholder-facing agent for a client project, isolated so it can only see what that project needs.
Your installation stays yours: your hardware or your server, your accounts, your data, and your own Google Cloud project where one is needed. If you want to stop, you switch it off.
Write to jan@bartunek.dev.