Valet Blog

Awash in AI Artifacts

By Michael Ducker·

Some of my friends in product management have started alerting me to a new problem brought on by the success of agents in our workplaces: the enormous pile of one-off artifacts being generated and left behind. You spend an hour with Claude working through a problem, going back and forth in the console, and at the end you have a synthesis. It's well formatted, easy to read, and the obvious next move is to share it with your team. So you ask for a website. Multiply that by everyone in your org doing the same thing every week and you can see where this goes. Now I have hundreds of random links with work product on them.

The reason it's happening is wonderful! An artifact is a one-to-one mapping between a problem you care about and the software that solves it. I, among many others, have dreamt for decades of bespoke, dynamically generated software, presented perfectly to your taste and needs. Plenty of attempts have gotten close, as early as FileMaker and as recent as Dreamer, but they stay stuck in the idea that what you build is meant for reuse. Artifacts are bespoke in the way that old dream imagined, but reuse isn't really the point of them. They exist to communicate. An artifact from an agent has more in common with a Notion page or a wiki entry than with a piece of software, even when it's dynamic and wired into your systems.

We have been here before. When Word files got networked we needed somewhere to put them, and we got Dropbox and Box and Google Drive. Then wikis arrived, and SharePoint, Confluence and Notion turned shared pages into their own enterprise language. Every time a new format shows up, organizations end up awash in it before anyone works out where it should live. Artifacts are at that stage right now, and I think the sprawl is a real blocker to collaborating with AI.

Are you seeing this?

At my startup Valet, we're taking a stab at one solution: A secure place to share artifacts built by agents. Tell your agent to put it on Valet and get back a URL only your company can open. It works in Claude, Codex, ChatGPT, GrokBot, Town you name it. Discovery gets easier, accidental leaks get harder, and you have a shot at finding the thing someone already built.

I'd LOVE your feedback- copy the prompt at valet.dev into your agent to get started, and send me a note ducker@valet.dev to let me know how it went.

Prior posts