spantail/spantail v1.2.0 is out, alongside version 0.5.0 of the Claude plugin. Where v1.1.0 moved attribution to the repository, this release turns to the agent session itself — linking it to the work you log, measuring its time honestly, and getting the hook that captures it out of your way.
When you log work from inside Claude Code — /spantail:log-work — the session you're in is now linked to that entry directly. Until now a live session only attached itself if its branch name happened to carry the issue number; the session id arrived too late to help. The plugin exports the session id at start and passes it when you log, so the work and the session that produced it are connected regardless of how the branch is named.
Session durations now reflect active time. A session’s span from start to end counted idle time too, so one left open over lunch looked like hours of work. The Agents list measures active duration instead — the sum of gaps under fifteen minutes between events — and sorts sessions by last activity, so the one you are working in stays at the top rather than sinking below sessions that started later.
And the Stop hook got out of the way. It used to post to your instance inline and could hold Claude Code for ten seconds or more on a slow network; now it writes the payload to disk, hands it to a detached worker, and returns in about twenty milliseconds. Recovery is unchanged — ingest is idempotent, so a worker that dies mid-flight is repaired on the next turn or at session end.
The upgrade carries two additive migrations (0012, 0013); neither drops nor rewrites data, so this is an ordinary deploy — no backup dance like v1.1.0’s. The release notes have the details, and the setup is documented at docs.spantail.com. If you want to follow along, star the repository — releases, issues and the day-to-day work all land there.