Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

tui: scroll speed setting only increments (→ works, ← does nothing)

Open Beginner friendly
#55,383 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
62/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
cli

Research direction

The payload does not name a file. Start by finding the TUI settings dialog and the handler for the "TUI scroll speed" row, then check how it treats the left and right arrow keys. Right increments the value, so the decrement branch is the likely gap. Done when left arrow lowers the value and it can be returned to 1 from the UI, with the value still reloading correctly from cli.json.

Written by the indexing model from the issue text.

Description

Description

The scroll speed setting in the settings dialog can only be increased. With the row selected, → increments the value but ← does nothing, so once it has been raised there is no way to bring it back down from the UI.

Workaround: cli.json accepts lower values ("scroll": { "speed": 1 }) and valid edits reload while the TUI is running.

Plugins

opencode-skill-creator, plus local plugin files: engram.ts, model-variants.ts, opencode-review-transport.ts, skill-registry.ts, telemetry-runtime.ts

OpenCode version

2.0.28

Steps to reproduce
  1. Run opencode in Windows Terminal
  2. Press Ctrl+P and select Open settings
  3. Select the scroll speed row (labelled TUI scroll speed)
  4. Press → — the value increases
  5. Press ← — nothing happens
Screenshot and/or share link

No response

Operating System

Windows 11 (NT 10.0.26300, x64)

Terminal

Windows Terminal

Dominant language
TypeScript
Stars
213k
Forks
28.4k
Avg merge
8h 58m
Merged PRs (30d)
251

Getting set up

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.

More from anomalyco/opencode

All issues in anomalyco/opencode

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.