anomalyco / anomalyco/opencode

[FEATURE]:appearance.fontSize setting not applied to UI or terminal font size (v1.18.21 Linux)

Open
#44,184 2 comments 0 reactions 1 assignee View on GitHub

@Hona is already working on this.

Since Aug 22, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

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

OpenCode Desktop v1.18.21 Linux

Problem

Changing settings.v3.appearance.fontSize in the desktop settings has no visible effect on the UI font size or the embedded terminal font size. The setting is persisted correctly but not applied.

Expected behavior

The desktop UI font size should reflect the appearance.fontSize setting, and the terminal should also use the configured size.

Actual behavior

The value is persisted (confirmed via jq on ~/.config/opencode/default.dat), but the visible font size remains unchanged after relaunch.

Environment
  • OpenCode Desktop: v1.18.21
  • OS: Linux (Ubuntu/Debian based — please specify)
  • Desktop data store: ~/.config/opencode/default.dat or ~/.config/opencode/
Steps to reproduce
  1. Open OpenCode Desktop settings
  2. Change Appearance → Font Size to any value (e.g., 18)
  3. Restart the app
  4. Observe that font size remains unchanged
Additional context
  • Issue #24131 (v1.14.22) reported the same problem and was closed as not_planned / auto-closed
  • Issue #26269 requested Ctrl++ / Ctrl+- shortcuts, also closed
  • The setting exists in config schema and has a setter, but the frontend does not apply it to CSS font-size variables
  • Terminal initialization uses a hard-coded fontSize: 14
Possible workarounds (for now)
  • Use OS-level Display Scaling / Zoom
  • Use browser Ctrl++ / Ctrl+- if running via OpenCode web

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.