I Gave an AI Agent the Keys to My Life (Here's What Happened) — Radek Sienkiewicz (@velvetshark-com)
TL;DR
Radek didn’t hand over control all at once — he built trust one channel and one workflow at a time — He started with a single chat interface on WhatsApp, later moved to Telegram and Discord, then layered in tasks gradually instead of doing a risky “install OpenClaw and let it run my life” leap.
The real unlock was plugging the agent into his 3,000-note Obsidian vault — Once OpenClaw could search, index, and connect years of work, research, tasks, and bookmarks, it stopped being a chatbot and became a context-rich system that could reason across his life.
His agent turns dead bookmarks into an active knowledge base — When Radek drops in a tweet, thread, article, or YouTube link, it analyzes the content, tags it, connects it to existing notes, and resurfaces related material he had forgotten, which he says is where the setup became “super super useful.”
A lot of the value happens while he sleeps — Between roughly 3 and 6 a.m., the system backs up files, refreshes indexes, updates OpenClaw, and prepares morning summaries so he wakes up to a fresh, ready-to-go workspace with only a few hours of worst-case data loss exposure.
The flashy part isn’t autonomy — it’s attention filtering with context — Because the agent can see emails, calendars, notes, and project history, it can flag urgent things like a failed Netflix payment or domain renewal, and even draft replies using project-specific context already stored in Obsidian.
Radek’s biggest lesson is that inspectable, editable systems beat magical ones — His setup depends on markdown memory files, scripts, and “critical rules,” and he warns that bad memory, brittle 10-step automations, noisy notes, and weak boundaries will compound if you don’t maintain them.
The Breakdown
From “just a chat” to “keys to my life”
Radek opens with the big claim: OpenClaw can access his email, notes, files, calendar, tools, and even operating system-level automations — basically anything he can do on his computer. But he immediately undercuts the sci-fi framing: this was not one dramatic handoff, it was a series of tiny steps starting with a single messaging channel and one simple workflow at a time.
Why his “simple setup” turned out not to be simple at all
He says he long assumed his setup was pretty modest because he never made one huge architectural jump. Then he started seeing Twitter threads, YouTube videos, and other people’s agent setups and realized his system actually included most of what others were showing — plus more sophistication — just because he kept iterating slowly and fixing failures as they happened.
The Obsidian vault is where the magic kicked in
The turning point was giving OpenClaw access to his knowledge base: around 3,000 markdown notes in Obsidian covering work, personal life, research, tasks, projects, and link inboxes. With search, memory, and cross-linked context layered together, the agent could finally operate on his history, not just his prompts — and that’s when Karpathy’s viral tweet about LLM knowledge bases felt to him like, well, yes, that’s already my life.
Turning bookmarks into connected thinking
One of his favorite workflows starts with something mundane: dropping a link into an inbox. Instead of becoming another forgotten Twitter bookmark, the agent analyzes the tweet, thread, article, or video, tags it, connects it to relevant notes already in the vault, and often reminds him of adjacent ideas he had completely forgotten — which is exactly why the new bookmark mattered in the first place.
What the agent does at 4 a.m.
While he’s asleep — usually sometime between 3 and 6 a.m. — the system is indexing, backing up, refreshing memory and QMD indexes, and preparing the latest state of everything for the morning. He’s also built update scripts so OpenClaw can verify whether a new version is safe before restarting the gateway, which keeps the whole thing from bricking itself overnight.
The five jobs: plumbing, filtering, drafting, research, and more
Radek groups the work into areas like ambient operations and attention filtering, and his Discord is organized around them with channels like inbox, consulting, video research, briefing, Instagram, YouTube, and OpenClaw. The most vivid examples are small but real: a failed Netflix payment caught and fixed within five minutes, a domain renewal surfaced before he missed it, and emails drafted with project-specific context already pulled from his notes.
Under the hood: judgment from the LLM, reliability from files and scripts
He’s clear that this only works because many parts cooperate: the LLM handles judgment and synthesis, while scripts handle deterministic “if this happens, do this” tasks without wasting model calls. He also emphasizes memory design — agent files, soul/sol files, critical rules, and now a fuller memory folder with “dreaming” and promotion — because OpenClaw stays useful precisely because the system is inspectable markdown, not opaque magic.
His closing metaphor: building for future-you
The talk ends on a very human framing: past him was lazy, present him had to clean up the mess, and future him felt like some all-powerful “god creature” who would somehow handle everything later. The agent’s real job, he says, is to become a helper for future-you — doing as much as possible overnight so tomorrow starts with less friction and more momentum.