Claude Coders: Ultracode updates. 1. Toggle Ultracode On/Off with... tab 2. Use Ultracode on any effort, not just xhigh I find Low to Medium is the sweet spot. Ultracode writes an orchestration script then generates a Claude swarm to execute it. It is amazing.show more

This is amazing. Do this: 1. Set model to... Opus 4.8 2. Reasoning effort to /ultracode Enables Claude Code's new Dynamic Workflows. Claude will autonomously detect complex tasks, write an orchestration script, and spawn an agent swarm.show more

Claude Code has a new wild feature... dynamic workflow.... How to try: set /model to opus 4.8 set /effort to "ultracode" 😂 use “workflow” in your prompt Claude will write an orchestration script, spawn subagents swarm, verify results, and report back.show more

Claude Code's new dynamic workflow is the real deal.... 🤖 Why it matters: It's not just a chain of prompts — it's an autonomous agent swarm. 1. Set model to Opus 4.8 + reasoning effort /ultracode 2. Claude detects complexity, writes orchestration script on the fly 3. Spawns a parallel fleet of coordinated subagents Operator takeaway: This is the first time I've seen an agent actually decompose and delegate autonomously without a rigid framework. Have you tried it yet? 🚀show more

Claude Code with: > Opus 4.8 > Ultracode >... Dynamic Workflows > Auto-mode ON ...is amazing. This is the way. I only use it with my Enterprise account. On work that will return material value to my company. I'd use it in my personal account but I don't want my family to be destitute after one prompt.show more

Sonnet 5 is here. It's worse than Opus 4.8... on nearly every benchmark... Does that mean it's useless? Absolutely not. Use it with Claude Code Dynamic Workflows! 1. /model set to Sonnet 5 2. /effort set to Ultracode 3. Any complex task will kick off a dynamic workflow This will only become more powerful when Fable is back. You'll use Fable 5 as the superintelligent advisor and Sonnet 5 as the fast and efficient implementer.show more

I put Opus 5.5 on Ultracode mode and asked... it to create the best motion design launch video it possibly could 12 hours of continuous running later, this is what it produced Thoughts?show more

Go to then double-click Clawd Then switch the effort... to ultracode and start coding on a Sunday What does double-clicking Clawd and his ball juggling add?... nothing, just to give your vibecoding a World Cup vibe 🙌show more

Codex Dynamic workflows are great. Try it out. 1.... Go to GitHub link below 2. Copy install instruction 3. Type /dynamic to invoke the skill Recreates the same orchestration logic as Claude Dynamic Workflows. > Generates orchestration script. > Spins up a swarm of subagents. > Enters /goal mode to complete the task. Free and open source.show more

Codex cooked for 12 hours 19 minutes last night... using a /goal 🎉 It added: - Stopwatch (count up) - Clock (with seconds) - Pomodoro - Tabata - Autocomplete Everything worked except the UI interactions around auto-complete (Codex GPT-5.5 is still not great at UI, but even Claude Opus 4.8 Ultracode struggled here). Overall, I'm really happy with the results. These are features that I've wanted for a while, and getting them close to release is awesome.show more

Nike would pay you $3000 for this. Took me... some 15 minutes to set up a Claude skill using Seedance 2.0 and Arcads. This is how it works: → I send a product image to Claude → Claude analyzes the product → Writes an ad script → Triggers arcads api with image and prompt → Arcads generates a product ad → Claude updates my Notion database RT + comment "AGENT" and I'll send you the skills .md, full setup, and a guide for free.show more

By tomorrow, everyone will be using this: Anthropic just... revealed the ultimate power move for Claude Code The concept: have Opus 5.5 design the master plan as a script, then deploy parallel swarms of the new Haiku 5.5 Massive scale operations with zero wasted Opus compute: the script manages the execution loop so Opus only reviews the final diff Simply boot up Claude Code with these parameters: claude --model opus --effort ultracode Here is the task distribution: -> Opus 5.5 translates your target into a fully runnable workflow script -> Haiku 5.5 scans all files concurrently at 340 tokens/sec to spot candidates -> Sonnet 5.5 applies each patch and validates findings within an isolated workspace -> You eliminate wasting Opus context on dozens of agent log transcripts Opus is involved at only three specific steps: -> writing the initial workflow script before execution -> analyzing verified results once the swarm wraps up -> giving final approval prior to committing any code to git Opus architects | Haiku audits | Sonnet delivers JEV engineering applies the exact same principle a level deeper: logic paths that require no deep reasoning (choosing files, picking tools, handling retries/stops) pass through JEV in milliseconds, leaving heavy models to focus only on complex branches The complete architecture: Opus 5.5 orchestrates the core session and generates workflow.js pipeline() fans out instances of Haiku 5.5 to inspect every file parallel() schema validators eliminate false alarms directly in V8 Sonnet 5.5 applies fixes within dedicated, isolated worktrees verify double-checks all code diffs prior to summary generation Opus 5.5 processes exclusively the results that survived validation JEV routes lightweight micro-decisions in milliseconds Feed this architecture and prompt directly into Claude Code Reconfigure my Claude Code setup following this tree: 1. Execute the primary session using Opus 5.5 with ultracode enabled 2. Assign read-only scanning phases to Haiku 5.5 across all workflows, while routing code modification steps to Sonnet 5.5, running each edit inside its own isolated copy 3. Update CLAUDE.md with a new rule: assign a separate verifier agent to every issue before reporting, and terminate fix loops after two iterations without progress 4. Route fast, deterministic branching (tool selection, path routing, retry logic) via JEV Present every modification as a diff upfront do not execute changes until approved Bookmark this to stay one step aheadshow more

