Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

this is crazy... the guy reverse-engineered his camera with Opus 5.5 into an AI object tracking device he built it on Opus 5.5 + OpenCV and open-sourced the whole workflow here's how it works step by step: step 1 → connect OpenCV to Claude Code with one command: claude...

24,547 görüntüleme • 5 gün önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

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

37,171 görüntüleme • 22 gün önce

Holy sh*t, this GitHub repo + Opus 5.5 turned my TV into Jarvis powered by Grok Bot I reverse-engineered my Android TV with Opus 5.5... 1 sentence out loud = Netflix opens and scrolls itself. No remote, no phone, no ads on the home screen. here's the full guide step by step: • step 1 → put your TV and your laptop on the same Wi-Fi • step 2 → turn on network debugging on the TV: Settings → About → tap Build 7 times → Developer options • step 3 → paste the prompt below into Claude Code on Opus 5.5 with the GitHub repo and a photo of your TV's About screen • step 4 → Opus reads the repo and finds the loophole: every Android TV takes orders over ADB on your home network. The same door the phone remote apps use • step 5 → it cleans the TV first: ads, tracking and brand bloat switched off, restore point saved, every app can come back • step 6 → it writes a tiny remote with exactly 3 tools: open Netflix, move, select. Nothing else • step 7 → it plugs that remote into Grok Bot as a plugin. Grok is the ears, the plugin is the hands • step 8 → press Allow on the TV once, the last time you touch the remote. Then say "Hey Grok, open Netflix" and watch it browse for you the result: you talk, the TV listens, and the home screen finally has zero ads... p.s: the repo covers 131 TV models from 46 brands Find gitHub repo + full prompt below Then read the full guide on reverse engineering with Opus 5.5 in the article.

Codez

44,588 görüntüleme • 22 gün önce

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 görüntüleme • 1 ay önce

everyone's sharing motion graphic videos that Opus 5.5 made, and it's genuinely insane everyone says they created it with "one prompt", but my one prompt video looked mid so i went through a bunch of these videos to see how they were actually made, and found the workflow that works here's how to generate pro level motion graphic videos w/ opus: 1. get reference videos to direct from -> pick 1-2 videos whose style you want and tell opus to match them. naming a style works way better than describing one without a reference, opus falls back to its default look: centered text, gradient background, everything fading in that's why so many of these videos look the same. a reference gives it the pacing, the type and the transitions to copy 2. install HyperFrames or Remotion so opus can build the video both let opus write every scene as code and render it straight to mp4. no video editor without one, opus can only describe a video or hand you a rough html page you have to screen record with it, every frame is exact, and when you ask for a change it edits one line and re-renders instead of starting over 3. install 21st for high quality components in the video real buttons, cards and UI components made by design engineers, instead of whatever opus invents on the spot without it, opus draws your product UI from scratch and it looks off. wrong spacing, placeholder boxes, fake-looking buttons anyone who's used good software can feel it in a second, and the whole video reads as cheap 4. steps 1-3 were context + setup. now dump all of it into opus your brand (logo, colors, fonts), screenshots of your real product, the reference video, and a quick braindump of how you see the video then ask for 3 storyboard variants without this, opus guesses your colors, your font and what your product even does. the video could be for any startup with it, it could only be yours. and 3 variants means you pick a direction instead of fixing the first idea it had 5. pick the storyboard you like ask for one still frame per scene before anything moves. fixing a storyboard is way cheaper than fixing a render without this step, you only find out scene 4 is wrong after the whole thing is animated, and every fix means re-rendering. a still frame takes seconds to change 6. let claude cook then give notes like a director: "slow every zoom to 0.7x", "hard cut here", "push in on the button" without notes, the first render is usually 80% there, and that last 20% is what makes it look pro. vague notes like "make it better" get random changes. camera words get exactly the change you want everyone has the same model. the context you give it is what makes it look pro let it cooookk

Rexan Wong

652,181 görüntüleme • 1 ay önce