Skip to content

Allow opening one project across multiple directories/worktrees without requiring local splitting workarounds #43316

Closed as not planned

Description

@lianglujiang

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

Problem

Currently, when a single project needs to be opened or worked on from multiple directories, users may need local workaround flows such as splitting-opencode-projects. This adds friction and makes multi-directory workflows feel like something users have to manually adapt around instead of something opencode supports directly.

Use case

Some projects naturally span multiple local directories, for example:

  • monorepos split across several working directories
  • generated/distribution mirrors next to source repositories
  • multiple worktrees for parallel feature work
  • related project folders that should share one opencode project/session context

In these cases, it would be useful for opencode to treat several directories as belonging to the same project identity.

Requested behavior

Allow a project to be opened from multiple configured directories without requiring a local skill/workaround.

Possible approaches:

  • Support multiple root paths for a single project
  • Let users define project aliases that map several directories to the same project
  • Allow session/project identity to be configured independently from the current working directory
  • Provide first-class support for multi-directory or multi-worktree project contexts

Expected benefit

This would make opencode smoother for users working with monorepos, mirrors, generated repos, and parallel worktrees. It would also reduce the need for custom local skills that compensate for project-directory limitations.

Activity

  1. github-actions commented on Aug 19, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

    If your request isn't covered by one of these, please add a comment explaining what's different so maintainers can keep the issues distinct.

  2. github-actions commented on Oct 18, 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