OneCode 0.8.9

OneCode 0.8.9

Explicit paths in your message grant access before the task is prepared.

• Put an existing native file/folder path on its own line, followed by the task. Quoted paths in direct Read/Scan/Open-style requests and the existing explicit approval declarations are also supported. Paths with spaces can be quoted or placed on their own line.
• Use the same durable root owner as folder approval. Folder paths cover their contents. A file path grants only that exact file, without approving its parent or siblings or becoming a default command workspace.
• Apply grants from the trusted Desktop submission or authenticated Remote user's text before message preparation. Attached document contents, generated plan stages, tool/model output, fenced code, blockquotes, negated directives, relative paths and unsupported network paths cannot supply this approval.
• Retain existing read/write capability settings, canonical path and link checks, restart persistence and current worker access. Duplicate submission IDs do not restore a grant removed after the original submission. A newly approved containing folder retains earlier virtual aliases.
• Open recorded ChatGPT PDF/file links from Remote in their exact ChatGPT chat on the phone, where ChatGPT's native download control remains available. The destination is verified against the saved session and assistant message. A sandbox: address is not a public download URL; this release opens the native chat rather than transferring provider files through OneCode.
• Keep normal external links in a separate browser tab, provide a second tap when mobile Safari blocks a new window, show file-link errors, and hide leaked inline provider reference markers while preserving literal code examples.

The release includes full Windows x64 and Linux x64 installations plus compatible cumulative capsules over the verified Windows 0.5.9 and Linux 0.8.2 bases. Bridge protocol 22, recorder 127 and immutable native components are unchanged. See verification scope.