You can both use a separate account and have Claude co-sign its commits. > In the context of $DAY_JOB, I don't think it matters anymore I meant mosyly for ope

You can both use a separate account and have Claude co-sign its commits. > In the context of $DAY_JOB, I don't think it matters anymore I meant mosyly for open-source projects, but if in your $DAY_JOB you (occasionally) use AI much more than your colleagues, it would matter very much. Especially for those who will come after you. > And 99.99% of the commits is AI assisted / authored I'm extremely sad that your job is like this. Keep in mind that it might be specific to your location. If in the company everyone uses AI a lot, AI co-signing can sure be redundant. > something that takes away my agency from me. Putting my name on a commit means I take pride in it and that I want to ensure that I did my utmost best to verify it. With an LLM's co-author tag, I find myself slipping easily instead on this metric. If an LLM co-author really makes you be more sloppy and get away with more in your company, avoiding it could indeed make sense. The best solution, for that specific situation, could indeed be making a dedicated account (or more than one), and explaining in its profile how you're going to use it ("This account will make heavy use of AI with xy models, but I'll review all the code carefully and take responsibility for it"). That account could be a co-signer, though, instead of the only signer; but for this situation it probably wouldn't make a lot of difference.