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

Claude Session URL appended to commit messages and PR descriptions by default

github.com

Post reply on HN
Print view View original

91–100 of 257 posts

Re: Claude Session URL appended to commit messages and PR descriptions by default

#91

Post by MassiveQuasar »

leoqa wrote: post #85
Jcampuzano2 wrote: post #72

Earlier quoted context omitted.

Realistically, what do you actually get from viewing people's sessions? I honestly don't really understand why people care. The specific model used can't be important because theres a new trending one every couple weeks nowadays. The conversation could be wildly out there and have 10+ different iterations of the same thing in it that led to the final product, etc. It's not like before AI we were asking people to expl…

People don’t want their incompetence displayed. The session is probably a series of “continue” prompts with basic understanding demonstrated in the initial ask.

Do you also add all of your notes ever recorded to your PRs?

Re: Claude Session URL appended to commit messages and PR descriptions by default

#93

Post by mirashii »

mirashii wrote: post #87
skeledrew wrote: post #69

Earlier quoted context omitted.

Thing is, if you enable remote control for one session, it becomes globally enabled for all (which I personally prefer as I want to access all my sessions from my phone).

This isn’t quite true. There’s a daemon you can launch with `claude rc` that will let you get at all sessions, but if you just `/rc` in one session only that session becomes available.

Just in case, you can check your config. https://code.claude.com/docs/en/settings-reference#remotecon...

Re: Claude Session URL appended to commit messages and PR descriptions by default

#94

Post by lawrjone »

gedy wrote: post #74
klodolph wrote: post #21

I may be missing something, but this is exactly what I want as a default. I want the session links there. I see PRs from my coworkers with session links. I still get to control whether other people can see the session, but I don’t lose it. I don’t get the “unprofessional” argument. This is attribution. Attribution is professional. If you don’t want it, you turn it off or rewrite the commit messages. If you are having…

Sure, but it does spook some people like me where I frequently mention context in session like: "it would be better to fix this on the backend, but that is a separate team that moves VERY slowly", etc. And I don't want that accidentally getting broadcast.

Am I misunderstanding this change? This makes it sound like Claude is attaching the entire session content when I thought it was only a link that is exclusively readable by the author, unless deliberately shared?

Re: Claude Session URL appended to commit messages and PR descriptions by default

#95

Post by [deleted] »

drrotmos wrote: post #22

I really like working using Claude Code, but Anthropic has a really bad tendency to push out new "features" like this as default-on, through auto-update. That, and their models trying to do everything through bash (including editing files) is enough that I'm seriously looking in to switching harness to pi.

[deleted]

Re: Claude Session URL appended to commit messages and PR descriptions by default

#96

Post by lawrjone »

Insimwytim wrote: post #77

Wouldn't think I'd be cheering Antrophic decision, but this is excellent. They probably were thinking about how that serves them as an ad, not about transparency, but still. I say they should go one step further and somehow make it harder/inconvenient to turn it off (big tech is good at this already, so...); or, maybe, hide that option behind extra feature under premium subscription or something. P.S. The comments ar…

As a Claude user this is just a benefit to me. Means I can grab the session and resume if I ever see a commit I want to jump back into, and Claude can read these sessions itself whenever I reference the commit, which helps a bunch.

It might come with advertising benefits for them but expect it’s mostly just because it helps their tools work and that benefits everyone.

Re: Claude Session URL appended to commit messages and PR descriptions by default

#97

Post by lawrjone »

eli wrote: post #38
ketzu wrote: post #25

I like claude code, I use it quite a bit for things, and I don't mind the attribution (I do not plan to deceive people of me using AI or not for a change) and I think a link back to the session is valueable after the fact. At least for me, the session contains a lot of discussion, back and forth, changes from me and more. (Also, if the feature is not on by default, it probably might not exist.) However, I think claud…

Seems plausible that the feature was only added (quietly and by default) for marketing reasons

It’s really useful for helping agents navigate history and maintain continuity between sessions. So wouldn’t assume it’s for marketing, it has a lot of utility.

Re: Claude Session URL appended to commit messages and PR descriptions by default

#98

Post by lawrjone »

_pdp_ wrote: post #4

I really hate this attribution nonsense ... On one hand I guess it is fine to automatically tag that the commit was AI-generated. On the other hand, this will happen even if you audit every line and add your own changes too, which means the attribution is misleading.

It’s not meant for saying “this change was done by Claude” it’s meant to connect commits back to the session. Makes it way easier to jump back into a follow up change between sessions as the agent can reload parts of the context.

Anyone thinking this is about tagging AI generated changes and not just making the experience in Claude better is missing the point of the feature.

Re: Claude Session URL appended to commit messages and PR descriptions by default

#99

Post by [deleted] »

eli wrote: post #34
klodolph wrote: post #21

I may be missing something, but this is exactly what I want as a default. I want the session links there. I see PRs from my coworkers with session links. I still get to control whether other people can see the session, but I don’t lose it. I don’t get the “unprofessional” argument. This is attribution. Attribution is professional. If you don’t want it, you turn it off or rewrite the commit messages. If you are having…

It’s a default that changed silently during an automatic update. Also I frequently use an LLM to commit work that I have written. It is just misleading in that case.

[deleted]

Re: Claude Session URL appended to commit messages and PR descriptions by default

#100

Post by saghm »

sparsesignal wrote: post #59
klodolph wrote: post #21

I may be missing something, but this is exactly what I want as a default. I want the session links there. I see PRs from my coworkers with session links. I still get to control whether other people can see the session, but I don’t lose it. I don’t get the “unprofessional” argument. This is attribution. Attribution is professional. If you don’t want it, you turn it off or rewrite the commit messages. If you are having…

I'm OK with the attribution, but I just didn't like a session URL appearing on a public repo all of a sudden. I was left wondering "did I just leak my private session?" I don't understand why it isn't opt-in. Or at least a heads-up somewhere.

At this point it's believable to me that Anthropic might not even be aware of what features get added in a given release. It's hard to tell the difference between "they actively are against documenting all of the defaults they keep changing" and "they genuinely don't even pay enough attention to notice when their vibe-coded changes have changed a default". Functionally they're the same, and both would stem from similar (lack of) values, but I think it does kind of matter because it's essentially the difference between explicitly crafting an experience for users versus defining same things they want and letting the vibes end up driving it towards a bunch of user-facing emergent properties that no one has considered.

"Of course they were intentional in adding in an ad to everyone's git log" honestly night be the less cynical take, because the alternative is assuming that they actually look at git logs ever rather than only having Claude deal with it.

Post reply on HN