[HN Gopher] How we made v0 an effective coding agent
___________________________________________________________________
How we made v0 an effective coding agent
Author : MaxLeiter
Score : 25 points
Date : 2026-01-08 01:08 UTC (2 days ago)
(HTM) web link (vercel.com)
(TXT) w3m dump (vercel.com)
| themafia wrote:
| > A simple example is substituting long strings the LLM often
| refers to. For example, when a user uploads an attachment, we
| give v0 a blob storage URL. That URL can be very long (hundreds
| of characters), which can cost 10s of tokens and impact
| performance.
|
| > Before we invoke the LLM, we replace the long URLs with shorter
| versions that get transformed into the proper URL after the LLM
| finishes its response.
|
| So, instead of fixing your blob URLs, you effectively run a regex
| to search and replace on the prompt before you feed it to the
| LLM? That does not seem like high quality engineering.
|
| > In addition to text injection, we worked with the AI SDK team
| to provide examples in the v0 agent's read-only filesystem. These
| are hand-curated directories with code samples designed for LLM
| consumption. When v0 decides to use the SDK, it can search these
| directories for relevant patterns such as image generation,
| routing, or integrating web search tools.
|
| Curated or created? If you "curated" them what is the copyright
| license on those examples? Are they just copied into the project?
|
| Remember when programming was about creating useful libraries of
| code? Now it's about sequestering them inside of an LLM and then
| charging insane amounts of money to convince a machine to
| sometimes copy them into your code for you.
|
| Just.. wow... what are we even doing? Prepare for a very fragile
| future.
| Aurornis wrote:
| > Curated or created? If you "curated" them what is the
| copyright license on those examples?
|
| Given that they're talking about _their own SDK that they
| created_ in this article, the examples are probably from their
| own docs and engineers.
|
| > Are they just copied into the project?
|
| No, v0 doesn't copy and paste snippets into projects. LLM
| coding tools don't work like that.
|
| Providing example code or patterns for LLMs to follow is a very
| effective technique. They don't copy and paste or clone the
| code. They're good at identifying patterns, especially when you
| give them hints. What they did is not new or novel, it's just a
| well-known and effective technique for accomplishing various
| things with LLMs. Providing _similar_ or generic examples goes
| a long way.
| aziaziazi wrote:
| > They don't copy and paste or clone the code
|
| That's not how I understand his post, instead "read-only
| filesystem" seems to reference the LLM working directory and
| not it's outpost directory. He's asking what's the licences
| of the code sample which is fair.
|
| It's forbidden for Toyota to use a process protected by BID
| even if they only sell the result of that process (the car)
| and not the process itself.
|
| I might have misunderstood the original article or themafia
| message though.
| Aurornis wrote:
| The article is about their AI SDK. So this isn't taking
| from someone else and using it as an example. They
| literally wrote the SDK, the docs for it, and the examples.
| MaxLeiter wrote:
| v0 actually can directly copy files out of its examples and
| then apply edits. This saves it from having to write out the
| long examples verbatim. The rest of your comment is accurate
| roncesvalles wrote:
| Although your criticisms are totally contrived, if it makes you
| feel better, nobody considers this real programming. Things
| like v0 are just an evolution on the no-code front, which has
| some utility but will always remain a niche without possibility
| of serious scale.
| ramon156 wrote:
| Depends what you consider an "effective coding agent"
| llmslave3 wrote:
| Doesn't everyone use OpenCode or Claude Code these days? I
| haven't heard about V0 in a long time.
___________________________________________________________________
(page generated 2026-01-10 23:01 UTC)