dex agrees with Michael Ramos on the idea of agent decision-making command centers

I think we are quickly evolving past needing surfaces to review intent/alignment and into needing better decision making "command centers." As decision making across many contexts, which agents effortlessly own, is becoming the bottleneck. This underscores the need for knowledgeable decision makers – and less so about a bottleneck of us not understanding; better models are able to derive aligned intent and produce tasteful+correct solutions without too much steering. This enables the experienced and things are just starting to get fun as we babysit less and do less of "wait bro wtf did you just do?" UI/UX: Similar to intent/alignment surfaces, and perhaps ironically bc better decision making surfaces need to provide adequate context per decision (that is easy for a human to consume/understand). e.g. similar things, but different: A tool feels behind when it focuses on a side bar of message thread activity and inline html rendering vs a tool that manages multiple contexts, surfaces relevant html artifacts per thread, and abstracts the exhaustive message threads away from you.

View original

I think we are quickly evolving past needing surfaces to review intent/alignment and into needing better decision making "command centers." As decision making across many contexts, which agents effortlessly own, is becoming the bottleneck. This underscores the need for knowledgeable decision makers – and less so about a bottleneck of us not understanding; better models are able to derive aligned intent and produce tasteful+correct solutions without too much steering. This enables the experienced and things are just starting to get fun as we babysit less and do less of "wait bro wtf did you just do?" UI/UX: Similar to intent/alignment surfaces, and perhaps ironically bc better decision making surfaces need to provide adequate context per decision (that is easy for a human to consume/understand). e.g. similar things, but different: A tool feels behind when it focuses on a side bar of message thread activity and inline html rendering vs a tool that manages multiple contexts, surfaces relevant html artifacts per thread, and abstracts the exhaustive message threads away from you.