what does "needs review" look like when 200 agent decisions flow past in an hour?
every interface paradigm shipped with a design language. the gui gave us windows and buttons. the web gave us links and pages.
there's still no equivalent primitive for supervision.
@charlesmendez why would they do that much due diligence just because they wanted to not accept you? just saying no would be easier.
somethings not adding up
weโre launching Motion, the frontier agent for tasteful motion design.
this launch video is made entirely with Motion. ๐๐ฝ
QT + comment "MOTION" to get 1,000 free credits.
tag @motion_so in any X post for a surprise.
now generally available at motion [dot] so.
been turning some customer ops workflows into pi agents.
the recurring pattern is that the agent needs context before it needs autonomy.
- who is this customer?
- what changed in usage?
- what happened in support?
- what did they say in slack/email?
- what facts do we know, and where did they come from?
@outlit/pi gives pi agents tools to query that customer context.
we started with a few examples:
usage decay, friction-to-churn, activation failure, and expansion readiness.
small step, but it feels like we're getting clsoer to the right abstraction.