Agent Setups

An agent setup is how Athenode packages the agents and commands that get exported into your AI coding environment — Claude Code, Codex, or Cursor. Instead of installing a fixed, one-size-fits-all bundle, you choose which setup your project uses, and you can build your own so the commands and agents your team sees match how you actually work.

Creating a new setup from scratch

Every project starts out on the default Athenode setup, but you're not limited to it. From your project's Agent Setups page in the web app, you can create a brand-new setup and build it up from nothing — adding whichever agents and commands you want it to contain, one at a time.

Cloning and customizing an existing setup

The faster starting point is usually to clone an existing setup — the default one, or any other setup already in your project — and adjust it from there rather than starting empty. Give the clone a new name and it's created as an independent copy: its description carries over from the source, and every agent and command the source contains is forked into the new setup, so editing the clone's agents or commands never changes the original setup or any other setup still using it.

Choosing which agents/commands a setup contains

Once a setup exists, you add or remove individual agents and commands to shape exactly what it contains — see the Commands reference for what each built-in command does. Changing a setup's contents (or creating or cloning a setup in the first place) requires editor or owner access on the project; see Permissions below.

Switching which setup is active

A project always has exactly one active setup, and switching to a different one takes effect the next time you run the CLI's init command from your codebase:

npx @athenode/cli init

Re-running init reinstalls the active setup's agents and commands into your local AI coding environment, so switching setups in the web app doesn't take effect locally until you run it again.

Permissions

• Editor or owner access on a project is required to create a setup, clone a setup into that project, or change which agents/commands a setup contains.
• Viewers can see a project's setups and what they contain, but can't create, clone, or modify them.
• The shared default setup can't be renamed or deleted by anyone — it can only be cloned into a new, independent setup.

What's next

• Getting started — set up Athenode and create your first specification
• Commands reference — the full set of commands for mind-mapping, decomposing, and implementing specifications