Skip to content

[Bug]: Theme CLI help does not explain that remote-only desktop clients ignore the setting #37256

Closed

Description

@hong-tm

Before submitting

  • I searched existing issues and PRs and did not find a duplicate of this reporting issue.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/server (theme CLI help), with desktop behavior as the reproduction context.

Summary

t3 theme set --help says "Set the environment's theme; connected clients switch to it." This does not explain that a desktop app connected to a server on another machine does not consume that server's published themes or default theme, even when its local environment is disabled.

The detailed appearance documentation does explain this restriction. The CLI help does not, so a successful command is easy to interpret as applying the theme to the connected desktop app. The MCP theme tool likewise returns a successful server-side setting result, without any client-application acknowledgment. This is a scope/wording report, not a request to let arbitrary remote environments override the desktop's theme.

Steps to reproduce

  1. Use the Windows desktop app with Local environment disabled.
  2. Connect it to a Linux server on a different machine through T3 Connect.
  3. On that server, publish the unmodified Nyx theme from https://github.com/Deepusleepy/t3-nyx-theme with t3 theme set nyx.json.
  4. Run t3 theme show on that server.
  5. Open Settings > Appearance in the Windows desktop app.
  6. Compare with the web UI served directly by the Linux server.

The same desktop result was observed after invoking t3_theme_set from a thread on that remote server with {"themeId":"nyx","appearance":"dark"}.

Expected behavior

The theme command's help should make its scope explicit: it sets a server default consumed by the server-served web client, the primary local desktop environment, or the matching same-machine background service. Other remote connections do not apply it to the desktop app.

A short limitation in the CLI help, and a corresponding clarification in the MCP tool description/guide, would prevent agents and users from treating server-side success as confirmation that a remote desktop client applied the theme. No change to theme-source precedence is requested here.

Actual behavior

  • The command succeeds and the server reports Environment theme: "nyx". and Published themes: nyx.
  • The server-served web client lists Nyx and loads its custom stylesheet.
  • The Windows desktop app still lists only its built-in themes. Nyx is absent, and its appearance does not change.
  • Manually importing the exact same JSON through Add theme and selecting Nyx in the desktop app works.

Impact

Cosmetic issue. Installation instructions and agent workflows report server-side success even though the requesting desktop client remains unchanged, leading to unnecessary reloads and troubleshooting.

Version or commit

Desktop app and remote server: 0.1.10-nightly.20261115.4736.

Environment

Windows desktop app; Linux x64 remote server; Local environment disabled; T3 Connect remote connection. No local/remote version mismatch was present in the final reproduction.

Relevant output

t3 theme show
Environment theme: "nyx".
Published themes: nyx.

The native theme tool returned:

{"themeId":"nyx","appearance":"dark","published":false}

This confirms a server-side setting result, not desktop application of the theme.

Source evidence and related work

Workaround

Import the theme JSON through Settings > Appearance > Add theme in the desktop app, then select it. This worked without enabling the local environment or reconnecting environments.

Duplicate search

Searched both open and closed issues and PRs with: remote environment theme, environmentThemes, desktop theme local environment, theme remote-only, themeEnvironmentIdAtom, published themes local disabled remote, theme tool misleading, t3_theme_set remote, and theme set connected clients. The related entries above were read before filing.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions