[Bug]: fail to create with opencode in desktop app

[Jarekkkkk]

Preflight

• I searched existing issues and this isn't a duplicate
• I'm on the latest version (or I've noted my version below)

What happened?

getting The terminal session ended (exit code 1) error in created terminal when try to create with opencode cli

i also checked the config files in ~/.ok/mcp-status.json, and it doesn't exist. should i manually config as well with desktop app usage

Steps to reproduce

1. open openknowledge desktop app
2. initialize the project
3. input my prompt in the composer

Platform

macOS (Apple Silicon)

How did you install Open Knowledge?

Desktop app (DMG)

Version

0.19.2

Logs, errors, or screenshots

[amikofalvy]

Thanks for the report, and sorry for the trouble!

One clarification that should help us narrow this down quickly: "The terminal session ended (exit code 1)" is the docked terminal's login shell failing to start. It's separate from opencode. When you "Create with OpenCode," OK opens a terminal running your login shell ($SHELL -l -i) and then types opencode --prompt '...' into it. That message fires when the shell exits, independently of opencode, so a missing or misconfigured opencode would actually show a different message ("OpenCode isn't installed or on your PATH"), not this one.

(And ~/.ok/mcp-status.json not existing is expected if you haven't run File > Configure AI tool integrations… from the menu bar yet. That dialog wires the OK MCP server into your editors, and it's unrelated to this terminal error.)

To tell whether this is on our side or in your shell setup, could you share two things?

1. The desktop log from the day it happened: ~/.ok/logs/desktop.<date>.log (e.g. desktop.2026-06-27.log). Attach it here, or paste any lines mentioning terminal, spawn-error, pty, or cli-preflight.

2. Run this in Terminal.app and paste the output:

echo $SHELL && ls -l "$SHELL" && "$SHELL" -l -i

• If that fails, or $SHELL points to something that no longer exists, your login shell is misconfigured (commonly a shell installed via Homebrew that was later removed). That would be the root cause, and we can point you at the fix.
• If it works fine there but the in-app terminal still dies, that points back to us, and the log will show where.

Two quick extras that help triage:

• Does the same thing happen if you choose Claude or Codex instead of OpenCode? (Tells us whether it's shell-level or opencode-specific.)
• Is the app running from /Applications (not the mounted DMG)?

Thanks!

[Jarekkkkk]

Hi @amikofalvy, thank you so much for the detailed breakdown!

It turns out this was indeed a shell/macOS configuration issue. Because I use the fish shell, the problem boiled down to how macOS GUI applications inherit the $SHELL environment variable. Everything is working perfectly now after correcting my configuration. really appreciate your help in tracking this down

As a heavy OpenCode user, I also have a quick feature request: it would be amazing if the in-app terminal supported scrolling. When running opencode --prompt "...", it launches its own TUI/GUI, and being able to scroll back through the terminal to check past chat conversations would be incredibly helpful.

This is a fantastic product and exactly what I’ve been looking for. Keep up the great work ❤️

[amikofalvy]

Glad you were able to resolve the shell config issue. We're so excited that you are enjoying using our tool. Please keep providing us with feedback, we benefit greatly from engaging with real users.

I'll look into your other request to add the scroll capture to the in-app terminal and get back to you.

Creating a new issue to track that request separately.