Summary
When typing in the Amicode chat input, switching to another application (e.g. Slack) and then switching back to VS Code, the cursor disappears from the chat input. The user must re-click the chatbox to continue typing — the focus is not retained or restored on window re-activation.
Context
harmoniqs.amicode@0.3.0; Darwin 25.6.0 arm64; engine base v1.18.10-amicode.17 (harmoniqs/opencode).
Expected vs actual
- Expected: When returning to the VS Code window after alt-tabbing away, focus remains in (or is restored to) the chat input, allowing the user to continue typing without clicking.
- Actual: Focus is lost; the cursor disappears from the chat input and the user must click back into the chatbox to resume typing.
Diagnostics
- no active run
- macOS 25.6.0 arm64, extension v0.3.0, engine v1.18.10-amicode.17
intake: not-ready — mature per the maturity contract before picking up
suggested_path: A
diagnostics: inline
upstream: n/a
Summary
When typing in the Amicode chat input, switching to another application (e.g. Slack) and then switching back to VS Code, the cursor disappears from the chat input. The user must re-click the chatbox to continue typing — the focus is not retained or restored on window re-activation.
Context
harmoniqs.amicode@0.3.0; Darwin 25.6.0 arm64; engine base v1.18.10-amicode.17 (harmoniqs/opencode).
Expected vs actual
Diagnostics
intake: not-ready — mature per the maturity contract before picking up
suggested_path: A
diagnostics: inline
upstream: n/a