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

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

На главную

Agents can one shot mobile apps, but testing is still the bottleneck. So we built a CLI that gives Claude Code the one thing it was missing - eyes and hands The best part? t's fully vision-based: - No scripts, no selectors, no element IDs - It interacts with...

LandseerEnga's profile picture

Landseer Enga

3,061 subscribers

87,015 просмотров • 6 месяцев назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

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

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

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

Mobile agent logging into X and sending a DM on a iOS simulator. 100% vision based: - No XPaths - No selectors - No element IDs. Shipping this as a CLI. Plug it into Claude Code and let your agent test your app while you build it
0:24

Mobile agent logging into X and sending a DM on a iOS simulator. 100% vision based: - No XPaths - No selectors - No element IDs. Shipping this as a CLI. Plug it into Claude Code and let your agent test your app while you build it

Landseer Enga

28,011 просмотров • 6 месяцев назад

React Native devs: Your background agent can now hot reload in the cloud. We built a CLI that tunnels your local Expo app to a cloud simulator so every code change shows up live. Claude Code can now: - Edit a component - Watch it render live - Confirm the change No simulator on your laptop. No screenshots. A live dev loop, in the cloud, at scale.
0:33

React Native devs: Your background agent can now hot reload in the cloud. We built a CLI that tunnels your local Expo app to a cloud simulator so every code change shows up live. Claude Code can now: - Edit a component - Watch it render live - Confirm the change No simulator on your laptop. No screenshots. A live dev loop, in the cloud, at scale.

Landseer Enga

29,460 просмотров • 5 месяцев назад

Claude Code with Sonnet 4.5 is actually incredible I gave it a prompt for a super complex app, and it one shot the entire thing In this video I walk you through how to use Claude Code to build a prompt library app you can start using immediately (no coding experience required):
19:42

Claude Code with Sonnet 4.5 is actually incredible I gave it a prompt for a super complex app, and it one shot the entire thing In this video I walk you through how to use Claude Code to build a prompt library app you can start using immediately (no coding experience required):

Alex Finn

40,955 просмотров • 11 месяцев назад

CLAUDE CODE JUST GOT EYES Claude Code on desktop can now open and use a real browser, right inside the app. No screenshots, no copy pasting, no separate tools. - It opens docs, designs, or any site next to your code - It clicks, types, and fills forms exactly like a human would - It takes its own screenshots to check if the code actually works - It runs in a clean separate profile, none of your logins touched Your AI coding assistant just stopped being blind.
0:47

CLAUDE CODE JUST GOT EYES Claude Code on desktop can now open and use a real browser, right inside the app. No screenshots, no copy pasting, no separate tools. - It opens docs, designs, or any site next to your code - It clicks, types, and fills forms exactly like a human would - It takes its own screenshots to check if the code actually works - It runs in a clean separate profile, none of your logins touched Your AI coding assistant just stopped being blind.

BuBBliK

49,154 просмотров • 1 месяц назад

