Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • > 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. "Fix login.ts lines 148-160, it's broken like this ___"

    by dfabulich
  • Kinda 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.
    by sixhobbits
  • > /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.

    by mritchie712
  • "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

    by WickyNilliams
  • Don't sleep on using Claude Code to improve your Claude Code config. Switch to plan mode and try the following prompt:

    read the document at https://blog.sshh.io/p/how-i-use-every-claude-code-feature and tell me how to improve my Claude code setup

    by michaelbuckbee

  •     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.

    by spicyusername
  • I really like this take on MCP: https://blog.sshh.io/i/177742847/mcp-model-context-protocol

    > Instead of a bloated API, an MCP should be a simple, secure gateway that provides a few powerful, high-level tools [...] In this model, MCP’s job isn’t to abstract reality for the agent; its job is to manage the auth, networking, and security boundaries and then get out of the way.

    by simonw
  • > 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...
    by simonw

Explore Birbla archives