gvkhna

The harness is making a big difference, lackluster performance with pi but somehow very good performance with opencode. There’s some rl there for sure, for a smaller model it’s likely going to perform much better in a harness it understands the best.

256gb ddr5, so this is going to cost north of 100k? Damn.

If it’s not zhipu then why is it returning errors that zhipu does for other models? Who else would return the exact same errors even if they took a lot of core infra like tokenizer from z?

That’s the whole point, just cost and compute limitations in your way (mostly).

Incidentally the fact that you could read and write from essentially thousands of harddrives at once for even a tiny file makes you wonder what novel use cases you could get out of that.

Nice @OP i put together something similar as well. Incidentally I found for motion design specifically llm is not able to infer specific animations as well as it just being described very plainly and accurately what is happening and the timing.

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 is my go to for simple coding projects now, if i have an agent work grind on it. It’s lightweight fast and resource minimal, while being quick to code.

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.

Use the real browser: clawchrome.com. You can evaluate code on the page, do network capture, screenshot. But it’s the real browser, no fork, no cdp.

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

UUIDv7 as pk is inherently the best option besides just a bigint where you really don’t need a public id.

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.

I agree technically but in most use cases the timestamp from uuidv7 is not a security leak. Especially where you’re already sharing that data in some way or another. A default guid is unnecessary if you use uuidv7 I think (in most situations).

Clawchrome uses a mitm proxy like this for network capture of a browser. I had my agent test using network capture with playwright, then again with simple HAR style reconstruction of the mitm proxy capture. It was just as effective.

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

That’s at the request of a user they aren’t operating autonomously.

There are many usecases for agents having access to a real browser and many usecases for humans where work wise it's useful or for agent success in completing the task. Including any specific situations where sites may block "controlled" browsers, as well as co-working.

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.

You can trace almost anything back to incentives, renewables are more profitable now in one way or another.