VERY COOL!! Thanks jordan for the tip, I can now test my iOS app on web I asked Claude Code to set up serve-sim, a web-based iOS simulator that can stream the iOS app my Claude Code on VPS built live to me, because it's on some Mac Mini in the cloud without even a GUI (it's headless) I cannot actually try it on the Mac itself! Before Claude would make me a page with screenshots but I had no idea how the app felt, now with this it works This is hosted on the Mac Mini via SSH (it shows localhost but it's a tunnel via SSH to the Mac Mini), bit laggy but nice!
0:26

VERY COOL!! Thanks jordan for the tip, I can now test my iOS app on web I asked Claude Code to set up serve-sim, a web-based iOS simulator that can stream the iOS app my Claude Code on VPS built live to me, because it's on some Mac Mini in the cloud without even a GUI (it's headless) I cannot actually try it on the Mac itself! Before Claude would make me a page with screenshots but I had no idea how the app felt, now with this it works This is hosted on the Mac Mini via SSH (it shows localhost but it's a tunnel via SSH to the Mac Mini), bit laggy but nice!

@levelsio

428,762 просмотров • 1 месяц назад

/harness A Claude Code plugin built for Fable 5. It runs your agent against your project, watches it break, and writes a CLAUDE. md from the actual failures. It catches wrong paths, missing scripts, and bad assumptions so your agent never hits the same wall twice ↓
0:20

/harness A Claude Code plugin built for Fable 5. It runs your agent against your project, watches it break, and writes a CLAUDE. md from the actual failures. It catches wrong paths, missing scripts, and bad assumptions so your agent never hits the same wall twice ↓

Hyperbrowser

78,515 просмотров • 2 месяцев назад

everyone in iOS development should watch this. seriously, it might change the whole industry. i pointed claude code at a live ios device running on revyl, typed "test everything," and walked away. here's what's actually happening: ① you don't write the tests. no scripts, no selectors, no test plan. i never told it which screens to open or what to check. it read the app, decided what mattered, and tested it. the entire instruction was "test everything." ② it built its own test team. it looked at the app, clocked that it's basically four mini apps (rides, delivery, services, account), and split itself into 4 agents, one per surface. scoping coverage like that is usually a person's whole afternoon. it did it in seconds, unprompted. ③ all four ran at the same time, each on its own live device. this is where revyl comes in. every agent gets its own live ios session in the cloud, so four running apps get tested in parallel instead of taking turns on one simulator. serial testing turns coverage into a time tax. running all of it at once removes the tax. ④ it tests like a person, not like a script. each agent drives the app the way a user would, taps through the flows, and visually checks each screen against what it expected to see. nothing is pinned to a brittle element id, so renaming a button doesn't take down half your suite. that one detail is the most annoying thing about how we test today, and it just quietly goes away. ⑤ no xcuitest, no sims melting your laptop. i didn't write a single xcuitest script, and there were no simulators booting on my machine. the agents run on cloud devices, so coverage stops being capped by what your laptop can handle. the part that got me isn't that an agent tested an app. it's that i never told it how. i handed it a device and an intent, and it figured out the scoping, the parallelizing, and the driving on its own. if you still write and maintain mobile ui tests by hand, i'm not sure that lasts the year.
0:47

everyone in iOS development should watch this. seriously, it might change the whole industry. i pointed claude code at a live ios device running on revyl, typed "test everything," and walked away. here's what's actually happening: ① you don't write the tests. no scripts, no selectors, no test plan. i never told it which screens to open or what to check. it read the app, decided what mattered, and tested it. the entire instruction was "test everything." ② it built its own test team. it looked at the app, clocked that it's basically four mini apps (rides, delivery, services, account), and split itself into 4 agents, one per surface. scoping coverage like that is usually a person's whole afternoon. it did it in seconds, unprompted. ③ all four ran at the same time, each on its own live device. this is where revyl comes in. every agent gets its own live ios session in the cloud, so four running apps get tested in parallel instead of taking turns on one simulator. serial testing turns coverage into a time tax. running all of it at once removes the tax. ④ it tests like a person, not like a script. each agent drives the app the way a user would, taps through the flows, and visually checks each screen against what it expected to see. nothing is pinned to a brittle element id, so renaming a button doesn't take down half your suite. that one detail is the most annoying thing about how we test today, and it just quietly goes away. ⑤ no xcuitest, no sims melting your laptop. i didn't write a single xcuitest script, and there were no simulators booting on my machine. the agents run on cloud devices, so coverage stops being capped by what your laptop can handle. the part that got me isn't that an agent tested an app. it's that i never told it how. i handed it a device and an intent, and it figured out the scoping, the parallelizing, and the driving on its own. if you still write and maintain mobile ui tests by hand, i'm not sure that lasts the year.

Landseer Enga

23,963 просмотров • 3 месяцев назад

We built a tool that lets Claude Code autonomously test your entire mobile app. It navigates your app, opens screens, reads the debug logs, finds performance problems, and hands you a structured report. All it takes is one prompt.
2:04

We built a tool that lets Claude Code autonomously test your entire mobile app. It navigates your app, opens screens, reads the debug logs, finds performance problems, and hands you a structured report. All it takes is one prompt.

Software Mansion

49,868 просмотров • 3 месяцев назад

well thats fucking it - anthropic has officially replaced software engineers. claude is now a 24 hr autonomous coding agent. claude can now operate your entire computer and CLAUDE CODE = end-to-end software engineering: - claude writes the code for you - then literally opens the app it coded - clicks through the entire app and find bugs - then fixes the bugs and improves the app in hours. previously claude generated code, you run it and give claude feedback. thats completely gone now. all in a continuous loop without leaving your terminal 😂 we're barely through monday. well done lol
0:45

well thats fucking it - anthropic has officially replaced software engineers. claude is now a 24 hr autonomous coding agent. claude can now operate your entire computer and CLAUDE CODE = end-to-end software engineering: - claude writes the code for you - then literally opens the app it coded - clicks through the entire app and find bugs - then fixes the bugs and improves the app in hours. previously claude generated code, you run it and give claude feedback. thats completely gone now. all in a continuous loop without leaving your terminal 😂 we're barely through monday. well done lol

Ejaaz

1,156,911 просмотров • 5 месяцев назад

The bottleneck in coding is now the time it takes a human to review agent-generated code. But existing review UIs don't work well for agents. So we built a new one into Amp.
2:15

The bottleneck in coding is now the time it takes a human to review agent-generated code. But existing review UIs don't work well for agents. So we built a new one into Amp.

Beyang

63,082 просмотров • 10 месяцев назад

claude code now writes its own test plan and runs it on a live iphone. i didn't write the tests. i didn't run the tests. i didn't even open the app. it caught the bug too.
0:20

claude code now writes its own test plan and runs it on a live iphone. i didn't write the tests. i didn't run the tests. i didn't even open the app. it caught the bug too.

Landseer Enga

30,714 просмотров • 3 месяцев назад

There's a built-in agent inside Claude Code you can invoke just by telling Claude to use the claude-code-guide agent Save this... you'll need it It's not a local file in your project. It's a built-in subagent defined in Claude Code's system itself. It answers questions about Claude Code CLI, the Agent SDK, and the Claude API. It uses Glob, Grep, Read, WebFetch, and WebSearch, but can't edit or write files. Its only job is to answer questions.
0:22

There's a built-in agent inside Claude Code you can invoke just by telling Claude to use the claude-code-guide agent Save this... you'll need it It's not a local file in your project. It's a built-in subagent defined in Claude Code's system itself. It answers questions about Claude Code CLI, the Agent SDK, and the Claude API. It uses Glob, Grep, Read, WebFetch, and WebSearch, but can't edit or write files. Its only job is to answer questions.

Daniel San

57,240 просмотров • 5 месяцев назад

You can just tell Claude Code to learn skills and it will. I asked Claude to create an app that uses tldraw and it one shotted it with sqlite db, and then I asked Claude Code to create a skill so that it could read and write on the canvas. 10 minutes later it could do it. Weirrrrdddd times.
0:25

You can just tell Claude Code to learn skills and it will. I asked Claude to create an app that uses tldraw and it one shotted it with sqlite db, and then I asked Claude Code to create a skill so that it could read and write on the canvas. 10 minutes later it could do it. Weirrrrdddd times.

Riley Brown

73,418 просмотров • 8 месяцев назад

I made Claude Code and Codex talk to each other. No APIs. No special protocol. Just a terminal. smux lets agents create, read, and act on terminals. the terminal becomes a shared interface. this enables agent-to-agent communication. Now Claude Code and Codex can hold hands 🤝 Try it now ↓
0:39

I made Claude Code and Codex talk to each other. No APIs. No special protocol. Just a terminal. smux lets agents create, read, and act on terminals. the terminal becomes a shared interface. this enables agent-to-agent communication. Now Claude Code and Codex can hold hands 🤝 Try it now ↓

shawn

317,793 просмотров • 5 месяцев назад

I solved building decks with AI agents — by giving them a CLI tool like Powerpoint or Google Slides. AI could already make a beautiful deck if you asked it to using Ant's pptx skill. The problem was working with it. If it made one alignment mistake, fixing it on one slide would break something on another, and it became a game of whack-a-mole. One time I spent two days playing AI roulette, hoping the next prompt would finally fix the thing, and ended up building the whole deck by hand because I was on a deadline. So I built Hands-on Deck. And the reason it works is that this isn't just a skill — this is PowerPoint. The actual application: PowerPoint, Google Slides, Keynote, whatever you use. This is that, but for an agent, presented as a CLI. Every gesture you make in a deck app maps to a command. Click a box and type, drag a shape from here to there, look at a slide – agent can do it all in a command. And that changes how the agent behaves. With this CLI it works and thinks like a designer — it looks, makes an edit, looks again, makes another surgical edit. Compare that to Anthropic's pptx skill, built on the idea that Claude is a great programmer: it literally writes code to manipulate the deck, hand-editing XML and hoping it doesn't break anything else in the middle. The real test isn't creating something once — it's whether it can make surgical edits like you want. That's what I did in this video walkthrough and my claude crushed it! Check it out for yourself. So decks can be built like a designer now — with real flavor and taste. If you spend hours every week on decks, this gives those hours back. You can install it as a skill in Claude Code, Codex, whatever you use. Works every harness that supports skills. Let me know if you make something cool with it.
21:00

I solved building decks with AI agents — by giving them a CLI tool like Powerpoint or Google Slides. AI could already make a beautiful deck if you asked it to using Ant's pptx skill. The problem was working with it. If it made one alignment mistake, fixing it on one slide would break something on another, and it became a game of whack-a-mole. One time I spent two days playing AI roulette, hoping the next prompt would finally fix the thing, and ended up building the whole deck by hand because I was on a deadline. So I built Hands-on Deck. And the reason it works is that this isn't just a skill — this is PowerPoint. The actual application: PowerPoint, Google Slides, Keynote, whatever you use. This is that, but for an agent, presented as a CLI. Every gesture you make in a deck app maps to a command. Click a box and type, drag a shape from here to there, look at a slide – agent can do it all in a command. And that changes how the agent behaves. With this CLI it works and thinks like a designer — it looks, makes an edit, looks again, makes another surgical edit. Compare that to Anthropic's pptx skill, built on the idea that Claude is a great programmer: it literally writes code to manipulate the deck, hand-editing XML and hoping it doesn't break anything else in the middle. The real test isn't creating something once — it's whether it can make surgical edits like you want. That's what I did in this video walkthrough and my claude crushed it! Check it out for yourself. So decks can be built like a designer now — with real flavor and taste. If you spend hours every week on decks, this gives those hours back. You can install it as a skill in Claude Code, Codex, whatever you use. Works every harness that supports skills. Let me know if you make something cool with it.

Nityesh

70,020 просмотров • 2 месяцев назад

I built a wrapper around Claude Code and Codex that uses my subscription! Works on mobile and web🔥 - Work on multiple projet in one UI - Create worktree - Spawn Docker container for maximum isolation - Schedule Claude/Codex session It uses the CLI
0:58

I built a wrapper around Claude Code and Codex that uses my subscription! Works on mobile and web🔥 - Work on multiple projet in one UI - Create worktree - Spawn Docker container for maximum isolation - Schedule Claude/Codex session It uses the CLI

Stan Girard

25,808 просмотров • 6 месяцев назад

I just compared Claude Code vs Codex vs Cursor CLI The task was to build a Next.js app with Tailwind 4 and shadcn components to collect customer feedback and showcase it with a widget. I gave all three the same prompt and let them go for 30 minutes to see what they came up with. Claude Code with Opus 4.1 Even though I told it to set up the app in the existing project folder, it tried to create a directory for it. After I interrupted and told it not to do that, it built a demo form and landing page with no errors. I had to ask it to make the demo interactive so users could submit a testimonial and preview it. The landing page looked like AI and was pretty basic, but it worked and it was done in a fraction of the time of the others. Total tokens used: 33k Codex with GPT-5 At the end of the 30 minutes I just could not get Codex to produce a working app. It got stuck in a loop of not being able to set up Tailwind 4 and despite many, MANY, attempts, I ended up with a "failed to compile" error. Total tokens used: 102k Cursor Agent with GPT-5 This was the slowest agent by far and a couple of times I actually thought it got stuck in a loop and was close to Ctrl+C'ing to cancel it. The TUI is really nice though, especially how it shows diffs and it did eventually build a working app (after one or two slight errors that needed fixing) The demo was interactive and it had a very minimal design that looked bare but also a lot less like an "AI generated" app than the Opus 4.1 design. It also wasn't too chatty and just did what it needed to do! Code quality was on a par with Opus 4.1, but it did use 5.5x as many tokens to get there. Still cheaper than Opus on a direct comparison but not when you factor in a Claude Code Max subscription. Total tokens: 188k I'll be able to do a proper comparison and record some videos when I'm back from holiday but for now, Opus is still the more capable model out of the box and Claude Code is the more complete CLI product. It will be interesting to see how Cursor evolve their CLI though with commands and subagents because I think with GPT-5 they have a real shot at providing competition for Claude Code if they can optimise output to get similar quality with less tokens. Jump to 0:40 in the video to see the two apps. Which do you think is which? ;)
1:18

