Skip to content

[FEATURE]: configurable path for worktrees #14032

Closed as not planned
Closed as not planned

Description

@kvokka

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Now git worktrees are created as ~/.local/share/opencode/worktree/8481/cosmic-rocket, but it makes them tricky to save with ephemeral environments, like codespaces or even plain Docker containers. As a workaround i'm creating the link for the folder to the path that is convenient to me for ~/.local/share/opencode/worktree;

But it would be great to have this path configurable either globally or, even better, with the relative path to the project.

Now I use this temporary workaround

ln -sfT ~/my/awesome/opencode_worktrees ~/.local/share/opencode/worktree

Can implement it, if u approve the idea.

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Feb 17, 2026
  2. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Feb 17, 2026
  3. linussvahn commented on Mar 16, 2026

    @linussvahn

    Yes please! 🙏

    @thdxr any updates on this feature?

  4. assigned and unassigned on Apr 26, 2026
  5. removed
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  6. StephanMeijer commented on Jun 22, 2026

    @StephanMeijer

    Filed #33332 which builds on this with three more dimensions: base ref (e.g. origin/main instead of HEAD), git fetch before creation, and explicit branch naming (vs. the current hardcoded opencode/<adj-noun>). Plus a worktree.create.before plugin hook so the customization is extensible.

    Linking here as the originating ask on the location dimension — happy to scope the eventual PR however maintainers prefer (location-only first, full bundle, or plugin-hook-driven).

  7. github-actions commented on Aug 22, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions