Loading video...

Video Failed to Load

Go Home

Wait what 🤯 Gradio's new Playground Search is just: "how do i use image component?" ↓ *gets perfect docs* ↓ *generates working code* ↓ *demo ready* we really used to read docs at one point?

13,919 views • 1 year ago •via X (Twitter)

5 Comments

Gradio's profile picture
Gradio1 year ago

Try it here: 🔥

Vila's profile picture
Vila1 year ago

awesome

Mcqueen42's profile picture
Mcqueen421 year ago

wait, link please

Gradio's profile picture
Gradio1 year ago

There you go : 🔥

Sandra Chaney's profile picture
Sandra Chaney1 year ago

@_akhaliq ok but can we talk about how this is literally coding for night owls? perfect docs + working code at 3am when the debugging demons usually come out to play? gradio gets us 🦉 who else is excited to try breaking this in the best way possible? 😈

Related Videos

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

42,501 views • 24 days ago