Ben Holmes

It needs these repositories, probably needs these tools.

Or if you're not a developer, you can kind of just say, I just need an environment.

And then we'll figure it out from there.

And the agent can self-update depending on what is needed.

Either way, you can kind of go back and forth with an agent to get it deployed.

And a lot of early success can just come from writing some skill files, making sure the agent has access to those, giving it some API keys if it needs to access external services like customer analytics.

That's a common one.

If you just need to embed access to BigQuery so that it can access all of your customer data and answer questions about it, you can have an agent set that up, guide you through the keys that you'll need in that environment, and then get an early prototype.

From there, you do need some amount of...

perhaps engineering work to make it sustainable, something that a whole team can use with authentication gateways and things like that.

But those kind of come as a step two after you have your V0 in place.

So I feel like the bar to a V0 is kind of on the floor.

As long as you know your domain and you know the requirements of whatever you're trying to build, you can definitely get these things spun up without the technical experience.

Yes.

Yeah, I actually have one coming up later today.

We've been scheduling these, yeah, on our YouTube.

Once a week right now, we're doing live walkthrough.

It's kind of like an intro to Warp and the Oz platform.

We bundle it all together.

And I try to roll in if there's any like new features or things relevant to