One agent setup. Every coding CLI. Today you configure the same MCP server once per tool, in a different format each time, with your tokens sitting in plain JSON. With AgentStack the whole setup — config, skills, servers, instructions — lives in one repo you own, any machine gets it with one command, and every CLI speaks it: Claude Code, Codex, Cursor, Gemini CLI, OpenCode and eight more — served live where the tool speaks MCP, written as native files where it does not.

Try it in 60 seconds

curl -fsSL https://raw.githubusercontent.com/Tarekkharsa/agentstack/main/install.sh | sh
export PATH="$HOME/.local/bin:$PATH" # only if the installer printed "Add to PATH"
agentstack init --connect            # import what your CLIs already have, and connect them
# now restart your coding CLI — it reads its config at startup
agentstack status                    # is it ready — and if not, the one thing that fixes it
agentstack more why <server>         # which of your CLIs is served this, and from where

The installer verifies the download against the checksums published with the release. Plain init is a guided wizard and needs a terminal; init --yes is the scripted form. more is the extended toolbox, and every more command also runs at its bare name.

Two more worth knowing early: agentstack doctor tells you what is wrong and what fixes it, and agentstack more restore takes any write back.

Your second machine

Publish your setup into a library repo you own, commit it, and the next machine is one command: agentstack up --library <git-url> --write. Two things stay per machine by design: secret values, and the trust review — you read what the project declares, and say yes once. → Set up another machine

Where to go next

• Get started — the guided walkthrough, with real output at every step
• Documentation — concepts, how-tos, migration recipes, troubleshooting
• All commands — the complete inventory; agentstack more lists the toolbox in your terminal
• Releases · CHANGELOG — what shipped, and when
• Contributing — the fast loop, every CI gate, and the security invariants
• Support and conduct — SUPPORT.md · CODE_OF_CONDUCT.md · GOVERNANCE.md. Report vulnerabilities privately through SECURITY.md, never in a public issue.

Supported platforms: macOS and Linux. A Windows binary is published but is not exercised by CI — treat it as untested rather than supported.

MIT OR Apache-2.0.