|
|
|
|
|
|
by deepdarkforest
315 days ago
|
|
|
Congrats! I think the space is very interesting, I was a founder of a similar windows CUA infra/ RPA agents but pivoted. My thoughts: 1) The funny thing about determinism is how deterministic you should be when to break, its kind of a recursive problem. agents are inherently very tough to guardrail on an action space so big like in CUA. The guys from browser use realized it as well and built workflow-use. Or you could try RL or finetuning per task but is not viable(economically or tech wise) currently. 2) As you know, It's a very client facing/customized solution space You might find this interesting, it reflects my thoughts in the space as well. Tough to scale as a fresh startup unless you really niche down on some specific workflows. https://x.com/erikdunteman/status/1923140514549043413 (he is also building in the deterministic agent space now funnily enough)
3) It actually is annoyingly expensive with Claude if you break caching, which you have to at some point if you feed in every screenshot etc. You mentioned you use multiple models (i guess uitars/omniparser?), but in the comments you said claude? 4) Ultimately the big bet in the RPA space, as again you know, is that the TAM wont shrink a lot due to more and more SAP's, ERP's etc implementing API's. Of course the big money will always be in ancient apps that wont, but then again in that space, uipath and the others have a chokehold. (and their agentic tech is actually surprisingly good when i had a look 3 months ago) Good luck in any case! I feel like its one of those spaces that we are definitely still a touch too early, but its such a big market that there is plenty of space for a lot of people. |
|
|
1) You're totally right about this problem! We handle this issue with intelligent caching and heavy prompt/context engineering. These measures have been controlling agent behavior pretty well.
2) The key to scaling is building a tool that developers can learn and pick up themselves and that's what we're seeing here. By understanding how to use the tools we built to control agent behavior, developers have been able to leverage our docs to achieve desirable behaviors from our computer use agents when using Cyberdesk.
3) Surely you're correct about cost here as well, but with well defined workflows this will only happen a minority of the times the agent runs.
4) Great point! The beauty of what computer use made possible is it can solve problems previously unsolved by RPA altogether. The TAM will increase significantly when computer use agents start working really well. We've already seen this with our customers: they're able to build automations with Cyberdesk that they weren't able to using RPA. So while the TAM might bleed some ERPs and legacy apps that will implement APIs, I think it's going to grow at a much faster rate than it will shrink.