Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How I use every Claude Code feature

blog.sshh.io

Post reply on HN
Print view View original

171–180 of 193 posts

Re: How I use every Claude Code feature

#171

Post by shanecp »

dfabulich wrote: post #36

> If you’re not already using a CLI-based agent like Claude Code or Codex CLI, you probably should be. Are the CLI-based agents better (much better?) than the Cursor app? Why? I like how easy it is to get Cursor to focus a particular piece of code. I select the text and Cmd-L, saying "fix this part, it's broken like this ____." I haven't really tried a CLI agent; sending snippets of code by CLI sounds really annoying…

Direct use of Codex + GPT5 or Claude Code CLI gives a better result, compared to using the same models in Cursor. I've compared both. Cursor applies some of their augmentation, which reduces the output size, probably to save on tokens.

Re: How I use every Claude Code feature

#172

Post by nl »

dfabulich wrote: post #36

> If you’re not already using a CLI-based agent like Claude Code or Codex CLI, you probably should be. Are the CLI-based agents better (much better?) than the Cursor app? Why? I like how easy it is to get Cursor to focus a particular piece of code. I select the text and Cmd-L, saying "fix this part, it's broken like this ____." I haven't really tried a CLI agent; sending snippets of code by CLI sounds really annoying…

I use Claude and Codex in VS Code and they work really well.

> I select the text and Cmd-L, saying "fix this part, it's broken like this

This flow works well.

Re: How I use every Claude Code feature

#173

Post by prodigycorp »

ed_mercer wrote: post #70
prodigycorp wrote: post #67

Earlier quoted context omitted.

Nothing crazy about it, judging by how much CPU and memory it uses. Now, if it managed to grow features without bringing my M4 Mac with 64GB of ram to a crawl... that's be magic .

My m1 macbook pro works fine with +10 claude code sessions open at the same time (iTerm2). Are you using a terminal with a memory leak perhaps?

I'm using iterm2. Memory leak and cpu problems are very well documented in the github issues.

Re: How I use every Claude Code feature

#174

Post by stressback »

dfabulich wrote: post #36

> If you’re not already using a CLI-based agent like Claude Code or Codex CLI, you probably should be. Are the CLI-based agents better (much better?) than the Cursor app? Why? I like how easy it is to get Cursor to focus a particular piece of code. I select the text and Cmd-L, saying "fix this part, it's broken like this ____." I haven't really tried a CLI agent; sending snippets of code by CLI sounds really annoying…

Better? Hard to say. Different? Yes. Worth evaluating? Absolutely. Using it for 30 minutes will answer your question better than any reply here. I think you'll answer your own question quickly.

I've been coding seriously for about 15 years. No single tool has changed how I code more than claude code and I'm including non-"AI" tooling/services. This sounds like I'm shilling but I am not affiliated. It's played a large part in injecting my passion back into building stuff.

Re: How I use every Claude Code feature

#175

Post by SavioMak »

allyant wrote: post #72
simonw wrote: post #2

> Finally, we keep this file synced with an AGENTS.md file to maintain compatibility with other AI IDEs that our engineers might be using. I researched this the other day, the recommended (by Anthropic) way to do this is to have a CLAUDE.md with a single line in it: @AGENTS.md Then keep your actual content in the other file: https://docs.claude.com/en/docs/claude-code/claude-code-on-t...

This is one thing I think they need to get in-line with, and rename CLAUDE.md to AGENTS.md to follow convention.

I strongly disagree. It is extremely annoying when I cannot make different agents read a different prompt file when I needed to tell them different things. Cursor currently autoloads AGENTS.md without a way to disable it and it sucks.

Re: How I use every Claude Code feature

#176

Post by fourthark »

cannonpalms wrote: post #154
mritchie712 wrote: post #102

> /clear + /catchup (Simple Restart): My default reboot. I /clear the state, then run a custom /catchup command to make Claude read all changed files in my git branch. I've found myself doing similar workarounds. I'm guessing anthropic will just make the /compact command do this instead soon enough.

I've found the latency of /compact makes it unusable. Perhaps this is just the result of my waiting until I have 0% context remaining. Fun fact, a large chunk of context is reserved for compaction. When you are shown that you have "0% context remaining," it's actually like 30% remaining that's reserved for compaction. And yet, for some reason I feel like 50% of the time, compaction fails because it runs out of contex…

Weirdly, I’ve found that when that happens I can close Claude and then run `claude --continue` and now it has room to compact. Makes no sense.

But I have no idea what state it will be in after compact, so it’s better to ask it to write a complete and thorough report including what source files to read. Lot more work but better than going off the rails.

Re: How I use every Claude Code feature

#177

Post by quinnjh »

johnfn wrote: post #157

Does anyone else struggle with getting Claude to follow even the simplest commands in CLAUDE.md? I’ve completely give up on maintaining it because there’s a coin flip chance it disregards even the simplest instructions. For instance, (after becoming increasingly exasperated and whittling it down over and over), my CLAUDE file now has a single instruction, which says that any ai generated one-off script should be name…

Definitely experience this. After losing over 2 hours fiddling between a few sessions and still having no actual control I’ve settled on a handful of python and perl/regex scripts to make sure things are following my own conventions

Re: How I use every Claude Code feature

#180

Post by spicyusername » 

    At this point these tools are all pretty good. I also feel like folks often also over index on the output style or UI. Like to me the “you’re absolutely right!” sycophancy isn’t a notable bug; it’s a signal that you’re too in-the-loop. Generally my goal is to “shoot and forget”—to delegate, set the context, and let it work. Judging the tool by the final PR and not how it gets there.
I use LLM tools daily and my experience is that this just does not work on an application of any meaningful size or complexity.

You're going to immediately be overwhelmed with code, comments, markdown files, and all manner of extra text that may or may not solve your problem. The chore then becomes PR reviews of tons of iffy code, and if you merge too much of it, after too long your codebase will be a bloated mess that even the craftiest prompts won't untangle.

It's best to use to brainstorm and implement very targeted prompts, set and forget is crazy.

Post reply on HN