Summary

In the web UI served by the OpenCode v2 background service, the message composer field blocks Android Gboard voice typing: Gboard shows "Voice typing is not available here" and the mic option is unavailable, only in this field. This makes mobile dictation impossible, which matters since the web UI is a main mobile entry point. Requesting a plain <textarea> composer on mobile (or otherwise IME/voice-typing-compatible input).

Environment

• opencode version: 2.1.2 (Desktop app, stable channel, bundled service 2.1.2-x64)
• OS (server): macOS Darwin 24.6.0, Intel x64
• Client: Google Pixel 6a, Chrome (Android), Gboard, French locale
• Terminal: n/a (web UI accessed via opencode pair --remote / OpenTunnel)
• Shell: n/a
• Active plugins: none

Reproduction

1. Run OpenCode Desktop 2.1.2 on macOS with the default shared background service
2. Generate a remote pairing link with opencode pair --remote and open it in Chrome on an Android phone (Gboard keyboard)
3. Open a project, then focus the message composer field
4. Try to use Gboard voice typing (mic on the keyboard toolbar)

Expected Behavior

Gboard dictation should work in the composer, as it does in plain <textarea>/<input> fields on other websites.

Actual Behavior

Gboard refuses with the toast "la saisie vocale n'est pas disponible ici" ("voice typing is not available here"). The mic is unavailable only in the OpenCode composer; the same keyboard dictates fine in other apps and web fields.

Additional Context

• Reproduces consistently.
• The composer appears to be a rich contenteditable-based editor (the SPA bundle contains contenteditable editor code). Gboard voice typing is known to be unavailable in some rich-editable web fields.
• Workaround: dictate in another field (e.g. Google Keep) and paste into the composer.
• Suggestion: on small viewports, render a plain <textarea> (or an editor mode compatible with IME voice input); this would also improve autocorrect and general mobile typing.