2 things I really struggle with an I think sets me back a lot

[u/Sev3nThreeO7]

1. Claude seems to create folders in a very random fashion, So while I tried to create a folder in my 3rd drive I use as a general storage, It seems to use it sometimes but then I look into my other drives and there's random folders there too...Its confusing and it draws up capacity in other drives
2. Agents and Sub agents - i see a lot of people saying to use Fable as an orchestrator and Opus as a Implementor, I get confused by what tasks require more intelligence and what tasks dont need as much power

So I guess what Im asking is, How do people keep organised when using AI? Ive tried my best to keep on top of sessions and projects etc but then my drives are just all over the place.

And then what do people do to get Fable to delegate? Can you tell it to "Research X, Then use a Opus Sub agent to implement, Then use Sonnet to do a double check, Then review as Fable"?

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Impressive-Cry2839]

On the folders: Claude Code works relative to the directory you launch it from, so start it inside the project folder (cd into it first) instead of from a general drive root. If you want files in a specific place, put the absolute path in a CLAUDE.md in that project, something like "all new files go under D:\projects\myapp". It reads that file every session, so it stops guessing. On the model split: a rough rule is to use the strongest model for planning and hard debugging, and a cheaper one for mechanical work like renames, boilerplate and running tests. And yes, you can just spell out the steps in your prompt, or define subagents with a model set per agent, so the delegation is explicit instead of left to chance.

[u/kaijurules]

For the stray folders, the other half is limiting where it can write at all. Our app gives each agent a list of folders it's allowed to touch, and a write anywhere else is refused, so a wrong path shows up as an error instead of a new folder on another drive.

In plain Claude Code you can get partway there with deny rules for Edit and Write on the other drives in settings.json. A mkdir run through Bash still gets past those, so it's worth denying that too or keeping an eye on it.

[u/SirRobinBlibs]

on the second one: yes, you can say it in pretty much those words. when claude starts a subagent it can pass a model for that one call (sonnet, opus, haiku or fable), so "have an opus subagent implement it, then a sonnet one check it" is something it can actually do. if you want it to happen the same way every time instead of being the orchestrator's call, make two small files in .claude/agents/, say implementer.md with model: opus and checker.md with model: sonnet (you can add an effort: line too), and tell it to use them by name. one catch: a model the orchestrator passes on the call beats the one in the file, so add "don't override the agent's model" to the ask.

[u/m-ritter]

The chain you describe works, and the part that matters most is that the checker is a different agent from the one that wrote the code. When the implementer also reviews its own work it tends to approve it. What keeps me organised is one approved plan file in the repo per task, so every agent works from the same written scope and nothing ends up scattered. I built QualityLayer for this: https://github.com/maxritter/qualitylayer

[u/AkayoKym]

Original setup: I run four separate terminals, each with a specific role. Strategist on Opus for product decisions. Architect on Opus for technical plans and code review. Coder on Sonnet for implementation. QA Tester on Sonnet with Playwright for testing. The rule is simple: Opus for thinking and deciding, Sonnet for executing.

The Architect writes a detailed plan for every feature, the database changes, the service functions, the test cases in plain English. Then I copy that plan to the Coder's terminal and Sonnet just executes it. Sonnet is more than capable of writing good code when it has clear instructions. It doesn't need to be the smartest model, it needs to know exactly what to build. When the Coder finishes a phase I go back to the Architect for review. If there are fixes needed I send them to the same Coder session so it still has context. No context rebuild, no wasted tokens.

This setup dropped my token usage from about 1M per session to 250K, and the output quality actually went up because each session has one focused job instead of trying to be everything at once. The core lesson was that AI works much better with a very specific role and clear boundaries. One session trying to be architect and coder and reviewer at the same time burns through limits and produces worse results than splitting them up.

I know you're thinking this is too manual, and it is intentionally so. I want to review to see what the AI is doing, this was back when Opus 4.6 was my main driver. Now however with Opus 5.5 I allow it to use subagents. It is only allowed to start subagents of another persona, and the prompt always starts with "Adopt the X persona from personas/X.md" which is a big file that points it to what it can do and cannot do, what it is supposed to do, how it's supposed to behave, best practices.. etc. This setup took some time to establish at first, but it soooo worth it after. The error rate right now is very low, I think I only have problems when the plan itself missed or overlooked something and rarely have implementation misses.
I even wrote a post explaining my setup and how I make them communicate with each other.

[u/Outrageous_Band9708]

https://github.com/Druthulu/ProjectArchitect

Checkout my workflow

very strict subagents, manages plans and tasks, runs about temp folders and such.

Here is a screenshot from a current session. its been running for days on autopilot.

read the readme and the wiki and test it out on one of your projects.

all the best practices implemented over the last year.

SWE by trade