> If you can't generate a report, it may be because you don’t have Memory turned on.
Has anyone found success with memory and Claude Code? I found Opus's 4.8 memories largely lacking value. Memories are too verbose/specific/yet-generic for the value captured.
Instead, I've been holding "retros" with the agent immediately after a session, and _those_ responses have been typically fantastic. It has ideas for coding changes, spots unmentioned small bugs, suggests invariants, principles to adopt, lint rules, tooling tweaks, skill-file updates, follow up work, all kinds of stuff.
Hah, 2 minutes before my remark. I feel like if anyone has 2+ ergomech keyboards, they should really try something with a pointing device. It's clear they don't mind having an expensive hobby :D
For people who like small keyboards, why do you NOT have an integrated trackball/pointing device? E.g. I love my Charybdis, but I rarely see people advocating for a keyboard with a pointing device. Does a trackball disqualify it as "small"?
I heckin love his /grill-me skill. Terse, to the point, and delivers outsized results.
Gonna take a moment to share my own generic "retro" prompt, which has found many areas of improvement IME.
> Let's conclude with a retro. Did you run into any issues during this session that you think could be improved? Any failed tool calls, confusing docs/prompts, or tricky wording that took you effort to figure out, etc? Any final thoughts that you want to raise? Anything minor you didn't mention? Help make this codebase easier for the next agent to work in.
It's somewhat doc-focused since I'm currently working on fairly dense design docs... but you can easily customize it for your own needs.
This prompt reveals how absolutely _ass_ the Claude Code harness is (so many stupid tool call failures), but not much I can do about that.
Feature request; `git diff --color-moved` uses colors to display moved chunks of code. Scanning https://diffs.com/docs it isn't obvious that yall support that; please add it :)
* Unclear TOS, citing Matt Pocock who sells a course on Claude (and therefore his interests are aligned with Anthropic):
> I have never before experienced, from any developer tool, such a frustrating lack of clarity over the basic terms of usage. I personally asked, 3 weeks ago, and have received nothing but delays. The recent @bcherny announcement did absolutely nothing to clarify things.
* And finally refusing to help a user debug issues with Dropbox, repeatedly saying "I'm best suited for software engineering" and "this is a question for Dropbox support" (paraphrasing Claude).
In the 14 hours since that flagged post, the OP has changed _nothing_ in that repo to address the feedback people gave him, and instead decided to just resubmit his proj to HN.
I flagged it because it includes incidents that weren't related to "vibe coding", e.g. ones related to Tea/Vite, and Cursor using "outdated Chromium/Electron builds".