PLUG YOUR CODING AGENT INTO HAIMAKER
Run one command and your coding agent talks straight to api.haimaker.ai. It writes the agent's own config file, then exits. Nothing of ours stays in the request path afterward.
ONE COMMAND
You don't install anything. npx fetches @haimaker/connect, asks which agent you want, writes its config, checks the connection, then exits. Your key stays in your own environment, and the CLI never sits between your agent and the API.
npx -y @haimaker/connectIt walks you through the rest. Pick your agent, pick a model, done.
WHY IT'S DIFFERENT
IT WRITES THE NATIVE CONFIG
The CLI edits each agent's own config file so the agent talks straight to Haimaker. It already knows the format every supported agent expects, so you don't have to look any of it up. After that, nothing of ours touches your traffic.
NO PROXY, NO MIDDLEMAN
It runs once and exits. There's no proxy sitting in the middle and nothing phoning home. Your requests go from your machine to api.haimaker.ai and back, the same as if you'd written the config by hand.
YOUR KEY STAYS YOURS
By default the config reads HAIMAKER_API_KEY from your environment instead of saving a key into a file. The setup is reversible, and the prompts let you choose a model if you don't want the default.
START IN ONE COMMAND
Grab a key, run npx -y @haimaker/connect, and your agent is on every model.