DevToolsDocumentationOpen SourceProductivity

SettingRadar

Auto-generated searchable settings index and changelog for large open-source tools

Problem
Tools like cmux have 200+ settings, making it impossible for users to find what they need—or even know a setting exists. People resort to asking AI or forking the code just to add one toggle. Settings explosion is a growing problem as tools get bigger.
Solution
A settings index generator for open-source projects: parses config files, README, and source to produce a structured, searchable catalog with one-line descriptions and examples for each setting. Developers can publish it as a docs plugin or standalone site.
Users
Developers using complex CLI/editor/terminal tools; maintainers of large open-source projects.
MVP
GitHub Action to parse repo and extract settings; generate static JSON and search page; support keyword, fuzzy match, and category filter; embeddable iframe/component for existing docs.
Revenue
Free for open-source; hosted version at $10–$29/month per repo; or one-time CLI tool purchase at $49.
Why now
AI coding assistants accelerate project growth, settings multiply uncontrollably, and no one wants to maintain an index manually—user tolerance for poor docs is dropping.

Source discussions · 3

  1. Hacker NewsAsk HN: Why does cmux need 200 settings?2↑ 1
  2. Reddit[r/SaaS] What does your vibe coding setup look like in mid-2026?
  3. Reddit[r/SaaS] How a 21k-view rant got us our first beta cohort in 7 days
← Back to list