Crazy how fast Claude Code is evolving, every week there’s something new to learn, and it just keeps getting better.
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 .
How I use every Claude Code feature
121–130 of 193 posts
Re: How I use every Claude Code feature
#122> 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.
Re: How I use every Claude Code feature
#123"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
The internet is dead. Long live the internet.
Re: How I use every Claude Code feature
#124Kinda sad if 3000 words is now considered "too long to read through rather use as reference" but some interesting points, I'd be keen to see an even longer version with actual examples instead of placeholder ones.
Re: How I use every Claude Code feature
#125I really enjoyed reading this. One thought I had on the issue of paths in Claude.md My concern with hardcoding paths inside a doc, it will likely become outdated as the codebase evolves. One solution would be to script it and have it run pre commit to regenerate the Claude.md with the new paths. There probably is potential for even more dev tooling that 1. Ensure reference paths are always correct, 2. Enforces standa…
Re: How I use every Claude Code feature
#126> 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…
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:
The agentic part of the equation is improving on both sides all the time.
Re: How I use every Claude Code feature
#127"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…
Re: How I use every Claude Code feature
#128> 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...
We have an AGENTS.md symlinked to CLAUDE.md, seems to work fine.
Re: How I use every Claude Code feature
#129> 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.
Re: How I use every Claude Code feature
#130Earlier quoted context omitted.
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…
Not worried about hallucinations?
> the author clearly read through, organized, and edited the output.
Also worth noting, I've read plenty of human written stuff that has errors in it, so I read everything skeptically anyway.