Skip to content

[Feature]: Windows Server 2016 #2316

@ew1982

Description

@ew1982

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/desktop

Problem or use case

Spent the last couple hours trying to figure out why T3 won't work with my claude code CLI. Finally got my answer from the CLI.

Image

I don't know if T3 can be made to work with Windows Server 2016, but there are plenty of people still using this for their VM at work and currently your tool isn't available for us so we're stuck with CLI until we can talk our companies into upgrading us. Would be great if there's an easy fix for this or compatibility could be added. Thanks.

Proposed solution

Add compatibility with Windows Server 2016 using Claude 2.1.111 as the max build available, 2.1.113 for sure breaks on this windows version, not sure about 112.

Why this matters

A lot of people still use 2016 at work due to company budgets or various other reasons.

Smallest useful scope

Making it work with Server 2016.

Alternatives considered

Telling my company I need a better VM, getting laughed at.

Risks or tradeoffs

No response

Examples or references

Image

Contribution

  • I would be open to helping implement this.

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