Skip to content

[Feature]: Jujutsu VCS support #1126

Description

@OdeToOpenSource

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I am describing a concrete problem or use case, not just a vague idea.

Area

apps/web

Problem or use case

It would be good for the worktrees / version control to support Jujutsu VCS: https://github.com/jj-vcs/jj / https://www.jj-vcs.dev/latest/

Currently it does not recognize jujutsu.

Proposed solution

Add support for Jujutsu

Why this matters

Initiating Git, gets issues when I am using Jujutsu

Smallest useful scope

Jujutsu worktrees support.

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

  • I would be open to helping implement this.

Activity

  1. added
    enhancementRequested improvement or new capability.
    needs-triageIssue needs maintainer review and initial categorization.
    on Mar 15, 2026
  2. binbandit commented on Mar 16, 2026

    @binbandit
    Contributor

    Can you not use the git backend with JJ?

  3. FugiTech commented on Mar 16, 2026

    @FugiTech

    As someone who uses JJ, I also thought I needed/wanted JJ workspace support in T3 code. But after using it a bit, I realized git worktrees mostly "just work" as-is.

    If you have a thread create a new git worktree, it will still show up in your main JJ repo (after you commit the changes). Because JJ checks out commits in a detached head state, you can even have your main repo/folder looking at the same changes as the thread's worktree. You can then take over the changes and merge them in however you want.

    The only snag is that once you start making changes to the branch in your main JJ repo, the worktree gets desync'd and you have to fuss with it to get it matching the changes you've made, if you want the agent to then keep working on things. Also, you obviously won't have working jj commands in the worktree, but that hasn't been a big deal for me personally.

    So yeah, overall as a JJ user I haven't found any need for explicit JJ support in T3 code, as the existing git features interop fairly well.


    It may still be worth leaving this open (or a similar issue) as a place for JJ users to track what they feel is missing or could be improved. But the OP didn't specify any specific needs or improvements so I don't feel there's any work for the maintainers to do currently.

  4. OdeToOpenSource commented on Mar 16, 2026

    @OdeToOpenSource
    Author

    Unless the documentation is out of date, git-worktrees is not supported (https://www.jj-vcs.dev/latest/git-compatibility/#supported-features). Claude Code added support for it recently: https://nitter.net/bcherny/status/2025007401766948935#m (https://nitter.net/pic/orig/media%2FHBpC7HzbYAET0-f.jpg)

    @FugiTech Agree, it is that 'worktree gets desync'd' is the reason I raised the feature request.

    Would be useful for jj bisect as well that I use a bit.

  5. gergesh commented on Apr 6, 2026

    @gergesh

    I submitted a PR - #1796

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementRequested improvement or new capability.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions