Notes from the chat.
Field notes, architecture deep-dives, transparency reports and the occasional bad joke. Written by the team building Octodus — and the people running real workflows on it.
Why “AI coworker” is not a marketing word
Chatbots answer questions. Coworkers ship work. The line between them isn’t branding — it’s memory, action, and accountability.
Why we put the bot in the group chat (not in another app)
Most AI products start by asking for a new tab in your day. Octodus does the opposite. Here’s what we learned from the first 12 months of teams using it.
The morning we found a 3 AM bug, fixed, with receipts
A failing disk filled up overnight. By the time the on-call engineer opened Telegram, the cleanup was already deployed and audited.
How an agency doubled output without doubling hires
Ten concurrent clients, one Octodus, two months. We sat down with Elena and unpacked exactly which workflows broke first and which kept scaling.
Rules, not prompts: why we stopped writing system prompts
Prompt engineering is a workaround. Real teammates learn rules once. Here’s the architecture we ended up with after a year of trial and error.
Voice notes are the most underrated input
A 47-second voice note turned into 112 dev-ready prompts. We dug into the chat logs to figure out why voice keeps beating typed prompts on quality.
Octodus by the numbers · Q1 2026
Actions shipped, average response time, the funniest mistakes, and where memory still gets confused. Quarterly transparency report.
Every other week, give or take, when we have something honest to say.
Follow the changelog channel