BTW Studio
← All work

A personal assistant in daily use.

A Telegram bot, an Android app and a background agent on a self-hosted server. It has run every day since April 2026.

Read the code
Chat: an answer with its steps, a result card, search across conversations
Events: signals grouped by source, read on sight, archived with a swipe
Watchdog: one alert per outage, false alarms swallowed with a diagnosis
Tasks and projects: today, deadlines, progress per project
Planner: counters, checklists, a study journal, unfinished items carried over
Finances: shared recurring payments, who pays, what is overdue
Home: the power schedule, devices, the server and model limits
Mail: what matters first, phishing quarantined, the reason for each verdict
News: a feed by topic with a short summary of each item
Content: drafts and scheduled posts for a Telegram channel
The whole app in two and a half minutes, with the interface switched to English for the recording. Demo data; chat replies are replayed from a script.

In plain words

One assistant for the small things that eat a day: tasks, mail that needs an answer, client messages, and the health of the server it runs on. It lives in Telegram and in a phone app, and it has been in daily use since April 2026.

How it works

  1. Talk to it

    Ask in chat or by voice. The answer shows the steps it took and a result card.

  2. Let it sort the noise

    Incoming signals arrive as grouped cards, one notification per batch.

  3. Let it watch the server

    One outage gives one alert. A short list of repairs it carries out by itself.

The problem

Tasks, mail, client replies and server alerts arrive in different places, and most assistants are demos that nobody uses a month later.

What we built

One assistant reachable from a chat and a phone app. Incoming signals become cards with one notification per batch. A watchdog monitors the server it runs on: one outage produces one alert, and a narrow set of repairs happens without a human.

How we know it works

In daily use sinceApril 2026
Releases shipped through pull requests60
Side effectssmoke-tested against the live system

The recordings use a fictional owner and seeded data; the app is used in Ukrainian, and its interface was switched to English for the recordings.

Built with
TypeScript, grammY, SQLite, Claude Agent SDK
Clients
Telegram, Android with over-the-air updates
Code
Private; the showcase repository describes the design

Under the hood

  1. ClientsTelegram bot and an Android app
  2. APIOne door for every client
  3. CoreTasks, mail, events, planner
  4. Memory and modelSQLite for state, Claude for reasoning
  5. WatchdogOn a schedule: checks the server, repairs a narrow list

Speech is transcribed locally on a GPU before it reaches the model.

Decisions and why

One alert per outage

While the server is known to be down, alerts about everything that depends on it are held back.

Repairs are a short, named list

It may restart one named container. Anything wider waits for a person.

Unused features get deleted

A usage audit over the full history retired ten modules that nobody opened.

The interface updates without reinstalling

The Android shell is rebuilt only when native code changes; the rest arrives over the air.