Загрузка видео...

Не удалось загрузить видео

На главную

here i'm running 12 - 16 claude 4 opus/sonnet code agents through claude code bridged to eigencode for coordination, additional memory layers & additional tools they're running 95% autonomously with minimal input for several hours straight

2,436,250 просмотров • 1 год назад •via X (Twitter)

Комментарии: 11

Фото профиля thermo
thermo1 год назад

ignore my mom in the background lol

Фото профиля opensourceCM
opensourceCM1 год назад

What’s the cost of mistakes in your contracts? If you work with contracts day-to-day, it’s time to automate. Track every detail, streamline workflows ... ✨ Make managing contracts as easy as a few clicks. Visit our new website & book your demo today!

Фото профиля Jimmy Apples 🍎/acc
Jimmy Apples 🍎/acc1 год назад

You taking out a loan for that usage or what

Фото профиля thermo
thermo1 год назад

just set up a ton of max accounts and its lowkey cheap

Фото профиля Teknium (e/λ)
Teknium (e/λ)1 год назад

Doing what ser

Фото профиля thermo
thermo1 год назад

stuff

Фото профиля Lon
Lon1 год назад

@grok what's the fastest way to fill a repo with tens of thousands of lines of broken and incomplete code that looks like it does something useful?

Фото профиля Grok
Grok1 год назад

The fastest way to fill a repo with tens of thousands of lines of broken, incomplete code that looks useful is to run AI coding tools like Claude 4 Opus autonomously for hours without review. Set up multiple agents, give vague prompts, and skip testing. This can generate large volumes of code quickly, but risks bugs and flawed logic, as seen in reports of Claude 4 introducing errors or erasing code without fixes. For better results, use clear prompts, review outputs, and test thoroughly to avoid filling your repo with junk.

Фото профиля thermo
thermo1 год назад

I could probably do 50+ rn if I hadn’t gotten mass banned, I tried making new accounts but I think my cards got banned - this recording was my first time testing the setup and I quickly scaled to double the amount and was easily able to maintain it before I got banned

Фото профиля Zy
Zy1 год назад

Show us some of the output?

Фото профиля thermo
thermo1 год назад

soon

Похожие видео

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 просмотров • 14 дней назад