Toolboard grew from a small browser utility into 83 tools

I built Toolboard because my browser workflow was fragmented across too many single-purpose extensions.

It started with a small set of utilities and eventually grew into 83 tools for inspection, capture, conversion, productivity, and optional AI-assisted workflows.

The biggest challenge was no longer adding features. It was keeping the product coherent:

• making 83 tools discoverable without turning the interface into a directory

• keeping interaction patterns consistent

• explaining why permissions such as tabs, clipboard, and capture access are needed

• separating optional AI features from the core browser utilities

The project uses a manifest-driven structure for registration, categories, search, favorites, and release checks.

Open source: https://github.com/ademisler/too...

I’d be interested in feedback from other makers: at what point does an all-in-one product become too broad, and what is the clearest way to communicate browser permissions without creating unnecessary concern?