This evening I am on a walk at the kids’ soccer practice, writing this from my phone with the same agent…

This evening I am on a walk at the kids’ soccer practice, writing this from my phone with the same agent stack we've been building on. Not a laptop. Not an SSH session I left open. #fitbuilders

That is the point.

We now have a multi-access harness for our Resilience Operations Centre (ROC): same Cloud Agent, same dedicated worker, from the Cursor desktop app, iOS, and the web. Status syncs. You pick up the thread wherever you are — no surviving terminal session, no “I have to be at the machine,” and remote sessions that land on our self-hosted worker. Internal, sovereign infra and app stacks. Not a public sandbox we reshape the work around.

We migrated an existing ROC specialist onto that harness so the job did not get rewritten for a new UI. Then we stood up non-human identity so the worker can reach GitLab (code) and Infisical (secrets) as itself — terraform-managed machine identities, least privilege, no shared human login on the box.

The design goal is building, not adapting my workflow to suit a tool. The agent comes to the ROC. Tonight: soccer, a walk, and a worker still on the LAN while I am on the sideline.

Yes, written with the support of AI - how are you making the tools fit your workflows?