3 ms·
Eh, 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 h
by nijave 1mo ago
Eh, 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"
- tepmoc 1mo agoI found both models produce word salad for PR bodies by default. Same thing with commits messages. I had to create hooks that invoke skills when pushing new commit and open PR body text.
- nijave 1mo agoI made a skill which is maybe why GPT is doing okay but Claude seems to straight up ignore it (it invokes/reads it but doesn't follow the directions)
- tepmoc 1mo agoI found using just skill isnt enogh. You have to bounce its turn and inject skill text to actually follow instructions 100%. Because even if you use PreToolUse hook and don't bounce it, it will never work since skill text is injected when along with text that already perpared to it need to be edited.