settings

Council Setup

Sets up the council plugin for a user. Detects or clones the repo, explains everything that will happen, asks for confirmation, then configures the shell.

Step 1: Detect Environment + Check for Repo

Detect shell and config file:

echo "SHELL=$SHELL"

Map shell to config:

• zsh → ~/.zshrc
• bash → ~/.bashrc (or ~/.bash_profile on macOS if .bashrc doesn't exist)
• fish → ~/.config/fish/config.fish
• Other → ~/.${shell}rc

Check if we're inside the council repo (or can find it nearby):

# Check current directory
if [ -f ".claude-plugin/plugin.json" ]; then
  PLUGIN_DIR="$(pwd)"
  echo "REPO_FOUND=true"
  echo "PLUGIN_DIR=$PLUGIN_DIR"
else
  # Check common locations
  for dir in \
    "$HOME/git/octant-council-builder" \
    "$HOME/octant-council-builder" \
    "$HOME/projects/octant-council-builder" \
    "$HOME/code/octant-council-builder" \
    "$HOME/src/octant-council-builder" \
    "$HOME/dev/octant-council-builder" \
    "../octant-council-builder"; do
    if [ -f "$dir/.claude-plugin/plugin.json" ]; then
      PLUGIN_DIR="$(cd "$dir" && pwd)"
      echo "REPO_FOUND=true"
      echo "PLUGIN_DIR=$PLUGIN_DIR"
      break
    fi
  done
  if [ -z "$PLUGIN_DIR" ]; then
    echo "REPO_FOUND=false"
  fi
fi

Store $REPO_FOUND and $PLUGIN_DIR.

Step 2: Explain Everything, Ask for Confirmation

Before doing anything, tell the user exactly what will happen and why. The preview content depends on whether the repo was found.

AskUserQuestion:
  question: "Here's what setup will do. Ready to proceed?"
  header: "Council Setup"
  options:
    - label: "Let's go"
      description: "Proceed with setup"
      preview: |
        HOW PLUGINS WORK
        Claude Code can load plugins from any directory via --plugin-dir.
        It reads .claude-plugin/plugin.json from that directory and registers
        all skills/*/SKILL.md files as slash commands under the plugin's name.

        This repo is a plugin called "council" — loading it gives you
        /council:evaluate, /council:setup, /council:add-agent, and more.

        [IF REPO NOT FOUND:]
        STEP 1: CLONE THE REPO
        The council repo wasn't found on your machine. We'll clone it from:
        https://github.com/golemfoundation/octant-council-builder.git
        You can pick where to put it (default: ~/git/octant-council-builder).

        STEP 2: CREATE A SHELL ALIAS
        Creates an alias so you can launch Claude Code with the council
        plugin loaded. Example: alias council='claude --plugin-dir /path/to/repo'

        The alias keeps things isolated — plain "claude" stays clean.
        The council only loads when you use the alias.

        STEP 3: ENABLE AGENT TEAMS
        The council's evaluate skill uses Claude Code's teams feature to run
        parallel agent waves. This requires an env var:
        export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1

        Both shell config changes are tagged with "# public-goods-council"
        so they can be cleanly removed or updated by re-running setup.

        WHY THIS IS USEFUL FOR DEVELOPMENT
        The alias points at your local clone. Edit agent .md files or skill
        files and changes take effect immediately — no reinstall, no rebuild.
        Run /reload-plugins inside a session to pick up skill changes without
        restarting.
    - label: "Cancel"
      description: "Exit without changes"