|
|
|
|
|
by pugio
580 days ago
|
|
I love the idea - owning the browser definitely seems like the right approach. I tried it out on a workflow I've been manually piecing together and it gave me a bunch of "Error encountered, contact support" messages when doing things like clicking on a form input field, or even a button. The more complex "Instruction" block worked correctly instead (literally things like "click the "Sign In" button), but then I ran out of the 5 minutes of free run time when trying to go through the full flow. I expect this kind of thing will be fixed soon, as it grows. In terms of ultimate utility, what I really want is something which can export scripts that run entirely locally, but falling back to the more dynamic AI enhanced version when an error is encountered. I would want AutoTab to generate the workflow which I could then run on my own hardware in bulk. Anyway, great work! This is definitely the best implementation I've seen of that glimpsed future of capable AI web browsing agents. |
|
curious what you mean by generating the workflow that you run on your own hardware? Is this different than running Autotab locally?