Log File Deleted When Multiple IDE Instances Are Attached to OpenCode Server

[taqtiqa-mark]

Description

Environment

• OpenCode v1.0.128 installed via curl script in a containerized setup.
• Server running locally using opencode serve.

Steps to Reproduce

1. Start the OpenCode server with opencode serve.
2. Attach the first IDE instance using opencode attach, which creates a log file.
3. Attach a second IDE instance using opencode attach.
4. Confirm server container instance ID has not changed.

Expected Behavior

Each IDE instance should maintain its own log file, or separate logs should be preserved for concurrent sessions without deletion or overwriting.

Actual Behavior

Upon attaching a new IDE instance, the previous log file is deleted, and a new log file is created with a timestamp corresponding to the most recent attachment. As a result, with multiple (e.g., two) IDE instances open, only one log file exists, reflecting the latest launch time. This leads to loss of logs from earlier instances.

Impact

This behavior hinders debugging and monitoring of multiple concurrent IDE sessions, as historical logs are not retained.

Suggested Resolution

Consider implementing server log file AND per-attach-instance log files (e.g., differentiated by session ID or timestamp) or appending to existing logs instead of overwriting.

OpenCode version

v1.0.128

Operating System

Linux (Debian testing)

Terminal

Alacritty+Zellij

[github-actions]

This issue might be related to:

• When running in serve mode, the log will contain two session IDs. #1649: When running in serve mode, the log will contain two session IDs (related to logging issues in serve mode with multiple sessions)

While not exact duplicates, both issues deal with serve mode logging problems affecting multiple sessions. Feel free to check that issue to see if there's any shared context.

[taqtiqa-mark]

No #1649 is not relevant. Here the whole log file for another running OC client is deleted.

[taqtiqa-mark]

Hmmm, I see the same behavior when i switch to just using the TUI (no opencode serve then opencode attach).
However in the TUI scenario the logs contain much more data - in the serve-attach scenario there was generally only one line in the file.

[taqtiqa-mark]

In the spirit of calling out excellent engineering and design....

I've found that the Pi Coding Agent is more robust and, for me has none of the issues that I've encountered in OC, or has an elegant way to resolve them.... I'm dropping out of OC issues:

• Pi Coding Agent
• Overview
• Example development session