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

141–150 of 193 posts

Re: How I use every Claude Code feature

#141

Post by simonw »

caymanjim wrote: post #131
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...

In my experience, neither Claude nor any other agent actually reads AGENTS.md (or CLAUDE.md or anything else) without being told to explicitly every session.

I've sniffed Claude Code's HTTP traffic and confirmed that the CLAUDE.md file content (and AGENTS.md if it is @-referenced) is automatically included in the system prompt without it having to perform any additional file read operations.

Re: How I use every Claude Code feature

#142

Post by layercakex »

Are "agents" really as useful as the hype makes them out to be?

Most of the time I'm just pasting code blocks directly into raycast and once I've fixed the bug or got the properly transformed code in the shape that I aimed for, then I paste it back into neovim. Next i'm going to try out "opencode"[0], because I've heard some good things about it. For now, I'm happy with my current workflow.

[0] https://github.com/NickvanDyke/opencode.nvim

Re: How I use every Claude Code feature

#143

Post by dboon »

layercakex wrote: post #142

Are "agents" really as useful as the hype makes them out to be? Most of the time I'm just pasting code blocks directly into raycast and once I've fixed the bug or got the properly transformed code in the shape that I aimed for, then I paste it back into neovim. Next i'm going to try out "opencode"[0], because I've heard some good things about it. For now, I'm happy with my current workflow. [0] https://github.com/Nic…

to be clear that repo is simply a thin neovim plugin for the truly excellent agent TUI opencode

I recommend using it directly instead of via the plugin

Re: How I use every Claude Code feature

#144

Post by cmrdporcupine »

smokel wrote: post #126
noodletheworld wrote: post #97

Earlier quoted context omitted.

Claude is just better at coding than cursor. Really, the interface isn't a meaningful part of it. I also like cmd-L, but claude just does better at writing code. ...also, it's nice that Anthropic is just focusing on making cool stuff (like skills), while the folk from cursor are... I dunno. Whatever it is they're doing with cursor 2.0 :shrug:

Cursor can use the Claude Sonnet and Claude Opus LLMs, so I would expect output to be quite similar in that respect. The agentic part of the equation is improving on both sides all the time.

There's something in the prompting, tooling, heuristics inside the Claude Code CLI itself that makes it more than just the model it's talking to and that becomes clear if you point your ANTROPHIC_URL at another model. The results are often almost equivalent.

Whereas I tried Kilo Code and CoPilot and JetBrain's agent and others direct against Sonnet 4 and the output was ... not good ... in comparison.

I have my criticisms of Claude but still find it very impressive.

Re: How I use every Claude Code feature

#145

Post by ramoz »

Hooks are underutilized and will be critical for long-running and better agent performance. Excited to release Cupcake in the coming weeks. What I started building when i made the feature request for hooks.

- https://github.com/eqtylab/cupcake

- https://github.com/anthropics/claude-code/issues/712

Re: How I use every Claude Code feature

#146

Post by WickyNilliams »

paulcole wrote: post #135
WickyNilliams wrote: post #76

"Claude Code isn’t just an interactive CLI; it’s also a powerful SDK for building entirely new agents—..." Em dash and "it's not X, it's Y" in one sentence. Tired of reading posts written by AI. Feels disrespectful to your readers

> Tired of reading posts written by AI. Didn’t realize you were forced to read this? > Feels disrespectful to your readers I didn’t feel disrespected—I felt so respected I read the whole thing.

Nothing there implies I was forced. I read the whole thing. It was not disclosed that it was written (in part?) by AI. And That sentence I quoted was pretty far along.

Re: How I use every Claude Code feature

#147

Post by WickyNilliams »

freedomben wrote: post #118
WickyNilliams wrote: post #76

"Claude Code isn’t just an interactive CLI; it’s also a powerful SDK for building entirely new agents—..." Em dash and "it's not X, it's Y" in one sentence. Tired of reading posts written by AI. Feels disrespectful to your readers

I have the same instinctive response to reading AI generated stuff, but I'm coming to a more moderate position where I'm trying to judge the content on the content itself. For example, in a post like this, it doesn't bother me at all because it's still an extremely useful reference, and the author clearly read through, organized, and edited the output. This is a good example of usage of AI in my opinion. The people w…

Writing is a tool for thought I feel, and when you're outsourcing your thought, it detracts from whatever you intended to say. I guess if it was that heavily-edited such a telltale sign wouldn't have remained.

I use AI for code, but I never use it for any writing that is for human eyes.

Re: How I use every Claude Code feature

#148

Post by paulcole »

WickyNilliams wrote: post #146
paulcole wrote: post #135

Earlier quoted context omitted.

> Tired of reading posts written by AI. Didn’t realize you were forced to read this? > Feels disrespectful to your readers I didn’t feel disrespected—I felt so respected I read the whole thing.

