Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Okay, I got Claude Code to actually fly my plane now It controls the keys via Chrome by running it with `claude --chrome` There is some issue with the lift vs gravity formula though so it takes a lot of speed to take off, but it's really cool to...

143,316 görüntüleme • 8 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

Claude Code + computer use is f*cking cracked 🤯 Build a landing page → Claude opens Chrome, looks at it, spots every issue, and fixes it — without you describing a single thing. All inside Claude Code. Perfect for DTC brands and agencies who are still vibe-coding landing pages and advertorials in Claude Code, then manually opening them in Chrome, spotting 15 things wrong, and describing every visual issue back to Claude one at a time. If you're building pages in Claude Code and your workflow looks like this — build the page, open it in Chrome, spot broken spacing, go back to Claude, type "the CTA button is too low and the hero image is cut off," wait for the fix, open Chrome again, find 3 new issues, describe those too ... Claude Code + computer use eliminates the entire loop: → Claude writes the full landing page or advertorial → Opens Chrome and navigates to it → Spots layout issues, broken spacing, off-brand colors, missing elements → Fixes everything and re-checks until the page looks right → Tests your Shopify product pages by clicking through like a real customer → Walks through your checkout flow and flags friction before customers hit it → You only see the finished, visually verified result No describing what you see on screen. No "the CTA button needs more contrast" back-and-forth. No being the eyeballs for an AI that can't see. What you get: → Landing pages and advertorials Claude builds AND visually QAs before you ever look at them → Product pages Claude clicks through — testing layout, images, and CTAs like a real user → HTML dashboards Claude opens and verifies the charts actually render → Checkout flows Claude walks through step by step to catch friction → All of it happening in one session — build, test, fix, done One prompt. Claude builds it, checks it, and fixes it. You just review the finished page. I put together a full playbook with the exact setup, the prompts, and 5 DTC workflows that use Claude Code + computer use. Want it for free? > Like this post > Comment "CLAUDE" And I'll send it over (must be following so I can DM)

Mike Futia

19,249 görüntüleme • 6 ay önce

✨ A dream I had finally came true: I can now chat directly with my sites to build any feature or fix any bug just via Telegram I've been playing with OpenClaw for 3 weeks now and it's great but I was always too scared to run it on any production server And I was right a bit as Marc Köhlbrugge was able to hack it by social engineering and acting as if it was me, and with enough tries it believed him, and was able to modify the server, change SSH keys etc. of course I had it isolated properly on its own VPS and it didn't touch anything sensitive (as it should!) Marc then reported that bug to Peter Steinberger 🦞 who patched it fast But I wanted to try something more basic and simple, and I think maybe more secure: to just connect Claude Code on my server to Telegram which would be hard locked to only messages from me So I installed claude-code-telegram by Richard Atkinson on the server and run it as a system daemon and it works really well The cool thing is that I was already using Telegram for server errors like this: > Photo AI - ❌ Random credits giveaway failed (Attempt 30/30) with an exception: SQLSTATE[HY000]: General error: 5 database is locked So now I can just reply, "Ok fix this", and Claude Code on the server in production will try (and probably succeed) in fixing it In the video below I asked it to make show [🌳 Parks ] on the map by default on load, it did that, then I reloaded the page and it instantly worked One thing it still needs is sending actual messages while it's doing stuff which OpenClaw does really well, it's annoying to just wait while it says "Working..." but that's probably next

@levelsio

644,262 görüntüleme • 7 ay önce

yesterday i showed claude code using codex's computer use, today i got some more fucking fire for you claude can also drive codex's official chrome extension, and it controls chromium browsers beautifully all in the background, without the "allow" popup chrome devtools mcp throws at you every time a new agent connects it even handles more than one browser: each install of the extension gets its own instance id, so claude knows which is which i have helium as my main and chrome for work, and claude code now uses both first, install the chrome plugin in the codex app and add openai's chatgpt extension to your chromium browser (or all of them, if you have a few) then give this to your claude: "Set up Codex's Chrome extension for you on my Mac. I've installed the Chrome plugin in the Codex app and the extension. Use Codex's computer use MCP server as user MCP "codex-cu": keep it if it's already registered, otherwise copy the "cua_repl" entry from ~/.codex/plugins/cache/openai-bundled/unified-computer-use/ /.mcp.json. Its browser side rejects calls without Codex turn metadata, so put a small stdio proxy in front that adds _meta["x-codex-turn-metadata"] (session_id and turn_id as a JSON string) to every tools/call. Add a Stop hook that tells this session's proxy to call the hidden turn_ended tool and start a new turn_id, so your tabs get released without touching other sessions. Test it by opening a tab straight at a URL in each browser with cua.createBrowserTab(browserId, url). Browsers can all report as "Chrome", so if I have several, ask me which test tab showed up in which browser." got more than one browser and ok with it touching your claude.md? give it this too: "Write each browser's name and metadata.extensionInstanceId into my global CLAUDE.md, with a note to pick browsers by that id and open tabs straight at a URL."

🥔🥔🥔

67,982 görüntüleme • 3 gün önce