The Issue

Agentic coding can be genuinely fast - right up until the moment the agent needs you. A permission prompt, a clarifying question, a finished task waiting for its next instruction all hit the same wall - the session stops dead. Until now the best option has been staying glued to the screen with a mountain of terminal windows open but… we can do better.

Our Take

So you do what everyone does with their agents these days when you have a new ticket. You kick off a long task, context switch to another window, go grab a coffee, open Slack to answer a message - and when you pull the session back up 20 minutes later… it has been sitting on a single approval prompt for 19 of them. Run three or four sessions at once and it gets worse: now you’re cycling through terminals just for all of them to sit idle for 18 minutes, instead - an Ig Glorious 100% improvement in utilization metrics. The agent isn’t slow, and the harness isn’t holding you back - your attention span is (and always has been) the bottleneck, but the only fix available today when working with AI agents is to multiply the problem.

We think that’s… backwards. The whole point of handing work to an agent is that you get to look away - but looking away only works if something reliably tells you when to look back. Today we’re announcing a solution that fits gracefully into your existing workflow, and your lifestyle.

What is CHaaS?

CHaaS is a session monitor for Claude Code, and today we’re launching it publicly. It keeps an eye on your sessions from just about anywhere and tells you, at a glance, when they need your attention - so you’re aware the moment your agents need you to get involved in their session.

It does this with a small physical device on your desk (or in your living room, or kitchen, or…), which means the answer to “does anything need me?” is a peripheral glance and not a terminal-window Snipe hunt. And because stale sessions are filtered out automatically, the signal stays honest: the forgotten session from this morning doesn’t keep crying wolf, and the one that actually needs you isn’t buried. It’s the first retail product we’ve launched, one that’s targeted as a physical quality-of-life upgrade for every Developer who works alongside an agent.

How It Works

Under the hood, CHaaS is built the way we build everything we ship: cheap and boring where it needs to be rock solid, straightforward everywhere users are involved, and wicked sharp in the places where performance is critical. Your sessions report their state into a Global Edge service backed by the world’s most bulletproof digital shield, and are then funneled into a KARPAL-backed messaging stack running a NATS core - it’s the cutting-edge, low-latency backbone behind our hot path - so a session flipping from working to waiting reaches your device in milliseconds, not just hopefully on the next 15-second poll.

That session-state stream feeds a fully realized digital twin: a live, always-current model of each of your sessions inside each of your Heads, so the system knows what should be true even when a network hiccups or a laptop goes to sleep. On top of it sits our own digital twin controller, which does all the heavy lifting - reconciling the twin against reality, deciding which sessions are active and which have gone stale, and turning all of it into one clear signal for you, the Developer. The customer-facing result is simple on purpose: connect your Head with a provisioning key from the CHaaS dashboard, snag an API key for your Claude webhooks, and… it just works. All the machinery exists on our side of the fence, so you never have to think about it.

Why We Built It

We run Claude Code all day, across several sessions at once, and we kept losing time to the same quiet failures: a session blocked with a simple clarifying question or cat README.md permission, and no way for us to know once the window was behind some other workflow. We tried the obvious fixes - a terminal bell, a notification, a second monitor full of tabs - and most of them got missed during a Zoom call or coffee break… or just got in the way of whatever else we were in the middle of.

Our last two posts, SOCKS and TIBIA, were about grinding through the recurring infrastructure annoyances so you don’t have to. This one is different. CHaaS isn’t a software solution for broken Operator workflows - it’s a retail product we’re simply happy to put out in public, because at 315Concepts we use it every day and think it makes working with an agent better for everyone.

Meet the Head

The retail device is called a Head, and it’s a hard-working team player. During the day it monitors your agent operations and shows you the state of your agent sessions. Once you’re finished for the day, it settles in as a cozy multi-color accent lamp - so the thing that nagged you all afternoon at least gets to be pleasant to look at all evening. Retail Heads are available now in the 315Concepts store. Each one pairs with your user account through the service dashboard - where you can manage your Heads, generate API keys for your session webhooks, and keep track of your subscriptions. Need a second one for another desk, or another room? Just buy another Head and add a subscription to it - each Head is managed independently, including shared or exclusive webhook consumption via your API keys assigned to each digital twin in our system. Want to set up two completely separate workstations and feed the sessions from each into two separate Heads? Sure. Want to combine both session feeds so you can monitor all of your sessions across all of your Heads? You can do that, too.

Honest Limitations

We like to be upfront about the edges of what we build, so here’s what to know before you buy:

• It’s a closed, private system. The CHaaS project is a bespoke technology demonstration platform that works only with our own devices. We don’t offer downstream APIs, BYOD support, or unlocked firmware for this project - but we do offer development kits in our store if you’d like to build an Open Source device for your own projects.
• It’s a subscription service. We’re as much a fan of recurring subscription services on the modern internet as anyone else - but we have to keep the servers turned on. $5 a month or $50 a year is where we’ve settled for now, but we ship each Head with 3 months of subscription service included, for free. We’re also committed to fair pricing with minimal price increases over time.
• It’s built for Claude Code. That’s the whole deal - but if you’re not running Claude Code there are workarounds, and we are working to increase the supported integrations list.
• Use it reasonably. The CHaaS project is a convenience for keeping an eye on your sessions, not a safety system. Don’t rely on it where a missed signal could cause harm.
• It’s young. We’re constantly improving the service, the user site, and adding to the store - there are going to be some rough edges but we’ll always communicate with and support our customer base as honestly as possible.

Get One / What’s Next

CHaaS is live today - here’s the whole path:

1. Pick up a Head from the 315Concepts store
2. Sign in to the CHaaS dashboard and get your Head provisioned with just a few clicks
3. Grab an API key, attach it to your Head in the dashboard, and start sending Claude Code webhooks with it

That’s it - the next time an agent is waiting on you, you’ll know before you’ve even thought to check.

The project page is the best place to find our next updates, and there’s plenty more coming - this is the first product we’re launching for Everyone, and we’re excited to hear how it fits into your day. If there’s something you wish your Head could signal, a workflow it doesn’t yet cover, or a rough edge we missed, we want to hear about it!