Nothing there implies I was forced. I read the whole thing. It was not disclosed that it was written (in part?) by AI. And That sentence I quoted was pretty far along.

> It was not disclosed that it was written (in part?) by AI

Who gives a shit?

If you can’t stand AI writing and you made it pretty far along before getting upset, who are you mad at, the author or yourself? Would you be happier if you found out this was written without AI and that you were just bad at detecting AI writing?

Re: How I use every Claude Code feature

#149

Post by riskable »

cheesedoodle wrote: post #137

What type of projects are you guys building? I bought Max and these features to try it out to build a more complex project (ROS2) and that does not seem to work out at all… HTML page, yes, embedded project not so much.

With all the LLM coding assistants, you have to get a feel for each model and which extension/interface you're using with them. Not only that, but it's also dependent on your project!

For example, if you're writing a command line tool in Python, it doesn't really matter what model you use since they're all really great at Python (LOL). However, if you're writing a complicated SPA that uses say, Vue 3 with Vite (and some fancy CSS framework) and Python w/FastAPI... You want the "smartest" model that knows about all these things at once (and regularly gets updated knowledge of the latest versions of things). For me, that means Claude Code.

I am cheap though and only pay Anthropic $20/month. This means I run out of Claude Credits every damned week (haha). To work around this problem, I used to use OpenAI's pay-per-use API with gpt5-mini with VS Code's Copilot extension, switching to GPT5-codex (medium) with the Codex extension for more complicated tasks.

Now that I've got more experience, I've figured out that GPT5-codex costs way too much (in API credits) for what you get in nearly all situations. Seriously: Why TF does it use that much "usage". Anyway...

I've tried them all with my very, very complicated collaborative editor (CRDTs), specifically to learn how to better use AI coding assistants. So here's what I do now:

    * Ollama cloud for gpt-oss:120b (it's so fast!)
    * Claude Code for everything else.
I cannot understate how impressed I am with gpt-oss:120b... It's like 10x faster than gpt5-mini and yet seems to perform just as well. Maybe better, actually because it forces you to narrow your prompts (due to smaller context window). But because it's just so damned fast, that doesn't matter.

With Claude Code, it's like magic: You give it a really f'ing complicated thing to troubleshoot or implement and it just goes—and keeps going until it finishes or you run out of tokens! It's a, "the future is now!" experience for sure.

With gpt-oss:120b it's more like having an actual conversation, where the only time you stop typing is when you're reviewing what it did (which you have to do for all the models... Some more than others).

FYI: The worst is Gemini 2.5. I wouldn't even bother! It's such trash, I can't even fathom how Google is trying to pass it off as anything more than a toy. When it decides to actually run (as opposed to responding with, "Failed... Try again"), it'll either hallucinate things that have absolutely nothing to do with your prompt or it'll behave like some petulant middle school kid that pretend to spend a lot of time thinking about something but ultimately does nothing at all.

Re: How I use every Claude Code feature

#150

Post by riskable »

rglover wrote: post #103
MangoToupe wrote: post #40

Blog posts like this would really benefit from specific examples. While I can get some mileage out of these tools for greenfield projects, I'm actually shocked that this has proven useful with projects of any substantial size or complexity. I'm very curious to understand the context where such tools are paying off.

It seems to be relative to skill level. If you're less-experienced, you're letting these things write most if not all of your code. If you're more experienced, that's inverted (you write most of the code and let the AI safely pepper things in).

Don't rule out laziness! I'm a very experienced senior dev (full stack, embedded, Rust, Python, web everything, etc)... Could I have spent a ton of time learning the ins and outs of Yjs (and the very special way in which you can integrate it with TipRap/prosemirror) in order to implement a concise, collaborative editor? Sure.

Or I could just tell Claude Code to do it and then spend some time cleaning it up afterwards. I had that thing working quite robustly in days! D A Y S!

(Then I had the bright idea of implementing a "track changes" mode which I'm still working on like a week and a half later, haha)

Even if you were already familiar with all that stuff, it's a lot of code to write to make it work! The stylesheets alone... Ugh! So glad I could tell the AI something like, "make sure it implements light and dark mode using VueUse's `useDark()` feature."

Almost all of my "cleanup" work was just telling it about CSS classes it missed when adding dark mode variants. In fact, most of my prompts are asking it to add features (why not?) or cleaning up the code (e.g. divide things into smaller, more concise files—all the LLMs really love to make big .vue files).

"Writing most of the code"? No. Telling it how to write the code with a robust architecture, using knowledge developed over two decades of coding experience: Yes.

I have to reject some things because they'd introduce security vulnerabilities but for the most part I'm satisfied with Claude Code spits out. GPT5, on the other hand... Everything needs careful inspection.

Post reply on HN