This message was deleted.
# proj-documentation
d
This message was deleted.
l
Some proposals: • Workflows • Custom Instructions
w
I feel strongly about "microagents", but more from a marketing than a technical perspective. Everyone wants to build agents, agents are the cool new thing. No one wants to write "instructions" or "prompt extensions". Calling them "microagents" gives developers a greater sense of creativity and ownership. It's also aspirational. There's room to make these more powerful over time, e.g. by letting people write pseudocode to drive their lifecycle. I'm happy to relent if the name is really causing pain, and we think another name would work better. Does anyone have examples of issues/messages with confused users?
l
(with 4 thumbs up)
There are more examples but I couldn’t dig them up through slack search. Overall I’m not actually very against the term microagents, but I do think it confuses people a bit originally because they think we’re doing delegation
w
Hmm interesting, yeah I could see that. (Actually I think that was how microagents originally worked 🫠 )
b
I won't change anything here. Seems like some discussions still need to be had.
👍 1
w
yeah but we should nail something down. Graham lets chat more about this in our next 1:1
👍 1
l
Sounds good!
f
Spitballing. Flow Optimization. 🥳 Optimizes how teams, individuals and Agents work together. Would be good to have something unique that doesn’t have namespace collision with terms in the market.