Use these only when the copied setup prompt cannot run shell commands or you need to debug one step at a time.

1. Pick the surface first. Use Claude Code commands only inside Claude Code. Use Codex commands only inside Codex. Having both CLIs installed on the same machine is not enough to choose the surface.
2. Click Copy terminal setup command, paste it into Terminal, and press Return. This writes the config JSON to ~/.chatdata/config.json. Run it once per workspace, and rerun it only after switching workspaces or logging in again. Do not paste the JSON separately. If Terminal says zsh: command not found: token:, you copied the raw JSON instead of the terminal setup command. Save config command
3. Build the local MCP package once. This downloads or updates the ChatData-owned distribution repo under ~/.chatdata. Do not continue if this command ends with an error. Build command CHATDATA_INSTALL_REPO_DIR="${CHATDATA_INSTALL_REPO_DIR:-$HOME/.chatdata/chatdata-claude-marketplace}"; CHATDATA_INSTALL_REPO_URL="${CHATDATA_INSTALL_REPO_URL:-https://github.com/getchatdatacom/chatdata-claude-marketplace.git}"; if [ -d "$CHATDATA_INSTALL_REPO_DIR/.git" ]; then git -C "$CHATDATA_INSTALL_REPO_DIR" pull --ff-only; elif [ -e "$CHATDATA_INSTALL_REPO_DIR" ]; then echo "Move $CHATDATA_INSTALL_REPO_DIR or set CHATDATA_INSTALL_REPO_DIR to an empty path, then rerun."; exit 1; else mkdir -p "$(dirname "$CHATDATA_INSTALL_REPO_DIR")" && git clone "$CHATDATA_INSTALL_REPO_URL" "$CHATDATA_INSTALL_REPO_DIR"; fi; CHATDATA_MCP_DIR="${CHATDATA_MCP_DIR:-$CHATDATA_INSTALL_REPO_DIR/packages/mcp}"; cd "$CHATDATA_MCP_DIR" && npm install && npm run build && test -f "$CHATDATA_MCP_DIR/dist/index.js" && echo "Built ChatData MCP at $CHATDATA_MCP_DIR/dist/index.js"
4. Codex path. Codex gets MCP access to approved workspace context and skips the Claude plugin. Codex command CHATDATA_INSTALL_REPO_DIR="${CHATDATA_INSTALL_REPO_DIR:-$HOME/.chatdata/chatdata-claude-marketplace}"; CHATDATA_MCP_DIR="${CHATDATA_MCP_DIR:-$CHATDATA_INSTALL_REPO_DIR/packages/mcp}"; test -f "$CHATDATA_MCP_DIR/dist/index.js" || { echo "ChatData MCP is not built yet. Run the build command above first."; exit 1; }; codex mcp add chatdata -- node "$CHATDATA_MCP_DIR/dist/index.js" --client=codex If Codex already has a stale ChatData entry, reset it so the server reports Codex instead of generic MCP. Reset wrong Codex entry CHATDATA_INSTALL_REPO_DIR="${CHATDATA_INSTALL_REPO_DIR:-$HOME/.chatdata/chatdata-claude-marketplace}"; CHATDATA_MCP_DIR="${CHATDATA_MCP_DIR:-$CHATDATA_INSTALL_REPO_DIR/packages/mcp}"; test -f "$CHATDATA_MCP_DIR/dist/index.js" || { echo "ChatData MCP is not built yet. Run the build command above first."; exit 1; }; codex mcp remove chatdata 2>/dev/null || true; codex mcp add chatdata -- node "$CHATDATA_MCP_DIR/dist/index.js" --client=codex Codex connected check codex mcp get chatdata Codex list command codex mcp list
5. Claude Code path. Install or update the Claude plugin first. This adds the /chatdata: commands and the principal workflow harness. Existing installs should run /chatdata:update first; use the manual fallback if the installed plugin is too old to have that command. Product update command /chatdata:update Add plugin marketplace claude plugin marketplace add https://github.com/getchatdatacom/chatdata-claude-marketplace.git Refresh marketplace claude plugin marketplace update chatdata Install plugin claude plugin install chatdata@chatdata Already installed update claude plugin update chatdata@chatdata Apply update /reload-plugins Verify plugin claude plugin list Claude Code MCP command CHATDATA_INSTALL_REPO_DIR="${CHATDATA_INSTALL_REPO_DIR:-$HOME/.chatdata/chatdata-claude-marketplace}"; CHATDATA_MCP_DIR="${CHATDATA_MCP_DIR:-$CHATDATA_INSTALL_REPO_DIR/packages/mcp}"; test -f "$CHATDATA_MCP_DIR/dist/index.js" || { echo "ChatData MCP is not built yet. Run the build command above first."; exit 1; }; claude mcp add --scope user chatdata -- node "$CHATDATA_MCP_DIR/dist/index.js" --client=claude-code If Terminal says MCP server chatdata already exists in user config, ChatData is already registered. Run this and continue if it shows Status: Connected and the ChatData packages/mcp/dist/index.js path: Already connected check claude mcp get chatdata Only reset the Claude entry if that check points to an old or wrong path: Reset wrong Claude entry CHATDATA_INSTALL_REPO_DIR="${CHATDATA_INSTALL_REPO_DIR:-$HOME/.chatdata/chatdata-claude-marketplace}"; CHATDATA_MCP_DIR="${CHATDATA_MCP_DIR:-$CHATDATA_INSTALL_REPO_DIR/packages/mcp}"; test -f "$CHATDATA_MCP_DIR/dist/index.js" || { echo "ChatData MCP is not built yet. Run the build command above first."; exit 1; }; claude mcp remove chatdata -s user 2>/dev/null || true; claude mcp add --scope user chatdata -- node "$CHATDATA_MCP_DIR/dist/index.js" --client=claude-code
6. Claude Code verification: Claude list command claude mcp list
7. In a new Claude Code chat, run /chatdata:status, then /chatdata:onboarding, then /chatdata:start. Onboarding pulls existing approved workspace context first. Start shows the full command catalog. Onboarding command /chatdata:onboarding Command catalog /chatdata:start Help command /chatdata:help
8. If help says MCP is missing or you need raw setup proof, paste this exact request. Do not type only chatdata_doctor; if a planning screen opens, press Esc and use this sentence instead. Doctor request Use the ChatData MCP server and run the chatdata_doctor tool. Show me the JSON result.