Ope Oginni authored commit 01a5c69 on June 29, changing packages/opencode/src/cli/cmd/tui.ts and packages/opencode/src/cli/network.ts so the served TUI path carries ServerAuth headers when it connects to an external thread.
The story is a contributor arc under integration pressure: once a terminal UI can be served outside the local process, the transport has to know how the server expects to be trusted.
The public trail
The patch keeps the change small: 28 insertions and 12 deletions wire auth-header construction into the external served TUI network path instead of treating the thread as just another local terminal surface.
That matters because opencode is also moving session information into visible app surfaces. Oginni's nearby desktop metrics commit made stored token and cost totals visible in the desktop session context, another sign that project state is becoming an operator-facing contract.
Public work context
Oginni's public GitHub profile links an opencode fork and a gitterm project described as running opencode anywhere. That context earns one sentence here because the served-TUI patch is about the same public work boundary: terminal agent interfaces leaving a single local shell.
Why this contribution matters
For agent operators, the consequence is not glamour. It is that remote or externally served terminal experiences need explicit connection contracts before they can be trusted as daily tooling.
The conversation to open
The constructive question for opencode is whether served TUI authentication should become visible in user-facing docs or diagnostics. The fairness limit is tight: the evidence proves this public patch and adjacent public opencode work, not Oginni's private motivation or any broad security review.