While jujitsu is superior to git in many ways, I found it hard to get Claude and other agents to use it consistently and more effectively than git.
Git and jj work trees are not interoperable, so any tool that assumes git forces you back. Looking at you, Claude app…
Recently JJ supports colocated workspace/worktrees so you get a .git directory in the workspace so git is happy. Also workmux has initial support for JJ colocated workspaces and sesh (tmux session handler) also has experimental support. Whilst there are still some sharp edges, none of them are around data integrity, and I'm using it every day. YMMV.
> I found it hard to get Claude and other agents to use it consistently and more effectively than git.
Write yourself a very good JJ skill or reference file from your AGENTS.md.
My LLMs struggled with it a lot too, but I slowly covered everything they were messing up and they haven't made a mistake in months now. Even when there are "divergent" issues, it knows how to recover now.
> I found it hard to get Claude and other agents to use it consistently and more effectively than git.
That was the biggest hurdle for me too. I was a 2+ year jj user, then I had to switch back to git because of all the agentic tools relying on it.
I recently went back to jj, after finding a decent skill [1] and discovering Emacs' majutsu plugin. Claude still tries to do a git command every once in a while, but it's a lot more bearable.
I wrote an extensive skill some time ago. Works really nice https://codeberg.org/thisalex/jj-skill
It's a tad opinionated: my agents are not allowed to push to external repos — but that's easy to change if you need
Yeah it took me a while to get agents comfortable with it. Mostly I had access to Gemini, and 2.x and early 3.x models struggled. By 3.7 it was much better, and with all the 4 models it's a complete non-issue. Separately I (and others) worked on improving our JJ skills and they're in a much better place now with some scripts that wrap up more complex operations (e.g. maintaining file copy/move markers).
This hasn't been an issue for me for a while now, and I've actually had Opus 5.5 and Gemini Hydrogen build and submit a 28 commit deep stack, with all the reviewing/rebasing/shifting around that entails.
You should really be doing your own commits anyway. It's not hard, and it's important to make sure you review what is going into the repo.
I have hooks that prevent repository modifications with git commands. And I have a global AGENTS.md file that says to prefer jujutsu if present.
It works totally fine.
Use hooks. Prompts are for guiding an agent towards a goal. If you want it to never, ever, do a thing then write some hooks that detect an attempt to use git and refuse the tool use. "Is the `git` executable in this command line" is entirely deterministic and doesn't require throwing an LLM running on 15 GPUs at the problem.