Skip to content

Claude Code

Purpose

The primary CLI tool that runs every agent in the eco|monetize™ operating system. Not a "tool we use" — this IS the runtime that executes chief.staff, project.manager, and all 19 other agents. Per-agent cwd model anchors memory namespaces.

How we use it

  • Per-agent cwd model — each Active agent launches from /Users/rhartley/Claude/sessions/{agent.id}/ so memory stays isolated per agent
  • Parallel sessions — chief.staff + Jordan + future agents can run simultaneously in separate terminals
  • MCP integrations — Claude Code is the surface through which Monday.com, Airtable, Slack, Gmail, and all other MCP servers are called
  • Skills + hooks — pre-tool, post-tool, session-start, session-end, and stop hooks at /Claude/system/hooks/ enforce governance (Missions, validator independence, worker reporting)
  • Memory namespaces at /Users/rhartley/.claude/projects/{cwd-slug}/memory/ — scoped per cwd

Setup & credentials

Installed on Mac (and presumably iPad via Termius + remote). Authenticated with Claude API key stored in 1Password and Anthropic account session tokens.

Owner

chief.staff — as the meta-agent that runs everything on Claude Code. Every agent's kickoff package assumes Claude Code as the runtime.

  • [[claude-anthropic]] — the model provider
  • [[CLAUDE]] Section 14 (folder structure), Section 10A (hooks + Missions)
  • /Claude/sessions/ — per-agent cwd anchors
  • /Claude/system/hooks/ — enforcement hooks

Notes

  • Evaluating VS Code as desktop IDE (2026-04-14) — Rick is moving from Termius to VS Code on Mac for better integrated-terminal features (clickable file paths, markdown preview, split panes). iPad stays on Termius.
  • Every agent's memory is cwd-scoped — see feedback_obsidian_launch_links.md and user_rick_tooling.md in chief.staff memory for current tooling context