Everyone is dunking on Sonnet 5 for losing to... Opus 4.8 on benchmarks. They're all making the same mistake, judging a teammate by a solo test. Sonnet 5 was never built to win alone. Set the model to Sonnet 5, effort to Ultracode, and any complex task auto-kicks a dynamic workflow where it plans, spawns agents, executes and checks its own work, fast and cheap. When Fable 5 comes back, the setup gets stupid good. Fable 5 decides what to build, Sonnet 5 actually builds it. You stop paying flagship prices to do grunt work.show more

🚨 THIS IS INSANE 🚨 Someone already shared Fable... 5.1 optimizations you can start to use "NOW". Here I show you how you can use them: 👇 1. Set effort to 'low' 2. Run '/claude-api cost-optimize' 3. Run 'claude-api prompt-audit' 4. Change effort mid-conversation w/o cache hit 5. Update Fable 5.1 API config w/ 'claude-api migrate' Bookmark this, you will need it 🔖show more

New feature in Claude Code 2.1.14 just dropped! You... can now search and install plugins from the marketplaces installed in your current Claude Code session. This is huge if you’re building plugins on top of Claude Code’s marketplace layer (Skills, Agents, Hooks, etc). How it works: - Run /plugin - The official Claude marketplace is installed by default - Use the search bar to find the plugin you want - Select one or multiple plugins with space, then press i to install - Go to the Installed tab to browse and enable them With the exponential growth of Skills and Agent-based components running in the CLI, improving plugin discoverability is a big win. Pretty sure more marketplace-related features are comingshow more

This is so cool! I had to try it... with Thrixel. Fully playable after 1 /goal prompt to Claude using Thrixel MCP. Then I had more fun ideas for follow-up prompts. Claude used Thrixel to create and iterate on the 3D assets, then assembled the scene and wired up the gameplay.show more

im honestly very impressed with Claude latest model 'opus... 5.5'. not that it was just 'cheaper to use' its way more intelligent as well. all I did here was simple I tell claude, hey make me multiple variations for this idea of a app im building and then I simply let it run for a couple hours and bam: (see vid) these are just 4 out of the 8 variations.. fully workable product btw, every tab is clickable, I've never gave it any direction. this really is the era of vibecoding. you can just.. build things.show more

Routing for long-horizon coding agents is a big deal.... Not Diamond just announced a model router that works natively with Claude Code. This is huge. It picks the model and reasoning effort before each turn in a session, runs through a privacy-preserving local proxy, and your requests still execute through your own gateway. In their benchmarks, it approximates Opus 4.8 Xhigh quality at 39 to 61 percent lower cost.show more

one of my favorite ways to use claude code... skills right now - combining remotion with claude-in-chrome for motion video creation. the workflow is addictive. the clip you see here was produced with minimal prompting effort let me know if you would like me to write a full break down of this process. you describe to claude code what you want, claude code writes the remotion components, opens the remotion studio (via browser) with claude-in-chrome, sees the actual rendered output, and iterates on it in real time. need the arrows pointing to the center of the bubbles instead of the edge? just say it. need the layout shifted to the center? say it. claude sees the preview, adjusts the code, re-renders. then when you're happy you tell claude code to render the final video. but skills are what make this possible. remotion knowledge + browser automation + the taste to iterate visually. no copy pasting screenshots back and forth. no "can you try moving it 10px to the right" over chat. it just looks and fixes. this is the kind of workflow that makes you realize how much further claude code can go beyond just writing code in a terminal. i didn't touch any code while working on the clip you see if you haven't tried combining skills together like this - start experimenting. the skills combos is where the magic is at.show more

Claude Code tip: if Opus 5.5 is already your... main model, Fable 5.1 has been sitting idle this whole time. wire it in with /advisor start it with /advisor fable Opus 5.5 writes every line. Fable 5.1 reads the whole session, every tool call, and says nothing until one of three moments: → a plan gets proposed: is this actually the right move, or just the first one? → the same error comes back twice: is the search stuck, or is this a dead end? → the task gets marked done: what got missed while it was moving fast? Opus 5.5 ships. Fable 5.1 catches what would've shipped broken. Jev engineering makes the same move one layer down: forks that don't need a real thinker, which file, which tool, retry or give up, get routed to Jev and answered in under half a second. the expensive model only ever sees the forks that genuinely split. the tree this runs on: > Opus 5.5, high effort, owns the main session > explorer, medium effort, reads the code > worker, medium effort, edits and runs tests > researcher, medium effort, pulls the docs > Fable 5.1 outside all of it, on call, never writing a line itself drop the tree and this prompt into Claude Code: "Rebuild my Claude Code setup around this tree: 1. Look in ~/.claude/agents and .claude/agents for subagents that already cover explorer, worker and researcher. Draft new ones only for roles that are missing. Set each to model: opus, effort: medium. If an existing subagent is pinned to a different model, list it, don't touch it. 2. Set the main session's effortLevel to high in ~/.claude/settings.json, and set advisorModel to fable. 3. Check for anything disabling the advisor: CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY, any variable blocking feature-flag fetches, and CLAUDE_CODE_EFFORT_LEVEL, which overrides subagent effort. Report what you find. Change nothing yet. 4. Add one line to ~/.claude/CLAUDE.md: consult the advisor before a large plan, when an error repeats, and before marking a long task done. Show every change as a diff first. Don't touch anything until I say go."show more