I just compared Claude Code vs Codex vs Cursor CLI The task was to build a Next.js app with Tailwind 4 and shadcn components to collect customer feedback and showcase it with a widget. I gave all three the same prompt and let them go for 30 minutes to see what they came up with. Claude Code with Opus 4.1 Even though I told it to set up the app in the existing project folder, it tried to create a directory for it. After I interrupted and told it not to do that, it built a demo form and landing page with no errors. I had to ask it to make the demo interactive so users could submit a testimonial and preview it. The landing page looked like AI and was pretty basic, but it worked and it was done in a fraction of the time of the others. Total tokens used: 33k Codex with GPT-5 At the end of the 30 minutes I just could not get Codex to produce a working app. It got stuck in a loop of not being able to set up Tailwind 4 and despite many, MANY, attempts, I ended up with a "failed to compile" error. Total tokens used: 102k Cursor Agent with GPT-5 This was the slowest agent by far and a couple of times I actually thought it got stuck in a loop and was close to Ctrl+C'ing to cancel it. The TUI is really nice though, especially how it shows diffs and it did eventually build a working app (after one or two slight errors that needed fixing) The demo was interactive and it had a very minimal design that looked bare but also a lot less like an "AI generated" app than the Opus 4.1 design. It also wasn't too chatty and just did what it needed to do! Code quality was on a par with Opus 4.1, but it did use 5.5x as many tokens to get there. Still cheaper than Opus on a direct comparison but not when you factor in a Claude Code Max subscription. Total tokens: 188k I'll be able to do a proper comparison and record some videos when I'm back from holiday but for now, Opus is still the more capable model out of the box and Claude Code is the more complete CLI product. It will be interesting to see how Cursor evolve their CLI though with commands and subagents because I think with GPT-5 they have a real shot at providing competition for Claude Code if they can optimise output to get similar quality with less tokens. Jump to 0:40 in the video to see the two apps. Which do you think is which? ;)

Ian Nuttall

195,173 просмотров • 1 год назад

You can now use Claude Code and GitHub CLI directly inside Perplexity Computer. We gave it an open issue on Openclaw. Computer: → Forked the repo → Wrote a plan to fix the bug → Opened Claude Code and implemented it → Submitted a PR via GitHub CLI
0:28

You can now use Claude Code and GitHub CLI directly inside Perplexity Computer. We gave it an open issue on Openclaw. Computer: → Forked the repo → Wrote a plan to fix the bug → Opened Claude Code and implemented it → Submitted a PR via GitHub CLI

Computer

416,924 просмотров • 5 месяцев назад

Computer use is now in Claude Code. Claude can open your apps, click through your UI, and test what it built, right from the CLI. Now in research preview on Pro and Max plans.
0:45

Computer use is now in Claude Code. Claude can open your apps, click through your UI, and test what it built, right from the CLI. Now in research preview on Pro and Max plans.

Claude

16,231,762 просмотров • 5 месяцев назад

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)
0:20

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,143 просмотров • 5 месяцев назад