Specivo 0.13.0 tracks what your AI coding agents cost. Usage is recorded per person, project and issue, from the whole company down to a single agent session, so the cost of a feature shows up next to the feature.

AI usage tracking

Every agent turn costs money, and the bill rarely says which work it paid for. Specivo now attributes that spend to the issue the agent was working on. The open-source ai-usage reporter collects usage from Claude Code, Codex, Gemini CLI and OpenCode, and you can also log usage by hand over the REST API or MCP. Each issue has an AI usage tab that totals what its work cost, sub-issues included.

The reporter sends only usage numbers to your own Specivo server. It never sends prompts, code or file contents. Spend reports group usage by person, tool, model and project, and export to CSV.

For the details, see the AI usage page.

CI and deployments on issues

The Development tab on an issue now lists CI runs, deployments, tags, releases and reviews, with a summary and a timeline. Agents get the same list from the MCP tool specivo_issue_development.

Other changes

  • Dashboard. Redesigned, with a needs-attention row, the agents working now, AI spend and agent time, and grouped activity.
  • Audit log. Every install keeps a full security audit log, with an admin viewer, an API and monthly retention.
  • Project-limited API keys. An API key can be limited to the projects you choose.
  • Links. Issues show what mentions them, wiki pages show what links to them, and bare URLs become links.
  • Similar issues. While you type a new subject, Specivo suggests similar issues, with Mark as duplicate.
  • Estimates. Issues take original and remaining estimates, in the API and over MCP.
  • Email. Notification emails are sent in each recipient's language, and @mentions send an email.

Fixes

  • The legacy MCP SSE transport no longer fails every call after a client reconnects its stream.
  • A back-channel deprovision no longer switches off the API keys of SSO-only administrators.

What to do when upgrading

  • Backup. Back up your database first. The migrations create the PostgreSQL extensions pg_trgm and btree_gist, so an external database must allow them.
  • Metadata check. Run python -m specivo.cli.admin metadata-check in the api container and fix what it lists.
  • Links. Run python -m specivo.cli.rebuild_links once in the api container to fill in the links of existing issues and comments.

How to get it

Pull the Docker image with docker pull specivo/specivo:0.13.0, or docker pull ghcr.io/specivo/specivo:0.13.0 where Docker Hub is unreachable. For servers without internet access, the GitHub Release includes an offline bundle. The source is at github.com/specivo/specivo. For installation and upgrade steps, see the user guide.

Claude Code, Codex, Gemini CLI, OpenCode, GitHub and GitLab are trademarks of their respective owners. Specivo is not affiliated with or endorsed by them.