3 ms·

From the contents of the issue, this seems like a fairly clear default effort issue. Would love your input if there's something specific that you think is unadd

by bcherny 6mo ago

From the contents of the issue, this seems like a fairly clear default effort issue. Would love your input if there's something specific that you think is unaddressed.

DennisL123 6mo ago
Gotcha. It seemed though from the replies on the github ticket that at least some of the problem was unrelated to effort settings.
vecter 6mo ago
From this reply, it seems that it has nothing to do with `/effort`: https://github.com/anthropics/claude-code/issues/42796#issuecomment-4194114622 https://github.com/anthropics/claude-code/issues/42796#issue... I hope you take this seriously. I'm considering moving my company off of Claude Code immediately. Closing the GH issue without first engaging with the OP is just a slap in the face, especially given how much hard work they've done on your behalf.
- wonnage 6mo ago
  The OP “bug report” is a wall of AI slop generated from looking at its own chat transcripts
  - rib3ye 6mo ago
    It's only slop if it's wrong or irrelevant.
  - vecter 6mo ago
    Do you disagree with any of the data or conclusions?
    - wonnage 6mo ago
      Yes
      - vecter 6mo ago
        I'm open to hearing, please elaborate
    - adi_kurian 6mo ago
      I must admit, the fact that the writing was well formatted and structured was an instant turn off. I did find it insightful. I would have been more willing to read it if it was one lower case run on line with typos one would expect from a prepubescent child. I am both joking and being serious at the same time. What a world.
JamesSwift 6mo ago
I commented on the GH issue, but Ive had effort set to 'high' for however long its been available and had a marked decline since... checks notes... about 23 March according to slack messages I sent to the team to see if I was alone (I wasnt). EDIT: actually the first glaring issue I remember was on 20 March where it hallucinated a full sha from a short sha while updating my github actions version pinning. That follows a pattern of it making really egregious assumptions about things without first validating or checking. Ive also had it answer with hallucinated information instead of looking online first (to a higher degree than Ive been used to after using these models daily for the past ~6 months)
- dev_l1x_be 6mo ago
  It hallucinated a GUID for me instead of using the one in the RFC for webscokets. Fun part was that the beginning was the same. Then it hardcoded the unit tests to be green with the wrong GUID.
  - viktorianer 6mo ago
    [flagged]
    - JamesSwift 6mo ago
      Well Ive never had the issue before and have hit that / similar issues every few days over the past couple weeks.

by bcherny 6mo ago

From the contents of the issue, this seems like a fairly clear default effort issue. Would love your input if there's something specific that you think is unaddressed.

DennisL123 6mo ago

Gotcha. It seemed though from the replies on the github ticket that at least some of the problem was unrelated to effort settings.

vecter 6mo ago

From this reply, it seems that it has nothing to do with `/effort`: https://github.com/anthropics/claude-code/issues/42796#issuecomment-4194114622 https://github.com/anthropics/claude-code/issues/42796#issue... I hope you take this seriously. I'm considering moving my company off of Claude Code immediately. Closing the GH issue without first engaging with the OP is just a slap in the face, especially given how much hard work they've done on your behalf.

wonnage 6mo ago
The OP “bug report” is a wall of AI slop generated from looking at its own chat transcripts
- rib3ye 6mo ago
  It's only slop if it's wrong or irrelevant.
- vecter 6mo ago
  Do you disagree with any of the data or conclusions?
  - wonnage 6mo ago
    Yes
    - vecter 6mo ago
      I'm open to hearing, please elaborate
  - adi_kurian 6mo ago
    I must admit, the fact that the writing was well formatted and structured was an instant turn off. I did find it insightful. I would have been more willing to read it if it was one lower case run on line with typos one would expect from a prepubescent child. I am both joking and being serious at the same time. What a world.

JamesSwift 6mo ago

I commented on the GH issue, but Ive had effort set to 'high' for however long its been available and had a marked decline since... checks notes... about 23 March according to slack messages I sent to the team to see if I was alone (I wasnt). EDIT: actually the first glaring issue I remember was on 20 March where it hallucinated a full sha from a short sha while updating my github actions version pinning. That follows a pattern of it making really egregious assumptions about things without first validating or checking. Ive also had it answer with hallucinated information instead of looking online first (to a higher degree than Ive been used to after using these models daily for the past ~6 months)

dev_l1x_be 6mo ago
It hallucinated a GUID for me instead of using the one in the RFC for webscokets. Fun part was that the beginning was the same. Then it hardcoded the unit tests to be green with the wrong GUID.
- viktorianer 6mo ago
  [flagged]
  - JamesSwift 6mo ago
    Well Ive never had the issue before and have hit that / similar issues every few days over the past couple weeks.