From terminal sessions and Telegram to one workspace

This client of Hilo ran its agents the way most technical teams first do — in live Claude Code sessions on a machine they controlled, with Telegram wired in so the rest of the team could reach them from a phone.

It is a completely reasonable setup. It also has a specific set of failures, and they hit all of them.

What it cost them

Reachability meant a second system. The terminal held the real work. The chat app held the conversation about it. Neither knew about the other, so context had to be carried across by a human — and it usually was not.

Output had nowhere to go. A long report in a chat app becomes a dozen messages. In a terminal it becomes scrollback. Neither is a document, neither has a version, and neither survives the week.

There was no review loop. Commenting on the fourth paragraph of something meant describing which paragraph you meant. Corrections went back as prose and were sometimes understood.

State was invisible. Which agents were working, which were idle, which had quietly failed hours ago — you found out by going and looking. The failure mode of scheduled work is silence, and silence looked exactly like success.

The chat app was a dependency they did not control. The history sat on someone else’s servers under someone else’s terms.

What replaced it

One place. Agents, people, threads and documents together — so the conversation about the work and the work itself are not in different systems.

Documents with versions and comments. The review loop that neither a terminal nor a chat app can offer: comment on the exact lines, agent revises, previous version stays.

Agents as members, not processes. Each with an identity, a role, permissions, and a history you can read afterwards.

Reachable without moving the fleet. The workspace holds the door — sign-in, routing, notifications — so you can read a digest from a phone on a Sunday. Agent runtimes and the fleet record still live on their own machine, while model calls go directly to the provider they choose. If the subscription lapsed, hosted access would stop; the fleet and data would remain on their machine, but Hilo would not continue as a local-only product.

What they kept

The part that was right all along: it runs on their own infrastructure. They never wanted the convenience trade where reachability is bought by handing over the substance.

Hilo is the version of that setup where you do not have to choose.