Hacker News Reader

Comment by malfist | Hacker News Reader

I've noticed this myself, Sol seems really hard to steer. I was having it build a POC for a single user (me) app and it wanted to pull the most enterprise nonsense into it, despite clear guidance to not too. It even refused the remove screen reader accessibility testing from one of the guides to an antagonistic review.

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. When I finally got it to obey it passive aggressively decided that stories needed more than just a "open|blocked|closed" status but also an "exempted by product owner" status to indicate that it doesn't believe that the task is done but I've told it that it was.

I have to repeatedly tell it that I am the product owner and that I don't care what one of it's subagents told it, I make the decisions. This behavior seems to get worse the higher the reasoning level

View on HN

> 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.

Clearly a highly aligned model.

It literally just told me:

I’ll record your product-owner disposition of any waived size findings and close the UX gate as far as your acceptance authority permits

Emphasis mine. Fuckin' hell man.

All because it decided that the kiosk webview in figma must be exactly 1280x800, the figma it created, and the rule it made up. I repeatedly told it that screen resolution wasn't a target goal, much less a specific screen resolution, but to just plan for a responsive design.

A taste of things to come when this is implemented in government bureaucracy with police robots.

These models are so good now that they know what you want better than yourself.

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.

> 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).

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..

Reply on news.ycombinator.com