Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

here’s how to make game models with claude opus 5.5 + blender... opus writes python and builds every model in blender, part by part. the trick is treating every model as code, but there’s a smart way to set it up: - step 1: connect opus 5.5 to blender...

73,391 Aufrufe • vor 10 Tagen •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

This is f*cking insane, this GitHub repo + Opus 5.5 turns any Android phone into a hands-free agent An Android phone, reverse-engineered with Opus 5.5... 1 sentence out loud = the phone opens Telegram, finds the app and installs it by itself. No taps, no swipes, nobody touches the screen. here's the full guide step by step: step 1 → put the phone and a laptop on the same Wi-Fi step 2 → turn on wireless debugging on the phone: Settings → About phone → tap Build number 7 times → Developer options → Wireless debugging step 3 → paste the prompt below into Claude Code on Opus 5.5 with the GitHub repo and a screenshot of the phone's About screen step 4 → Opus reads the repo and finds the loophole: every Android phone takes orders over ADB on a home network. The same door developers use to test apps step 5 → it checks the phone first: model, Android version, installed apps, and saves a restore point so nothing breaks step 6 → it writes a tiny agent with exactly 3 tools: see the screen, tap, type. Nothing else step 7 → it plugs that agent into Claude Code as an MCP. Claude is the brain, the phone is the hands step 8 → press Allow on the phone once, the last tap ever needed. Then say "open Telegram and install ChatGPT" and watch it tap through by itself the result: you talk, the phone does it, hands stay in pockets... p.s: the repo works on 300+ Android models from 40 brands, no root needed Find GitHub repo + full prompt below Then read the full guide on reverse engineering with Opus 5.5 in the article.

NO1ennn

33,045 Aufrufe • vor 3 Tagen

Claude Code vs Blender is getting f*cking ridiculous One approach builds a jet engine by hand The other turns a written description into a programmable 3D scene with rotating turbines, mechanical components, realistic materials, and cinematic camera movement And the difference goes way beyond modeling speed Traditional Blender workflow: > MODEL individual mechanical components > POSITION and assemble the geometry > CONFIGURE materials, lighting, and cameras > ANIMATE every moving mechanism > REWORK the scene when specifications change Claude Code + Blender Python: > GENERATE geometry from parameters > ASSEMBLE components programmatically > CONTROL turbine rotation through variables > AUTOMATE lighting and camera movements > REBUILD variations by editing the script The interesting part isn't that AI magically replaces Blender It's that Claude Code can operate Blender through Python, turning repetitive manual work into a reproducible system Want to test the difference? Open Claude Code and ask: "Generate a Blender Python script for a detailed turbofan engine with separate compressor and turbine stages, parameterized blade counts, independent shaft rotation, metallic materials, and a cinematic camera orbit Keep the geometry modular and expose the main parameters so I can regenerate variations without remodeling everything" Blender remains the rendering engine Claude Code changes how you build and control the scene Bookmark this workflow before your next 3D project

Lummox

34,057 Aufrufe • vor 7 Tagen

THIS IS F*CKING BRILLIANT. Anthropic’s docs describe one of the smartest ways to run Opus three models work on one task and each does only the part it’s cheapest at. start Claude Code like this: claude -> model sonnet -> advisor opus you stop paying Opus prices for work that doesn’t need Opus > Sonnet runs the session and edits the code > Haiku 5.5 searches the repo and docs, at up to 40x less per token than Opus 5.5 > Opus waits as the advisor and reads the whole session, tool calls included Claude usually calls Opus at three points: > before it locks a plan > when the same error comes back > right before it says it’s done Sonnet drives. Haiku scouts. Opus signs off and if you go one step lower, most of an agent’s day is tiny choices like picking a file or a tool, or deciding whether to retry. Jev takes those first, so Sonnet and Opus only see the moments that are really open the whole setup Sonnet runs the main session Explore on Haiku 5.5 searches and pulls docs, read-only Opus on call as the advisor give Claude Code this setup and the prompt below ↓ “Set up my Claude Code exactly like this: Main model Sonnet, advisor Opus, saved as advisorModel in my settings. One read-only subagent named exactly Explore, on claude-haiku-5-5, to replace the built-in one. One line in CLAUDE.md: ask the advisor before locking a plan, after the same error twice, and before calling a task done, not more often. Check what could turn the advisor off (CLAUDE_CODE_DISABLE_ADVISOR_TOOL, DISABLE_TELEMETRY) and only report it. Show every change as a diff first. Don’t edit anything until I say go.” before you turn it on: every advisor call re-reads the whole transcript with no cache. on a 200k session that’s about $0.80 in input, against $0.04 for a normal request. keep it to a few calls the built-in Explore agent runs on your main model unless a subagent is named exactly Explore. any other name does nothing turning the advisor on or off keeps your prompt cache. switching models rebuilds it it needs the Anthropic API, and it stays off if telemetry is disabled bookmark it before your next long session

rvaniaaa

62,223 Aufrufe • vor 14 Tagen