One thing which sort of worked decently was actually take the frames and put them into a grid and have the agent look at the image of all of the frames together. It did surprisingly well but missed a lot of subtle details that it couldn’t see.

Also tried various kinds of vision embeddings, heat map of motion etc, and blur etc to show motion. But none really worked as well so I ended up just describing it until it got it. Haven’t quite found the right solution yet.

Go tooling is kind of surprisingly minimal and takes more taming then should be required. Especially monorepo workspace support seems a bit like an afterthought.

Hope to see continued improvements because in agentic era go is a serious go to.

Rust is top tier but for most things, it’s not really needed for an agent, to spend longer tokens fixing memory ceremony.

But rust tooling is best in class overall I feel and hope google continues improvements for go.

For lower RTT you’ll need an instance and proxy close to upstream but a real browser will help with scraping detection.

But a Url62 as a url safe public id from the pk is simple and straightforward to use and comes with few risks of leak issues. Wish postgres had native base62 encoding for url62 now that it has uuidv7 native.

Check it out if you want to give your agent a real browser, no cdp. clawchrome.com

If an agent is controlling your own browser, it can get in the way of you being able to do work as well.

Additional security control, if you have control and audit trails regarding what the agent is doing, think things like not having access to the keys, cookies are unavailable through the api, certain sites blocked, especially for agents that run automated background tasks.

There's a ton of reasons really. Using stealth chromium forks can decrease security, potentially get you blocked from services/sites, and typically can be detected easily because Google is doing a lot more than just compiling Chromium to release Google Chrome now. That's why many of the stealth browsers out there are moving targets, and have tons of instances of being blocked.

I sure hope agents don’t swarm social media. But at the same time I think identity verification companies have a tougher problem, ai can produce real looking videos and documents. There’s probably no real way to verify someone purely through the internet at this point.

Makes it difficult to block by censors. Great video I saw here: https://youtu.be/pZiG8r-diTM?si=wy35elqMt1T6euq0

This also means wg is just doing one thing instead of a dozen it doesn’t “need” to.

Could you tell me more? https://discord.gg/HPpN42SKQ

It may be a fools errand but makes for an extremely interesting research project. http://climatesight.app if you’re interested in climate markets.

The issue is for many things playwright is really verbose, by better tailoring outputs and making them more fine grained you’ll get less context bloat and allow the llm to better work with the context. I’m making it open source.

http://github.com/gvkhna/vibescraper

I told Jared if bun had a sandbox i’m pretty sure everyone would use it.