spantail/spantail v1.1.0 is out, alongside version 0.3.0 of the Claude plugin. The change at the center of both is where an agent's work is attributed — the workspace and project its sessions are recorded against.
Until now that was bound to the agent token: one token meant one destination. If you worked across several repositories from the same machine, splitting their work into different workspaces or projects was awkward — the binding lived on the credential, not on the code.
Now attribution lives with the repository. Run /spantail:link once inside a repo and it writes a .spantail link; from then on that repo’s sessions are recorded against the workspace and project you chose. The agent token carries no destination of its own — one token works across all your repositories, and each repo decides where its work lands. Run /spantail:doctor to see where every setting resolves from.
This is a breaking change on the server. Agent tokens no longer hold a default workspace or project, and ingest now requires an explicit workspace — a payload naming none is rejected rather than quietly landing somewhere. The upgrade includes the repository’s first destructive migration (0011), so back up before you run it. Plugin installs older than 0.3.0 keep working: their existing config resolves on the client and is sent explicitly. The release notes have the details.
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.