Koda Remote attaches the moment you open it
Opening a live Koda session from the dashboard used to take two confirmations: matching a six-digit code in the browser, then running /remote approve in the terminal. Both are gone.
Reaching your session already required your OpenAdapter credentials — the same ones that authorize every model call Koda makes. A second and third confirmation guarded a door you had already unlocked, and the terminal step in particular defeated the point of remote: it asked you to walk back to the machine you had walked away from. Pick your session, and you are watching it.
Sessions stay end-to-end encrypted between your terminal and your browser; the relay still forwards frames it cannot read. Permission gates are untouched — a dangerous command still stops and waits for you to approve it.
Two fixes ship alongside. Refreshing the page no longer loses the conversation or the model and thinking controls: a long transcript exceeded the relay's frame limit, which quietly killed the connection every time you reattached. And a permission prompt raised while your browser was closed now waits for you instead of expiring unseen — the relay tells Koda when someone is actually watching.
