Skip to main content

← Back to Journal

A new face for DeskRhythm, and a way to bring work home

I keep noticing little mascots around apps and AI tools: Grok bot, Dots, Muse. They make a piece of software feel a little more personal. I thought that might work for an app whose job is to gently interrupt my workday.

Meet Pulse

Pulse is the new desk companion in DeskRhythm 2.0. He is there when it is time to switch between sitting, standing, and moving. The point is still the same simple rhythm, but a reminder from a little character feels different from another system notification. Pulse now appears in the iPhone dashboard, onboarding, and the Live Activity, including the Dynamic Island.

Pulse, the new DeskRhythm desk companion

I made Pulse in Blender with help from ChatGPT Astra. My brief was that he should be a little like a golden retriever: clumsy and silly at times, but always happy to see me. I was already building the character for the app, so I made a short film too. Getting the movement and rendering to look right took more work than I expected. Astra had to work hard on the scenes, and my little Mac mini spent a lot of time rendering them.

The 2.0 release also comes with a refreshed deskrhythm.com, with Pulse on the iPhone pages as well as in the app.

What's new in Build Studio

Building Pulse exposed a gap in my own workflow. Build Studio is good at keeping a project on track: when I write a PRD, the architect, brand, UX, and other reviewers check the idea against the product's vision and guardrails. Later, QA checks that the implementation has not broken what was already there. But when I want to try a new visual idea, I often need room to prototype, react to what I see, and change direction quickly. I did that part for Pulse in the ChatGPT desktop app.

Once I liked the result, I wanted it to become the new baseline in Build Studio, with the code, UX and brand documentation, and the reason for the change all brought along. A merge alone would not do that. The new Reconcile workflow takes an external branch or worktree, asks me what I intended, imports it on a separate integration branch, checks it against the project documents, and puts it through the agent team's reviews. I decide what to do with each finding before it goes through the usual QA and merge steps. It also handles colliding backlog numbers instead of leaving that problem for later.

Reconcile runs alongside the ordinary workflow queue. I can leave a larger experiment open while Build Studio continues with smaller fixes. In the Pulse review, the agents found details I had missed while working more freely, including onboarding, accessibility, and the app's existing analytics behavior. That is the combination I was looking for: freedom to explore in Codex or Claude Code, followed by a deliberate way to bring the work home.

Other Build Studio changes this week are smaller but useful. A CI slowdown can be put on watch without accepting a new baseline. An agent's uncommitted fix is sent back before QA tries to verify the wrong version. Projects recover more reliably after a crash, stuck drafting sessions can be ended, and a background monitor no longer makes a working agent look idle. If you run Build Studio from source, these changes include a desktop reinstall for the runtime update, a hub rebuild for Reconcile, and later resource syncs and restarts. The changelog has the exact steps.

Elsewhere in the projects

Fazon is still in iPhone beta. A recent update lets you choose the time for a weekly check-in reminder, and the Settings screen now shows the current phase more clearly. I am still keen to hear how the food database works outside Sweden.

Launch Studio is growing a workflow for films made outside the app: importing and reviewing the files, keeping versions of media, and preparing a publication for approval. A YouTube publishing adapter and a publishing queue are now in place. This is still product development, but it connects naturally to making a film like the one for Pulse.

Run Studio now has an Operations Review screen for decisions that need me, and a local MCP service with owner controls. The phone-based way of checking that work remotely is still something I need to put through real use.

Pulse began as an experiment outside the usual process. This week, both the character and the path back into that process became real.