That’s interesting, so in that scenario, you fixed it for that customer.

How do you then ensure it’s fixed for customers in the future? Do you add instructions to agents to write scripts where possible?

▲

lmf4lol 3 hours ago | parent [-]

Yes. Or we make a skill of it and offer it via our skills marketplace. Depends really on what the fix was. Sometimes its really a one-off issue, and sometimes it makes sense to roll the new "insights" out to everyone.

▲

sksksk 3 hours ago | parent | next [-]

Thanks!

Another question I have, is from a product perspective, how do you decide how much of the internals you show to users (like token usage).

I always thought that seems like (from a non technical users POV), like a implementation detail; and quite hard to map to actual usage. For example, one request might use lots of tokens, and another will barely use any; but it can be difficult for a non technical user to undertand the difference.

	▲	lmf4lol 3 hours ago \| parent [-]
		intuition and a lot of talking with our customers :-)

▲

newswasboring 2 hours ago | parent | prev [-]

I am not a user of your service, but a "system diagnostics" skill is something I have been meaning to develop for my hermes instance. Things like checking if I have left any running servers, cleaning up consumed linux ISOs from jellyfin, check for any repeated tool failures etc. Also its fun to say "run system diagnostics".