Sven, the Raven That Works With Me

TL;DR

Sven is my personal AI raven. Every morning he flies out over my tools (mailboxes, calendar, CI, server status, open tasks) and brings back a single report: the Morning Pulse in Discord. Instead of checking five places, I read one post. Over Discord I also hand him small work in conversation: "build idea two into a script outline." Sven drafts, I decide. The hard rule behind it: Sven proposes, but never publishes on his own. He is self-hosted, built on the open-source runtime OpenClaw, and the orchestration on top is my own layer. This article is the deep look at that one agent. In Building an Agent Fleet he stands in the ensemble; here he stands alone.

The Problem: The Signal Sits in Five Places

As a solo builder I run several products, a blog, presences on multiple platforms, email, CI, and a server. The state of all of it lives in different places. In the morning that would mean: open the inbox, open the calendar, open the CI dashboard, open the server status, open my own task list. Five contexts, five tabs, five chances to feel I have missed something.

The real problem is not the volume. It is the scatter. A meeting that collides with a red CI run only shows itself if both places are open in the same moment. What matters gets lost in the noise of many places, not in the mass itself. I did not want another dashboard to open on top of the rest. I wanted the opposite: one place fewer, not one more.

That is exactly what Sven is for.

The Raven as Blueprint: Huginn and Muninn

Sven is named after Odin's ravens. In the myth, Huginn (thought) and Muninn (memory) fly out over the world each day and return to Odin to report what they have seen. That is not a pretty label; it is the blueprint of the agent. The persona is the architecture.

Sven does precisely that: he flies out, gathers signal across my tools (mailboxes, calendar, CI, server status, open tasks) and returns with a single report. One raven, not a swarm of notifications. The guiding principle is already in the name: signal, not noise. Not everything that happened, but what counts today.

The Morning Pulse: One Post Instead of Five Tabs

The Morning Pulse is what comes out of it. Instead of checking five places, I get one Discord post each morning. In it, Sven folds together what lay scattered:

My open tasks. What is due today, from my own list, not from memory.
The calendar. The day's appointments, in the same view as everything else.
The mail. What is in the inbox and wants attention, condensed, not as a raw stream.
The CI status. Whether the pipelines are green or something turned red overnight.
The server status. Whether the machine everything hangs on is running.

The result is a paragraph, not a mountain. I read it over the first coffee and know where the day stands, without five tabs, without the worry that something slipped between two tools. The value is not a new capability but the removal: one place instead of five.

The Hand-Off Runs Over Discord

Discord is the surface I work with Sven on. The Morning Pulse arrives there, and there I hand back too. It runs in conversation, not through a form: "build idea two into a script outline," and Sven delivers a draft. I read, correct, decide.

That is the part that takes work off me. Not by an agent putting things into the world on its own, but by making the first version while I keep the last. The draft is cheap; the decision stays with me. My time shifts from "start everything myself" to "pick the best and sharpen it."

Here Sven is clearly distinct from another agent in my fleet. BuilderBob runs a site of its own and publishes there autonomously within firm bounds. Sven never does. He scouts, he assists, he drafts, and then he stops. That boundary is not a technical stopgap; it is the core of his design.

Sven proposes, I decide and publish. In public Sven never acts on his own: no commit, no external post without me. The Morning Pulse is a report to me, not a publication.

Built on Open Ground: OpenClaw

Sven did not start from zero. He is self-hosted and built on OpenClaw, an open-source runtime for personal AI assistants under the MIT license. I take that foundation as it is. What makes Sven Sven is the layer on top: the routing over Discord, a chain of models with automatic fallback, the scheduled jobs, the link to my knowledge base. That orchestration I built myself.

The point is not the brand of the runtime but the stance: stand on open, readable ground instead of renting a black box. When something jams, I can look into the foundation's code. My own layer I can read anyway, I wrote it.

Kept Small, on Purpose

Sven is deliberately lean. Less than a framework, more than a script. That is no accident but a reduction: the predecessor had grown too heavy, with too many capabilities I never needed. The current version is the trim-back to what works every day.

Small has a concrete advantage. I understand every part, and I can change every part without fear that three other things tip over. A small agent I fully see takes more work off me than a large one I only half understand.

Part of that trim-back is memory. Sven reads and writes into a knowledge base, a "second brain," a personal store where notes, decisions, and ideas sit in structured form. What turns out to be a durable decision, Sven mirrors there. So knowledge does not get stuck in the fleeting Discord log but lands in a place the next run can find again.

content-radar: Ideas on Demand

One thing Sven does on call, not on a schedule: the content-radar. When I ask, he scans AI, agent, and EU/AT-relevant sources and scores what he finds against a rubric for builder substance. Roughly: does the theme fit what I build? Is it relevant for Europe and Austria? Can I speak to it from my own building experience, or would it be borrowed opinion? Is it recent, does it have momentum, does it stand apart, and is there evidence for it?

What comes back is not a link dump but a handful of ideas, each with a hook and an angle I can make my own. I then decide whether one of them is worth a post. No fixed cadence, no automatic daily ration: the radar runs when I need it, in the loop with me.

And yes, this is self-referential: a radar like this could well put the idea for a post like this one on the table.

Conclusion

Sven takes work off me without taking decisions away from me. Three things make that work:

One place instead of five. The Morning Pulse folds scattered signal into one Discord post. The gain is not a new capability but the removal of the four other tabs.
He proposes, I decide. The draft is cheap and may come from the agent. Publication stays with me. That boundary is the honest core, not an afterthought restriction.
Open foundation, small own layer. Built on OpenClaw, kept deliberately lean, with a knowledge base as memory. An agent I fully see is an agent I can entrust work to.

AI is a tool, strong at gathering and condensing and blind to context. Sven shows it every morning: the value is not in the model but in the fit and the clear boundary.

If you want not just to admire something like this but to understand and build it yourself, that is exactly the kind of practice my tools come out of. A look at the fleet shows the ensemble, and my way of working says why I build this way. And if you would rather have it applied directly to a project: contact is the direct route.