"I Got Tired of Rewriting 4 AI CLI Config Files. So I Put Setup Behind One Button"

DEV Community

and the dashboard exposes actions like:

await this.api('/codex/config/proxy', { method: 'POST' });
await this.api('/api/tools/install/codex', { method: 'POST' });

So instead of editing files manually, I can open the panel, click install if a tool is missing, then click configure.

I did not want a generic "tool manager."

I wanted a very specific workflow:

That is what the page does now.

For example, the Codex side boils down to these settings:

chatgpt_base_url = "http://localhost:8081/backend-api/"
openai_base_url = "http://localhost:8081"

Claude Code gets its localhost base URL, Gemini CLI gets patched for proxy mode, and OpenClaw gets its provider block written with the same target.

I already had setup docs.

The problem was not missing information. The problem was repetition.

Every time I switched machines, reset a config, or wanted to try another CLI, I was doing the same boring setup work again.

Once I moved that into the product, the project became easier to try and easier to keep using.

If you use one tool with one API key, this is probably unnecessary.

If you keep bouncing between Claude Code, Codex, Gemini CLI, or OpenClaw, the friction adds up fast. That is the use case this page fixes.

If you've built a similar setup layer for AI tooling, I'm curious what you automated first: install, auth, config, or routing.