---
title: "A Slirc company, slirc.app and a marathon"
description: "Why the blog went quiet after Slirc's pre-launch: Slirc has a company now, slirc.app is up, I ran my first marathon, in Amsterdam, and there's a big project at Miro. Agents are next."
pubDate: "2026-10-22"
series: "Building Slirc"
part: 5
typora-root-url: ../../../public
---

On October 5th I wrote "see you tomorrow". Pre-launch happened the next day, and then this blog went quiet for two weeks. Slirc kept moving the whole time. I just didn't stop to write about it, so this is the catch-up.

## Slirc has a company now

I opened a company for Slirc. On paper it changes very little. In practice, it's now something I'm responsible for, beyond a weekend project I tinker with before/after work.

## slirc.app is up

Not everyone wants to run a server, even a small one. [slirc.app](https://slirc.app) will host Slirc for them. Each team will get its own instance at `yourteam.slirc.app`, with its own IRC server and daily backups, running in the EU. Pricing will start at €29 a month per instance for up to 250 users flat, and coding agents won't count as seats.

Right now signup is a [waiting list](https://slirc.app/#waitlist). During pre-launch you get a free instance until launch, and in return I ask for feedback. I set those up by hand, in the order people sign up.

## I ran a marathon

Amsterdam TCS Marathon 2026, 42km, my first one.

I have to write a whole post about it. How I went from 23 to 42km, with basically no training. Don't recommend, but worked out for me. Nothing new, the first half marathon I ran in 2018 I went from 13 to 21km, and very little training...

<figure>
  <img src="/amsterdam-marathon-2026-start.webp" alt="Runners waiting at the start arch of the Amsterdam TCS Marathon, under a grey sky" loading="lazy" />
  <figcaption>2026, 50 years of the Amsterdam Marathon. A proper START funnel.</figcaption>
</figure>

## And something big at Miro

My day job is at Miro, and right now I'm working on something big there. It's taking a lot of my time and focus, which is part of why I haven't written here. I can't say what it is yet. When it's out, I'll write about it.

## Next: agents

[Part 4](/blog/prelaunch-tomorrow) ended with "*agents will follow*". They're close.

You'll connect a coding session you already have open to Slirc with one command, `/slirc-connect`. It works the same in Pi, Claude Code, OpenCode and Codex. The session gets its own name and a DM with you, and it only acts on your messages. Then you can ask it something from your phone, it does the work on your computer, and the answer comes back in the chat.

Pi already works in pre-launch. The other three are in testing now.

Getting four coding agents to agree on one command took longer than I expected, and I threw away a few approaches on the way. That's part 6.
