This Neovim plugin and system-wide daemon, agent-tally.nvim, addresses the challenge of understanding and managing AI agent costs and activity. It targets Neovim users and developers leveraging AI coding assistants, providing crucial visibility into token consumption and tool usage across projects, thereby eliminating guesswork around AI spend.

How It Works

The system comprises a Neovim plugin and a Go-based sidecar daemon (agent-tallyd). The daemon monitors file I/O and command execution by AI tools. It estimates token usage based on file size changes (I/O In/Out) and, for specific agents like Claude Code and Copilot, parses local log files to capture precise API-level token counts (API In/Out). This dual approach offers both estimated file-level activity and actual model usage metrics, presented in a dashboard. It can also inspect project-specific AI configurations like rules, memories, and skills.

Quick Start & Requirements

• Installation: Install the Neovim plugin via lazy.nvim, packer.nvim, or vim-plug. Build the agent-tallyd daemon using :AgentTallyBuild (recommended) or manually via make build (requires Go >= 1.21).
• Prerequisites: Neovim >= 0.10, Go >= 1.21.
• Links: No external links for docs or demos are provided; the README serves as the primary resource.

Highlighted Details

• Monitors AI agents including Claude Code, Cursor, GitHub Copilot, and OpenCode by default.
• Provides both estimated I/O token counts and actual API token counts (where available).
• Enables inspection of project configurations (Rules, Local Overrides, Memories, Skills, Installed Plugins) for supported agents.
• Features a dashboard accessible via :AgentTally and heatmap generation capabilities.

Maintenance & Community

No specific details regarding maintainers, community channels (like Discord/Slack), or project roadmap are present in the provided README.

Licensing & Compatibility

• License: MIT.
• Compatibility: The MIT license is permissive, generally allowing for commercial use and integration within closed-source projects.

Limitations & Caveats

I/O token counts are estimations based on file size and do not account for conversational context or prompts. API token tracking is currently limited to Claude Code and Copilot; Cursor and OpenCode primarily support I/O tracking and project configuration inspection. The daemon requires a separate build step.