Skip to content

[Feature]: Support Linux Project Paths inside Windows T3 Code for WSL #2824

Description

@emincangencer

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

Not sure

Problem or use case

When using opencode serve on the WSL and t3 code on Windows, opencode needs linux path to work right. Adding projects via linux dir works. e.g. /home/emincan/projects/myapp
Project gets recognized, I can do agentic stuff just fine in t3code. BUT git and project icon etc. doesn't appear because it wants windows paths to find the .git or project icons.

Proposed solution

I propose:

  1. on windows a sort of path handling must be added for users using WSL for their codebase and coding agents
    For example if we add projects via: \wsl$\Ubuntu\home\emincan\projects\myapp
    To the agent, it should go as /home/emincan/projects/myapp (if codex, opencode etc. is inside it.)
    OR
  2. Besides windows project path or handling, during project creation support complete WSL experience (for those running both agent and projects inside WSL).

Why this matters

This way agents won't run powershell stuff thinking this is windows (as it does if you add paths with \wsl$\Ubuntu\home\emincan\projects\myapp).
And also solve no git or or other t3 side issues if given linux paths to add projects.

Smallest useful scope

Use T3 Code perfectly on WSL in a stable way.

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 May 27, 2026
  2. juliusmarminge commented on Jun 9, 2026

    @juliusmarminge
    Member

    Duplicate of #192

    The core ask (use T3 Code reliably against WSL projects from Windows) is what #192 tracks, and the \\wsl$ path-translation option is part of that discussion (see also #716 for the related UNC-path bug). Consolidating into #192.

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