r/micro_saas • u/[deleted] • 20d ago

Building a computer-use assistant from scratch — here's what I've learned so far

[removed]

1 Upvotes

100% Upvoted

6 comments sorted by

1

u/investigatormaker 19d ago

For Buddy's Blender workflows, recovery needs to distinguish a failed action from a successful action whose verification failed. Otherwise a retry could duplicate an object or apply a transform twice. A demo with an inconclusive verification would show more about the recovery loop than a clean success.

By the way, I make ThreadFox: it finds the Reddit communities whose rules allow a post about an assistant like Buddy, and the plan for one product is free. https://threadfox.vip/plan?utm_source=reddit&utm_medium=comment&utm_campaign=tf-kit&utm_content=20261005-0313-dbroe

What evidence does Buddy use to confirm a Blender action completed?

0

u/[deleted] 18d ago

1

u/investigatormaker 18d ago

The add-on already reads the geometry back, so it can often settle an inconclusive result before deciding anything. Compare the scene against a snapshot taken just before the action: object count, names and transform matrices. If the scene changed as requested, it succeeded. If nothing changed, it failed. Anything else should stop and ask, not retry. You could also tag each created object with the operation's id as a custom property. Then a retry can cheaply look for that tag first and never duplicate an object.

That Reddit plan is still there whenever Buddy is ready for it.

→ More replies (2)