5 Comments
User's avatar
Henrik Werdelin's avatar

This might be what OpenAI aims for with their OpenAI manifest file, which is necessary for creating plugins on their platform. It allow OpenAi to interface with your site without having classic API.

Expand full comment
Henrik Werdelin's avatar

Seems a bit what OpenAi is preparing with their manifest.json that works for the plugins...

Expand full comment
Blanca's avatar

I’ve noticed something similar with travel planning lately,clients say they want flawless itineraries, but what they actually remember (and talk about) are the little quirks. Like the unexpected driver who made espresso in the van or the storm that rerouted their boat. Maybe that’s the same thing happening with AI-generated content and voice tech now. Once everything’s smooth and high-res, we start craving the texture again.

Also,your Gmail+Gemini newsletter summarizer hack sounds gold. I’ve been drowning in Substack digests and keep thinking there has to be a better way to sift. If you ever feel like sharing that Loom, I’m 100% in.

One question: what’s your take on when “agent UI” becomes standard UX for consumer apps? Not just API-to-API but agents truly shaping front-end experience? I'm seeing bits of it but curious how far you think we are from mainstream adoption.

Expand full comment
Carla's avatar

Waiting for my wife - app (-: . Now that is usefull technology.

Expand full comment
Gordon Mattey's avatar

Do websites need something like an agents.txt file (just as we have search “agents” reading robots.txt) to declare their interface and the available agent/data/services from that domain?

Expand full comment