anomalyco / anomalyco/opencode

web: plan/build selector missing when accessing remote instance from mobile Firefox

Open
#48,810 1 comment 0 reactions 1 assignee View on GitHub

@Brendonovich is already working on this.

Since Sep 13, 2026.

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

Description

Summary

Accessing a running OC2 desktop instance remotely (opencode serve / opencode pair, via Mac internal IP) from Firefox on Android never shows the plan/build selector in the web UI composer/header area.

Environment

  • opencode version: v2.0.2 (opencode --version)
  • OS: Darwin G613393F4F 25.6.0 Darwin Kernel Version 25.6.0: Tue Aug 18 17:51:47 PDT 2026; root:xnu-12377.161.15.700.19~2/RELEASE_ARM64_T6050 arm64
  • Terminal: xterm-256color (COLORTERM empty, TERM_PROGRAM empty)
  • Shell: /bin/zsh
  • Install/channel: latest (local install, v2.0.2 vs skill snapshot 2.0.3)
  • Active plugins: none found in config (checked opencode.jsonc, no plugin key; no .opencode/plugin/ files)

Reproduction

  1. Start OC2 desktop instance on Mac, expose via opencode serve / opencode pair.
  2. From Android phone with Firefox, navigate to Mac internal IP instance URL.
  3. Open any session / composer view.
  4. Observe composer/header area — plan/build selector is not rendered.

Expected Behavior

Plan/build mode selector should be visible and switchable in the web UI, same as desktop/TUI.

Actual Behavior

Selector is always missing in the remote mobile web view. No error observed; rest of UI loads.

Additional Context

  • Client: Firefox on Android, remote access via Mac internal IP.
  • Frequency: always reproducible.
  • TUI comparison: not checked.
  • No workaround tried yet. No relevant logs/config snippets collected yet.

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.