Skip to content

Same project name, different folders #39676

Closed as not planned
Closed as not planned

Description

@wrymn

Description

OpenCode Desktop does not keep two separate folders distinct when both are checkouts or copies of the same Git repository. The project shown in the UI can differ from the directory the agent is actually using, so work intended for one Unity project may run in the other.

Expected behavior: Selecting a project switches the workspace and agent working directory to that project's absolute folder.

Actual behavior: The two folders collide. Switching projects can leave the UI showing one project while the agent session is rooted in the other.

Plugins

None relevant to project selection.

OpenCode version

1.2.27

Steps to reproduce

  1. Create two separate checkouts or copies of the same Git repository in different parent folders.
  2. Confirm both checkouts have the same Git remote and can be opened independently (in this case, as two Unity projects).
  3. Add or open both folders in OpenCode Desktop.
  4. Start a session in each project.
  5. Switch between the two projects and ask the agent to report its working directory.
  6. Observe that OpenCode does not consistently keep the entries separate: the selected project shown in the UI can point to the other checkout's working directory.

Screenshot and/or share link

Not available.

Operating System

macOS 26.5.2 (Apple Silicon)

Terminal

OpenCode Desktop app

Activity

  1. added
    needs:complianceThis means the issue will auto-close after 2 hours.
    and removed
    needs:complianceThis means the issue will auto-close after 2 hours.
    on Jul 30, 2026
  2. github-actions commented on Jul 30, 2026

    @github-actions
    Contributor

    Thanks for updating the issue! It now includes all the required information and looks good. We appreciate you taking the time to provide clear steps to reproduce and the relevant context.

  3. github-actions commented on Sep 29, 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