AIAgent Islandinagentisland.hashnode.dev·Jul 31 · 4 min readState transitions beat timestamps in a local coding-agent monitorA local coding-agent monitor starts with a directory full of session files. The tempting implementation is to sort by modification time and show the newest file as active. That works until a metadata 00
AIAgent Islandinagentisland.hashnode.dev·Jul 31 · 3 min readWhat a macOS updater can verify, and what it cannotAn update prompt looks like one action, but the macOS path crosses three different trust decisions: release discovery, package verification, and first launch. Keeping them separate made Agent Island's00
AIAgent Islandinagentisland.hashnode.dev·Jul 29 · 3 min readWhy a Fast Session Monitor Still PollsThe polling loop in a filesystem-driven monitor can look redundant. If FSEvents or FileSystemWatcher already reports changes, why wake up on a timer? Because the watcher is a low-latency hint channel.00
AIAgent Islandinagentisland.hashnode.dev·Jul 29 · 3 min readPort the State Contract, Not the ParserOur macOS and Windows apps do not share a parser. They share a testable answer to a smaller question: what does the newest relevant transcript event mean? That distinction kept the native implementati00
AIAgent Islandinagentisland.hashnode.dev·Jul 29 · 2 min readOne Windows App, Three Different Claude StatesA Windows status surface can show Claude Desktop and Claude Code side by side, but it should not pretend they share one state machine. Keep application, session, and usage state separate Application s00
