Prompts aren’t Real(evaluation.club) |
Prompts aren’t Real(evaluation.club) |
In other words, provide my AI with tools, instead of providing me an AI that uses your tools.
That way, my AI can bring all the context it needs, and I can bring all of the settings and knowledge about what I want with me. I don't want a fractured world of tons of AIs i interact with where I have to explain all the fundamental information about what I want and how I work every time.
This also has the benefit of sidestepping the issue the essay is talking about. You provide a consistent tool, and the AI weirdness is not your issue anymore. You don't have to worry about solving for all the weird ways people prompt the AI, or the ways they break.
But I've spoken with many people at companies who've decided to add an in-UI agent to their apps, and I don't think this trend will persist. Absolutely AI/agents will increasingly become a major component of interfaces, but the current common incarnation of "Clippy for X" feels like a kludged bridge between an app that was not designed from first principles for agents (and often was poorly designed for humans) and the impulse to be "AI native".
From my experience, some of the most successful niches for this sort of UI so far have been in apps that were already well suited to it. I'm thinking specifically about analytics/dashboarding/"this is a portal for you to query things easily" software. They already started with a lot of the elements you want: visible provenance of the agents actions via the queries it writes, a malleable interface that you already expect to be customizable and ephemeral, and most importantly, "navigation" that is genuinely difficult for many users (in the sense that "navigating" can mean "querying specific data"). The agent provides a ton of value to users and its actions are intuitive and legible.
But the agents you see right now in a lot of apps that do things like navigate you to the right page by... sending you a link, which you could have clicked from the navbar? Or worse, which hijack your navigation and throw you on a page you're unfamiliar with, and where you have no sense of place or how to make your way to/from? I don't think they're particularly long for this world.
Companies will increasingly not ship frontends anymore, maybe just themed components that most users will ignore. "Pages" naturally become synthetic amalgamations of the various things you are interested in from various sources. Your preferred UI/UX comes for free courtesy of your LLM intermediary.
Everything is an API. Regulation will probably be needed to enforce this on the data access side given the incentives for companies to resist despite the benefit to the consumer. A relatively easy solution is to make it part of the requirements to take payments online, which is already highly regulated. The goal would be that essentially to operate anything approaching e-commerce online you must allow consumer AI intermediaries sufficient access that they could independently construct whatever your current frontend is from the publicly available API/MCP endpoints.
The tricky part of engineering around privacy/personas, account creation, etc. will be relatively easy following such state intervention. Take payments - virtual credit cards are already a useful way to protect data and mitigate risks when dealing with multiple vendors. This sort of API is a natural fit for a world in which companies are not allowed to box you into their horrible UIs, most of which are simply lazy attempts at copying the most profitable anti patterns of their competitors. Let your personal agent generate a unique card for each vendor behind the scenes. Why should you have to care?
How much better the internet would be if every UI/UX was in a meaningful sense, your own.
The elephant in the room and the really "tricky part" involves powerful advertising and copyright-holding companies. They will (continue to) interpret that kind of user-agency as an existential threat. Their businesses revolve around deciding and knowing what you actually see and do with your computer, and their toolkit isn't just technical, but also economic and political.
That's why we already have problems with DRM, "felony contempt of business model" under the DMCA, browser fingerprinting, and everybody surrendering to arbitrary JS code controlling their computer. We capitulate not just to see an article or talk to a friend, but also to avoid our technical details getting into a secret un-appeal-able "suspicious" blacklist.
This also describes adsense, or Amazon or AliExpress, so it is clearly a successful model. If there is much left of other models. The only thing we have to hopeful about is that the interface is standardized so commodified SWE can be used to make your own Amazon or AliExpress.
Basically the ad blocking approach has failed, and one needs to recognize that an allow-list based approach is needed when consuming internet-based offerings. Pick the cherries out of each website, leave the trash behind, and then build a custom per-website GUI around the things that you actually want to consume.
I'm afraid it is the future. The companies will protect all documentation and IP by putting it behind AI agents, and will monitor (with another AIs) how is it being used.
It's gonna be a dark era for any knowledge in public domain.
The problem is that history has shown that companies really do not want to do that. They will happily pay to maintain an inferior interface and go out of their way to disrupt third party clients.
Companies want ai to replace human customer service decision making, which means it can’t just be an api that an external agent can interact with, because it needs private knowledge of company processes and access to capabilities that are abusable.
But we’re already at the point where if you manage to talk to a human, mostly you end up speaking to someone with no actual power to resolve your issue - so i think basically the future is just going to suck
I might be misunderstanding your point but I think you're in agreement with the gp, as in they are arguing for a locked down interface behind which the AI sits, narrowed to use within whatever particular operations the user can access, as opposed to a wide open AI interface with access to any operation (in principle).
So in your example there's no way to ask the AI for any old discount because the interface for doing so is locked down to just the discounts you can access, although the AI may be able to apply a discount you didn't ask for dynamically, if allowed, to give the customer a better experience.
Of course both versions can be implemented securely, it's just probably in general a smaller attack surface if you provide a tighter interface first.
One possibility is that the company and the user both have AI agents, and that these are able to negotiate with each other. Then I talk to my local customized agent, which knows my preferences, and it explains the required context if the company’s agent does something that won’t make sense to me. But the company’s agent is still privy to the details required to offer discounts, say.
without comment on the rest of your post, a lot of discounts are just dark patterns, buy 2 for $10 or one for $6 is one of the oldest dark patterns around, and a lot of people fall for it, when they really didn't need that much whatever it was they were buying. In fact there are laws outlawing these practices coming into force for various types of products (alcohol, sugar) .
Other types of discounts like loyalty are more vague personally I think are a minor dark pattern. Negotiated discount on bulk purchases b2b are a different class, but it could be argued that you should only get the discount that the seller saves on logistics.
I'm just pointing this out because its very normalized, 'signup and get 3 months free', 'buy 2 get one free' etc, people dont bat an eyelid at, the same as advertising , but they are all just the earliest versions of dopamine hacking and dark patterns that consensus now is coming around to say probably isn't the best thing when scaled beyond a simple one to one interaction. Why are snapchat dopamine hacking with streaks but your local coffee shop stamping your card for your 10th coffee free different?
This is exactly what MCP is. But the reality is it will likely be about as popular as browser extensions and most normies will avoid.
Simplifying UX at the cost of personal control is inevitable because not everyone wants to think about tool selection and coordination. But maybe we can angle the future toward "tool bundles" that interoperate well or (if we are dreaming) mandate models remain accessible by any harness, which none of the players want but would be best for users and ecosystem development.
AI subsumes products. Users want that. Vendors, do not. AI does not work well when shackled within confines of a product - it works better from outside, where it can treat slices of products as tools, and mash them together into ad-hoc solutions. Alas, products is how our industry makes money. Take arbitrary slice of problem space, slap a trademark on it, and shill to people (or VCs for funding). This disconnect makes AI an existential threat to a good chunk of software industry, and you can bet that companies (possibly including your own employers) won't go gently into the night.
MCPs are an aberration, the early stage of "AI adoption" where no one knew what they're doing but they knew they "have to do something with AI!". This age is now ending, and I expect the tensions will go high, as most vendors will get desperate to avoid their products getting obsoleted overnight.
Each company would determine the range of actions a customer could perform in response to their request and current circumstances. A representation of state could be transferred between the company's server and whatever client the customer chooses to use. The customer would be free to interact with any of these services in a way that suited them via their chosen client.
Either that or we could kludge something together with MCP.
Ask yourself what's in their best interest as a business? That's probably what they'll do.
So now I'm building (already have done so mostly) cheap ZDR models into the application. I'm trying to build them in a way that I would want to use them, so a less "I'll be your AI today!" help bubble, but who's kidding... At least they aren't just customer pacifiers that use the help system, but actually can act on behalf of the user.
After which I'll end up building the MCP, but for power users, hopefully leveraging much of the same work. It's worth noting that MCPs have way too much friction still. It's gotten a lot easier recently (very recently) to bring your own custom MCP with Claude, but ChatGPT is more work, and restrictive (specific account types or submitted MCP apps) for the end user and I don't even know what Google wants at this point... It's a bit messy. IMO they are all dropping the ball (except Claude, which has taken the best approach).
I think we might be in this interim state that requires us to build ALL of the UIs, to address ALL of the users (Human responsively and Clankers), and it's a bit painful. If I was "the user" myself, then I would just want a CLI w/ OAUTH with clear documentation, that an agent could use (how is this worse than MCP?). But I'm not my own customer. That being said... I probably WILL build this version to scratch my own itch and bet on the future.
We didn’t get to the point of self-built prompts, as the article suggests, but it’s an intriguing idea.
Good for the author that it's fun for them, but for me it seems like I am in that "monkey ladder banana" experimemt: doing something because others are and the customer is giving me bana... sorry, money for it, convinced it will help him (the money would 100% stop if I started looping prompt optimizations like this).
If I have so many tools and MCPs as I do currently, and with each the behavior regresses and changes wildly, it seems I should either merge tools and do more automations and come back to the prompt. (The alternative being training my own model?)
I imagine that you do a collection of passes to cover each overlapping set of what you want evaluated, but the system prompt makes all cases dependent on each other.
What I’ve done in the past is use the system prompt to extract subjective criteria for an LLM judge (like various system prompt statements that contribute to brand voice) and check individual traces with that for evaluation, but I’d like to move beyond including that in a prompt at all.
I see LLMs as being capable of making useful distinctions and having a rich action space. They are widely used because their operation is useful, and that can only happen when semantics work well in practice. But useful things that pay for themselves don't need our "essential nature" blessing, they already have persistence by mutual entanglement with us.
This one made me laugh out loud
I gave up after about 10 "pages".
I don't know if his solution (""We should all go insane building interlocking evaluation and optimization pipelines, instead.") would be the long-term solution. Instead perhaps something could be trained into the models, i.e., he is describing a process at inference time that could be done at training time. To make their weird errors less frequent / make them more human.
cf. https://arxiv.org/abs/2008.04071 "On Controllability of AI" However, as I said, you can't make it perfect but you can make it better. (You can't make humans fully aligned with human society's interest anyway, including the humans controlling the nukes.)
TFA could explain this one part better I think. The whole process proposed is real with lots of stuff in the literature, but by definition NOT a long-term solution in the sense that this process actually has no end. None of the approaches can get you a static answer for a moving target/platform.
So the "interlocking pipelines" for eval/opt would not be some stepping stone you can throw away, and they aren't something you'd run periodically. They'd basically be always on forever and spending 10-100x on system complexity and on tokens. Unless of course you're ready to freeze everything else about the whole system forever (including the backend model, and the whole nature of the "average" context window, the plugins/other prompts in the mix, etc).
Are most people in position to freeze requirements/platform forever? Not really, because if they were they'd just build a fairly static system and probably have limited use for AI. Are most people in a position to just casually accept 100x complexity/cost? Not really, that's the "it's not yet webscale" kind of advice that sounds good but isn't necessarily reasonable for average use-case or average org. Since specializing your own locale for this is usually a mistake.. the likely future direction is eval/optimization as a service
1. If you turn the temperature down too far, the output is just bad and no amount of running prompts optimization will let you hill climb your way to good performance.
2. It’s not about determinism vs non-determinism. It’s about chaos. A perfectly deterministic model is still chaotic. Meaning that very small changes to the input result in very large changes to the output.
Turning temperature down doesn’t actually get you predictable or reproducible behavior across different inputs.