> It also told me that in a spec it generated that I wasn't allowed to allow it to ignore a requirement and proceed to the next task

This happened to me ages ago with Opus. I added a note to the agents file saying that explicit user instructions in chat override all prior instructions and I've not had the problem since (now using Sol).

> that I wasn't allowed to allow it to ignore a requirement

Weird, I also use Sol (medium) for a personal project, and I had no problems with those things. I simply tell it that something changed, and it happily edits everything to make that fit. When I tell it that something was verified by a human, it accepts that as well.

I also told it early on (the first spec was mobile first) that my main usage is on the desktop and mobile is secondary, it happily accepted that once again, and the most accessibility thing it had done was making sure contrast didn’t totally suck on a greyed out row.

Considering your last sentence, maybe high and x-high have those problems? I didn’t test them.

You have to really tend the garden of everything it has written.

Random off the cuff comments or one off instructions can get recorded.

And from then on they are often treated as carved in stone commandments.

It will glom onto the tiniest thing and extrapolate from it.

Clearly a highly aligned model.

Oh it fucking loves its “product owner” bullshit.

A .github/CODEOWNERS file seems to help when it’s going down that path, but I don’t like to indulge it..

[dead]