Maybe using git notes for the conversation or conversation summary is better.
Claude Session URL appended to commit messages and PR descriptions by default
101–110 of 257 posts
Re: Claude Session URL appended to commit messages and PR descriptions by default
#102I 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…
Why not use something like openspec? You get the benefits of context without a whole conversation to read.
Re: Claude Session URL appended to commit messages and PR descriptions by default
#103Everyone loves AI so much that they want to hide the fact that they're using AI.
Re: Claude Session URL appended to commit messages and PR descriptions by default
#104Earlier 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.
I have never (manually) launched a daemon, but all my sessions are automatically available.
Re: Claude Session URL appended to commit messages and PR descriptions by default
#105I 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 is because many "developers" want to pretend that they have read the code and have understood it so they can claim it as their own. Attribution is indeed professional. If you use an AI to write the code for you and have no idea why you accepted the decisions it made nor can you explain them to another human, that would be clear evidence of acute skill atrophy.
Do you add your IDE version to your commits, everytime you use autocomplete, or when you refactor the code and ask ide to replace all function names?
Re: Claude Session URL appended to commit messages and PR descriptions by default
#106I 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.
After I moved to Pi I really started to hate Claude Code.
I still have to use Claude Code at work and after getting used to Pi I feel I'm always fighting against it.
Maybe the way I enjoy working with LLMs just works better with Pi.
Re: Claude Session URL appended to commit messages and PR descriptions by default
#107A lot of people say this is a reasonable feature, and I agree (I would strongly consider having it on), but that's not the defense they think it is.
- Having the feature available seems good.
- Having the feature default on is debatable, but not outside the realm of possibility.
- Having the feature default on, without any kind of release notes that say that it happens and link to the option to disable it is clownshoes "bring back the ghost of Steve Jobs to yell at the product team" type behavior.
Re: Claude Session URL appended to commit messages and PR descriptions by default
#108Eh, I don't want the tools I use to stamp their names on everything. It's also not uncommon for me to switch between GPT and Claude or different models in the harness if one of them isn't doing well. GPT-5.6 Terra has been doing a significantly better job at writing concise PR bodies and commit messages than Claude's usual multi paragraph word soup.
I don't need "Created by Claude Code 1.2.3, Opus 4.8 inside tmux inside ghostty on macOS ## on Mac Book Pro 2019 by git 123 in /Users/nijave/repo"
If you want session context, commit the session or prompt or add a git note. I think opaque URIs are the wrong approach unless they're to an issue tracker with more details. Proprietary URIs are not easily usable and interoperable with other tools. Commited information should still be valid and useful in 10 years.
I'm also not sure session is the right level of abstraction. I recently setup Claude Code with subscription delegation to opencode harness with z.ai coding plans and opencode go coding plan and it's been working fairly but there is no singular "session"
Re: Claude Session URL appended to commit messages and PR descriptions by default
#109Earlier 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.
I also wouldn't want people to have viewed my browser history on every commit pre-AI era.
Re: Claude Session URL appended to commit messages and PR descriptions by default
#110Earlier quoted context omitted.
Which ones are you thinking of? Were they actually generating code, or were they loading in templates or mechanically building interface stubs?
Like "code generator IDE plugins". There are hundreds of them for just about every IDE you can think of. I can't tell if this is a serious question or not, but metaprogramming/generators are decades old concepts that have been common features of basically every IDE since the 90s.
That’s not what we’re talking about, though. That’s mechanical transformation, and isn’t the same thing as code that’s generated on demand from scratch, based on plain-language intent.
Surely you know the difference, right? I assume you’ve used LLMs to generate code by now?