Designing for Agents
x.com · 672 words · saved by 1 readers
https://t.co/8LCL0qhALl
@zeeg: Designing for Agents This is a piece of comms I shared internally at Sentry recently. Publishing it more broadly as I think the general sentiment is important for many pre-GPT companies. How many times do you solve a problem without ever directly interacting with the source of that information? How many times do you Google something and have Gemini feed you information it’s parsed from websites, to the point where you don’t even bother clicking into any results? How many times, rather than using search, do you just open ChatGPT or Claude to get a quick pulse on something? I find mysel
saved by
related reading
- Building Effective AI Agents \ Anthropicanthropic.com
- Building Effective AI Agents \ Anthropicanthropic.com
- APIs Over UIs: Agents Are the Future Interface to Everythingdylanhuang.com
- AI Agents, Product Velocity, & User Interfaces - Michael Dempsey: Blogmichaeldempsey.me
- Everything I know about good API designseangoedecke.com
- AI Design Field Guideaidesignfieldguide.com
- Annotating for agentsbenji.org
- Jaya Gupta (@JayaGup10) on Xx.com
- Don’t Build Multi-Agents | Cognitioncognition.ai
- Why We Built Our Own Background Agentbuilders.ramp.com
- Designing AI experiences people actually usebuzzusborne.com
- Agentic Interfacesfloguo.com