What one day of launching a dev security tool taught me

Today I launched Agentmetry, an open-source tool I've been building alone: it records what AI coding agents like Claude Code, Cursor and Codex actually do on your machine (every command, file read and tool call) into a tamper-evident local log.

A few things I didn't expect, which might be useful to anyone building developer tools:

1. The first real feature request wasn't about security. A developer asked to see time and token usage broken down by task and tool, because they'd found by hand that one browser tool was burning most of their time and tokens. Same data, completely different value. I'd been pitching the wrong benefit to half my audience.

2. Saying what the tool can't do helped more than the features. It only sees agents whose hooks are installed, and it can't see cloud agents at all. Every time I said that up front, the conversation got more serious, not less.

3. Community moderation is a feature, not an obstacle. Two of my posts were sent back today for not following a community's rules, and both rewrites were better posts.

Questions for other builders here:

- When your users asked for something you didn't build it for, did you follow it or stay focused?

- How do you decide which benefit to lead with when the same product serves two very different audiences?

If you're curious about the tool itself, it's here: https://www.producthunt.com/products/agentmetry. But I'm mainly interested in how you've handled the questions above.