darkamaul

I wonder what's the ceiling for these plans' prices. At some point, it becomes a non-negligible fraction of the salary for the employee, especially in non-US employment markets.

A timeline to help understand what happened :

- Aug 6: Off By 1, the security lab of 1Password publishes their blog post (current title: Why AI-generated vulnerability patches still require expert human review)

This article gets some specialized and mainstream press coverage

- September 15 : Trail of Bits publishes a rebuttal on their blog 1Password's AI patching benchmark is misleading

- September 22: Suha publishes the current blog post

The main idea in the rebuttal is that the headline number (26 percent only of the AI generated patches are flawless) is misleading because the experiments were not well designed.

Silly question - but how do you apply the cooldown to brew itself ?

I would think this is one of the most critical dependency that you would not want to get right away at let it rest for a couple of days

I _think_ (disclaimer: I have only read the documention of the two tools) they overlap quite a bit. The main idea is to get VM isolation for your agents env.

I use coop daily and found it super convenient for my use case (ie letting agents go on with no access to my other projects or personal files)

I would recommend anyone that has desire to provide stricter boundaries to agents to give it a try - while remembering that a motivated agent would probably be able to escape it :)

This is uncomfortably too close to the reality…

And as always with those satirical posts, I love the attention to the details (location: Nebraska for instance)

Models are becoming scaringly good at finding meaningful issues with little guidance, and I have the feeling that the value of complex harness around them is ever decreasing.

Why spend time and resources creating a complex orchestration workflow around a model limitation, where the next model might just behave better without all these constraints around it?

Thanks for sharing this one, that’s truly a gem that I had no idea existed

I believe the changes here make a lot of sense because, most of the time, your best bugs are not your first ones

Anyone can point an LLM to a code base and ask to find a vulnerability - and the initial set of findings is going to be rather lame.

Encouraging researchers to stick to a target and to report 7 lows before getting in will probably make their contributions more valuable.

I have quite the opposite view here. I have switched from Firefox to Orion on my iPhone a year ago (potentially more?) and had a great experience.

Sure they are sometimes some buggy UI controls (like the focus not working), but for the most part, the experience has been smooth.

Did you try to report the bugs when you had some? Maybe this could help everyone else using the browser.

What an interesting article. I did not assume I would read it until the end when I opened it, but the writing was super clear and easy to follow.

At the end, I admire the craft and patience to try to solve code diff rendering, and wish the folks at GitHub could put the same effort to improve their platform.

On a side note, I feel that we’re going to see more and more of this type of agentic usage, in well defined sub tasks, and the ability of a model to try many possibilities is a huge gift here.