Loving the iOS client, two questions about voice input and Markdown previews

[ramzi-ammar]

Hi,

I installed OpenCode on my VPS to access my AIOS / Second Brain while I am away from my computer.

I am currently on holiday, so being able to use OpenCode from my iPhone is genuinely useful. I think the app is great. The SSH tunnel setup works well and it is exactly the kind of mobile access I was looking for.

I have two questions:

1. I would love to use the voice transcription feature. The settings ask for an AI Builder Space token, but I could not find how a TestFlight user can obtain one. Is this feature currently invite-only? Is there a public onboarding page, pricing, or a trial?

2. In the Files section, I can browse my workspace tree, including my Obsidian vault. But I cannot open or preview my Markdown files. Is there a setting I missed, a limitation of the current TestFlight build, or a planned feature?

Thanks again for building this. It is already making OpenCode much more practical when I am away from my desk.

[grapeot]

Thanks for testing OpenCode Remote and reporting these items.

Voice transcription connects to our AI Builder Space infrastructure. The token currently ships with the AI Builders course, and there is no standalone token purchase or trial available yet. We are tracking demand here if more people are interested.

Opening and previewing Markdown files is supported in current builds. The likely cause is symlinks: OpenCode blocks reading files that resolve outside the workspace root for path escape protection. If the Obsidian vault or a subfolder is symlinked from outside the workspace, it appears in the file tree but cannot be opened. You can verify this on the server host with ls -la <parent-dir> or readlink <vault-path>.

If symlinks are not the cause, please share a few details so we can investigate:

• What happens when tapping a .md file (nothing appears, spinner forever, or error message; screenshot if available)
• App build number from TestFlight
• OpenCode server version (opencode --version)
• Workspace setup (whether the vault is the workspace root, a subdirectory, or an external symlink)
• An example full path of a failing .md file (redacted if needed)