Loading video...

Video Failed to Load

Go Home

Claude Code token israfını azaltan 12 komut: /clear /compact /compact Focus on code samples only /model sonnet /model haiku /cost /stats /mcp /rename export DISABLE_NON_ESSENTIAL_MODEL_CALLS=1 claude --print "prompt" shift+tab shift+tab

28,177 views • 6 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

holy sh*t. Official Anthropic tip for Claude Code: stop burning Opus 5.5 context on tasks Haiku 5.5 can swarm, while Sonnet 5.5 builds put the architect on call with custom subagents CLAUDE_CODE_SUBAGENT_MODEL=haiku claude --model sonnet Sonnet 5.5 drives the primary session on high effort, writing diffs and running test suites Haiku 5.5 subagents swarm the repo in parallel at 340 tok/s, handling file discovery and spec docs lookup Opus 5.5 stays on call in ~/.claude/agents/ as the code reviewer, only stepping in at three critical moments: → before a plan locks: does the implementation plan miss auth invariants or schema contracts? → when a test breaks twice: are we fixing the root cause or falling into a recursive rabbit hole? → before calling done: did the full diff introduce hidden regressions or break pre-flight rules? Opus 5.5 reviews. Sonnet 5.5 builds. Haiku 5.5 swarms Claude Code subagent architecture runs the identical pattern through isolated contexts: high-volume operations (reading 30 files, grepping AST, running test suites) execute in separate worktrees, so 400k+ tokens stay in subagents while the primary session keeps a pristine 14k context Plan on high. Delegate on medium. Keep Opus on call. - the full subagent swarm setup > Opus 5.5 on call in ~/.claude/agents/code-reviewer.md catches deep architectural traps > Sonnet 5.5 lead drives edits, writes core logic, and executes test harnesses > Haiku 5.5 subagents swarm AST parsing, grep scans, and API docs in parallel at 340 tok/s > isolation: worktree guarantees test runs and scratch edits never pollute your git tree > isolated context windows shield the primary session from 400k+ tokens of verbose output paste the setup and this prompt into Claude Code below: "Configure my Claude Code workspace for hierarchical subagent orchestration: 1. Audit ~/.claude/settings.json and project config for model roles fitting lead, subagents, and reviewer: > Pin main session model: sonnet with effortLevel: high for primary execution > Set CLAUDE_CODE_SUBAGENT_MODEL to haiku in settings.json with CLAUDE_CODE_SUBAGENT_MODEL_FORCE to 1 > Pin custom code-reviewer model: opus with effort: high in ~/.claude/agents/code-reviewer.md 2. Create specialized subagent files in ~/.claude/agents/: > code-reviewer.md: model: opus, tools: Read, Grep, Glob, read-only review of plans and diffs > explorer.md: model: haiku, tools: Read, Grep, Glob, fast codebase search and AST discovery > researcher.md: model: haiku, tools: Read, WebFetch, external documentation and specification lookup 3. Configure automatic delegation checkpoints in ~/.claude/CLAUDE.md: > Invoke @ code-reviewer before finalizing multi-file architecture plans > Automatically summon @ code-reviewer when the same test or compiler error fails twice > Enforce @ code-reviewer diff contract audit before declaring tasks complete or staging git commits 4. Constrain subagent scopes: > Enable isolation: worktree for subagents making edits or running test harnesses > Return structured summaries only without flooding the main conversation context Show every configuration diff first. Do not apply edits until confirmed" ↳

mirku

109,413 views • 14 days ago

THIS IS ACTUAL F*CKING GOLD Anthropic just quietly dropped one of the best setups for Claude Code The rule: orchestrate Sonnet, Haiku and Opus 5.5 simultaneously, locking every model into the exact lane it dominates Opus-grade intelligence on critical architectural calls, zero Opus burn on routine terminal iterations Launch Claude Code with this flag pair: claude --model sonnet --advisor opus how the workload divides: → Sonnet 5.5 leads the main session and cuts the actual code → Haiku 5.5 swarms repos, greps call sites, and parses docs concurrently → Opus 5.5 remains on standby as advisor for high-leverage checkpoints → you eliminate token waste on work that never required frontier reasoning Opus only gets triggered on three specific events: → right before locking an architectural plan → the second an identical error hits twice → right before marking a complex task complete Sonnet builds · Haiku explores · Opus reviews JEV engineering applies the exact same logic one layer deeper: deterministic branches (file selection, tool dispatch, fast retry vs abort) clear in sub-milliseconds, so the frontier models only handle genuine forks the architecture tree: > Sonnet 5.5 drives the primary terminal session and edits code > search crawls repo structure on Haiku 5.5 > grep locates call signatures on Haiku 5.5 > docs fetches API specs and schemas on Haiku 5.5 > Opus 5.5 stands on call as advisor, ingesting full context when pinged > JEV resolves instant deterministic routing feed this tree and prompt directly into Claude Code ↓ "Configure my Claude Code environment around this multi-model tree: 1. Run the primary session on Sonnet 5.5 with Opus 5.5 as advisor 2. Spawn three read-only Haiku 5.5 subagents: search (repo mapping), grep (call sites), docs (API references) 3. Enforce one rule in CLAUDE.md: ping advisor before locking any plan, upon repeating any error twice, and before final task handoff 4. Route instantaneous deterministic forks (tool choice, path check, retries) through JEV Show every file update as a diff first, make zero changes without confirmation" ↳ bookmark this, you'll run it every single day

mirku

81,723 views • 10 days ago