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

More chat options and a way to reset all settings

Open
#74 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@beppe2880 is already working on this.

Since Oct 24, 2026.

  • #75 by @beppe2880 — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
mobile

Research direction

The issue proposes new chat options and a reset but names no files. A linked PR #75 is open; review it first. Then read the settings and chat screen sources in this Kotlin Android app to locate option handling. Done means the listed output lines, refresh, text size, keep-steps options and confirmed reset work as described.

Written by the indexing model from the issue text.

Description

feature
Problem

A few chat behaviors are still fixed: tool output always shows 12 lines before "Show more", a running command's output is read every 700 ms, steps followed live always fold back when the answer ends, and the chat text only follows the system font size. There is also no way to go back to the defaults after changing many options.

Proposal
  • Live activity:
    • Output lines: 6, 12 (default), 24 or 50 lines before "Show more";
    • Keep steps open (off): what was followed live stays open after the answer ends;
    • Output refresh: 0.3, 0.7 (default), 1.5 or 3 seconds, shown while shell commands are followed; slower uses less data and battery.
  • Appearance: Chat text size, Small, Default, Large or Largest, applied to the transcript on top of the system size.
  • Reset all settings, with a confirmation: every option goes back to its default; saved servers, drafts, seen intros and terminal keys are kept.
Dominant language
Kotlin
Stars
1
Forks
0
Avg merge
6h 11m
Merged PRs (30d)
32

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 beppe2880/opencode-mobile

All issues in beppe2880/opencode-mobile

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.