Live data from Hacker News

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

github.com

151–160 of 256 posts

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

#151

Earlier quoted context omitted.

100% agree with this. Want my browser search history too so you can see my thought process? This is terrible. I have no desire to read your Claude conversation. I don’t even want to read mine if I do use Claude. The code is the artifact. There’s no value in trying to make the noisy, verbose conversation one. It’ll likely be dead in future years anyway.

I disagree with this. The code alone is not the artifact. How you came to the decision to write the code in a certain way is certainly an important artifact of the development process. Otherwise how would your coworkers know whether or not a particular piece of logic is still relevant?

By commenting your code?

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

#152

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…

Same here, cool, now Claude can grab the context from the session to reason better about why things are the way they are. Maybe an ID alone would have been better, not a whole http url.

It feels like an absolute failure of project management if your tooling needs to attach a session identifier in a git commit message for it to understand what’s going on.

Wikis, changelogs, decision records, issue trackers and more are available to provide greater context for you, your team and the agents you deploy.

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

#153

This is probably a controversial take, but I love this. Back in the early days of claude code I had to write a script (well, claude wrote it) to pull out the session id and append it to every commit. It's a lifesaver when you are trying to debug an old commit to pull up the chat session that actually wrote it.

This annoyed me to the point that I created a python script that could search opencode's database and then a skill that uses the script to find the session I was thinking of. It's nice to be able to say "I think 4 days ago I had an issue with a dropdown in Qt6, find that session." Saves a lot of time and tokens.

I've been using the "experimental teams" in claude code forever and its great for this. I never start a claude code session manually, I just ask the main agent to open a new tmux window for me. The lead agent knows all the agents I've ever interacted with and built its own system to keep track of things between compactions.

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

#154

Earlier quoted context omitted.

I disagree with this. The code alone is not the artifact. How you came to the decision to write the code in a certain way is certainly an important artifact of the development process. Otherwise how would your coworkers know whether or not a particular piece of logic is still relevant?

By commenting your code?

Ok, but folks aren't even writing their own code, you think they'll go back and comment generated code? They often don't even look at the implementation that closely.

Also, while commenting is good, commit messages can stick around longer.

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

#157

Earlier quoted context omitted.

100% agree with this. Want my browser search history too so you can see my thought process? This is terrible. I have no desire to read your Claude conversation. I don’t even want to read mine if I do use Claude. The code is the artifact. There’s no value in trying to make the noisy, verbose conversation one. It’ll likely be dead in future years anyway.

I disagree with this. The code alone is not the artifact. How you came to the decision to write the code in a certain way is certainly an important artifact of the development process. Otherwise how would your coworkers know whether or not a particular piece of logic is still relevant?

> How you came to the decision to write the code in a certain way is certainly an important artifact of the development process. Otherwise how would your coworkers know whether or not a particular piece of logic is still relevant

Not really. Why is always more important than how. Even what is more important. Relevancy of a particular block of code is in the specs and some technical aspecs of computing/library/platform, not in the thought process of the developer.

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

#158
post #139

Earlier quoted context omitted.

Agree, that it is an ad. Also, unless the full session (in a resume-able format, along all session artifact such as intermediate research/docs used to produce the final output) is also included in the commit, the session id is useless. I presume this is Anthropic trying to their "usage" stats before their IPO.

Funny to compare it to “Sent from iPhone” that Apple appended to emails by default way back when. It was an ad, but nobody cared because using iPhone was a point of pride.

People cared. Anyone who did and could do so turned it off immediately as with every service that appends any of that nonsense.

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

#159
I consider my prompts and prompting style to be trade secrets. I've developed a very efficient and productive workflow for myself over the years without tutorials, without books, etc.

Anthropic is making very strange and very opinionated decisions far too often for my liking. It's really making me second guess my continued use of Claude Code.

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

#160
I don't really understand what makes this different from companies stamping "Made in China" on products that were made in China.

The line between "advertisement" and "attribution" seems to depend upon your impression of the entity taking the attribution.

Post reply on HN