Your AI chief of staff

Less an app you check. More a chief of staff who keeps up.

Most assistants forget you the second you close the tab — and do nothing unless you ask. Vasya keeps a growing memory of your life and runs in the background, checking, drafting, and reminding before you ask. When you're ready, your household plugs in too.

Already onboarded? Sign in. Otherwise it's invite-only for now — you can request access.

heyvasya.com
Vasya
scheduled · 7:00 AM
Morning. Two things before your 9:30 — the dentist confirmed Thursday, and that flight you watched dropped $80. Want me to hold it?
yes, and add the dentist to the shared calendar
Done — held for 24h and added to the household calendar. I remember you like aisle seats, so I picked 14C.
Message Vasya…

Most assistants forget you
the moment you close the tab.

Vasya doesn't. Each capability is something it does for you — with the engineering that makes it trustworthy sitting right underneath.

It remembers you

Vasya keeps a structured, growing knowledge base about each person: preferences, the people in your life, the context that usually has to be re-explained every time.

Under the hood

Per-user wiki-LLM memory. Persists across every session and run — not a sliding chat window.

It works while you're not looking

Ask it to check something every morning and report back. It can also set its own reminder to follow up at the right moment later. Proactive, not just reactive.

Under the hood

Event-driven scheduler with hot-reloading cron config. Agents schedule future prompts for themselves.

And it scales to your household

Start solo. When you're ready, drop a Google Calendar or Notion workspace into a shared channel and the people you live with can use it too — without ever getting full access to your account.

Under the hood

Connections provisioned per shared channel. Scoped capability without credential sharing.

The part the engineers came for.

The friendly surface sits on architecture that takes isolation, scheduling, and memory seriously.

Isolated execution

Every run spins up an ephemeral sibling Docker container with hole-punched mounts. Container destroyed on exit.

Dynamic provisioning

Agent receives exactly the connections you enabled. The orchestrator reaches Docker through a locked-down socket proxy.

Async scheduling

An APScheduler-based orchestrator with watchdog hot-reload handles concurrency, misfires, and self-enqueued prompts.

The stack

Go backend, Next.js frontend, PostgreSQL, Gemini for reasoning — containerized, with multi-user-extended agent runtimes.

Want in?

Vasya is invite-only while we onboard people one at a time. Leave your email — and if you tell us what you'd want it to handle, you'll move up the list.