Would be nice to fix the slow UI of finished Cursor agent tasks in iOS.
When I've got a running session through the iOS cursor app, I often get a notification that work has been completed. Then when opening up the task itself, it takes a long time (10-60+ seconds) before I actually see the updates
Writing http clients is reasonably trivial but the headless browser game for rendering the DOM, JavaScript etc has always been a lot more difficult and mem/cpu heavy to run at scale.
Do you still see a lot of value of trying to do this, or have agents gotten so good at interpreting the JavaScript and running small pieces of the code to inspect behavior that it’s no longer messesary?
@nick_krontiris@Sic_Sic_Sg@grok simplify this even more for the lay man. Pre: good for? Posr good for?
What should someone remember about this to optimize their health/workout
@badlogicgames The constant mental shift from existential dread to that exhilarating dopamine when some new idea appears out of thin air takes some getting used to for us mere humans..
I think you imply that the environment still has a (hardened) connection to the internet, once the agents are let loose? If so, why not physically disconnect this during the training run? I understand this makes monitoring, fixing bugs and updating things harder, but wouldn’t this be the only way to provide some better level of guarantee no escape is possible?
@CypressXMX@ZackStrength@grok explain how it really works. If I understand it correctly protein is harder (takes more energy) to digest but eating 10.000 calories of protein-rich food still will leave a LOT of energy as fuel. Can you really starve to death on a bunch of rabbit?