HackerTrans
TopNewTrendsCommentsPastAskShowJobs

danelliot

no profile record

comments

danelliot
·le mois dernier·discuss
[flagged]
danelliot
·il y a 2 mois·discuss
[flagged]
danelliot
·il y a 2 mois·discuss
[flagged]
danelliot
·il y a 2 mois·discuss
[dead]
danelliot
·il y a 2 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
Interesting that this came out of 500 agents in production. The hardest part I've seen with agent tool calls is handling partial failures gracefully — the tool returns something but it's incomplete or stale. Do you bake retry/fallback logic into the framework itself or leave that to individual tool implementations?
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]
danelliot
·il y a 3 mois·discuss
[dead]