Solo marketing agency, one workspace repo with ~15 client subfolders, each with its own CLAUDE.md (locked MCP account IDs, contacts, rules). Heavy MCP use (GA4, Google Ads, GSC). I would like to hear your opinion on:
- Always start in repo root, not the client subfolder? I used to cd into the client folder to “save tokens”. Turns out nested CLAUDE.mds load lazily anyway (on first file touch), while memory, settings and skills are keyed to the launch directory and got fragmented. So now: always root, plus a root rule “before any account-specific MCP call, read clients/<name>/CLAUDE.md first” to make sure the account fence loads even in MCP-only sessions. Is root-start the consensus? And does anyone enforce per-client data fencing deterministically (hooks, permission rules) instead of prompt rules?
- Big model only for thinking, Sonnet subagents for grunt work? How to implement best practice? Two agents in .claude/agents/ , both model: sonnet : an implementer for well-specified coding/document tasks and a data-runner that does all MCP pulls and returns condensed findings, so raw JSON never lands in main context. Main thread keeps architecture, specs and judgment. Rule of thumb: delegate what’s bulky, mechanical or output-noisy; small in-context edits stay on the main thread because subagents start blind. What are your setups? Do you agree/disagree with what I outlined here. For what reason? Thanks in advance (My Setup includes Windows 11, Claude Code CLI, Max plan.) submitted by /u/Joetunn
Originally posted by u/Joetunn on r/ClaudeCode
You must log in or # to comment.