A local-first usage tracker for coding agents.

Usage data for coding agents can feel private because it is close to the way you work. It can reflect when you are active, how long a project took, how often you lean on an agent, and whether a coding session was unusually intense. That does not need to become another cloud dashboard.

AgentPace is built as a local-first macOS utility. The product boundary is simple: show whether Claude Code and Codex-style usage is ahead of or behind pace, then get out of the way. It does not require an account. It does not provide a hosted analytics dashboard. It does not include telemetry, ads, or analytics.

What stays on your Mac

AgentPace stores usage snapshots and refresh errors locally on your Mac. The privacy policy documents the local paths and explains how history can be cleared from the app. The point is not to collect a long-term behavioral profile. The point is to make recent usage visible enough that you can understand pace during the active window.

For Codex, AgentPace reads usage through local Codex tooling. For Claude Code, AgentPace can use local credentials or an AgentPace-owned Keychain item depending on setup. Tokens are not stored in AgentPace settings or usage history. The implementation is designed around local utility behavior rather than server-side reporting.

No account, backend dashboard, telemetry, ads, or analytics

The privacy promise is intentionally concrete. AgentPace does not ask you to create an account to see your usage. It does not send your usage history to a Fe Studio dashboard. It does not include third-party analytics, advertising, tracking, or crash-reporting integrations.

That matters because the app is meant for developers who already have enough services watching their work. A usage tracker should not add another place where work patterns accumulate. AgentPace keeps the interface and the data model focused on the local machine.

Local-first also keeps the failure modes simpler. If a cloud dashboard is down, rate limited, or changed, the usage tracker becomes another dependency. AgentPace is meant to be a small Mac utility you can reason about: it reads the local usage sources it supports, stores recent history locally, and displays the pace signal in the menu bar.

License purchase is separate from usage tracking

AgentPace has a 7-day free trial and a $4.99 lifetime unlock. The purchase flow unlocks the app, but usage tracking itself is not a cloud reporting product. There is no account requirement to maintain a dashboard, no subscription analytics area, and no hosted usage archive.

That separation is part of the product philosophy. Paying for the app should not mean accepting another monitoring surface. It should mean buying a small tool that keeps a specific local signal visible.

Direct distribution trust notes

AgentPace is distributed directly by Fe Studio as a downloadable macOS disk image from the GitHub release. The product page links to the latest DMG, the privacy policy, and support email so the install path is clear. Direct distribution is used because AgentPace is a focused developer utility that needs to work outside the normal App Store flow.

If a release includes additional signing, notarization, or changelog details, those should be stated plainly alongside the download. The important rule is to avoid vague trust language. Developers need exact information: where the file comes from, what it does locally, how to get support, and how to remove it if they decide not to keep it.

The trust model should stay boring and inspectable. The product page should point to the current release, the privacy policy should describe local storage plainly, and support should be reachable without creating an account.