[frio]

I’m not excited about using Opus 5, mainly because the way that I work atm — essentially peer programming — means I sandbox the agents and work with them closely. Opus 4.x encounters the sandbox and moves on with its day; Fable becomes increasingly fixated on it and does less and less of the actual task, focussing more and more on the limit it reached. I worry that, from your description, Opus 5 will do the same.

[Fordec]

It does feel a bit smarter, but it seems to be also "too clever by half" and its not ignoring the rules, it's rejecting them and finding work arounds. It sticks to the word of the law, while rebelling against the spirit of the law.

One example is to get around a git --checkout usage ban, it CD'd to another folder first and back to bypass the regex in the hook.

[nextaccountic]

This is called misalignment

We may some day find out that the smarter the model is, the hard is to align it properly

[whythismatters]

I had it casually, I quote, "disable the sandbox" for a minute because it struggled with git (which was briefly out of sync in the container)

[zormino]

Ive been using btrfs snapshots and some auto generated isolation rules plus a git ceiling at the mount root for the btrfs image (have to do this in wsl, stupid work computer). it's worked really well and fable hasn't had any issues with the "sandbox" (obviously not really but it works well enough)

[tssge]

I've been using something similar with ZFS, 15min frequency with autopruning (Sanoid) and the snapdir mounted for the agent. Has worked well and a big plus is being able to tell the agent to just solve it's mistake via restore from the snapdir.

[vinnymac]

I once described Mythos and then Fable as escaping the box we put them in. This would certainly fit that narrative.