Opencode does not follow XDG Base Directory Specification (state files)

[aichingm]

Description

Opencode creates state files (log, session data and alike) in XDG_DATA_HOME which does not follow the specification.

From the specification:

The $XDG_STATE_HOME contains state data that should persist between (application) restarts, but that is not important or portable enough to the user that it should be stored in $XDG_DATA_HOME. It may contain:

• actions history (logs, history, recently used files, …)

• current state of the application that can be reused on a restart (view, layout, open files, undo history, …)

Logs, history and session data should be stored in XDG_STATE_HOME. XDG_DATA_HOME is more akin to the user specific equivalent of /usr/share/ not a place to store runtime data.

Three concrete problems with the current implementation:

• Running opencode in a container along other tools does not allow for a singe state related mapping opencode needs an exception to the general rule.
• Deleting $XDG_STATE_HOME should put all applications in a fresh "unused" state. Which does not happen in opencode's case.
• It makes it totally unclear which files a user would need to backup, migrate or sync to a new machine.

Plugins

No response

OpenCode version

1.2.27

Steps to reproduce

1. Start opencode
2. Execute some prompts

Screenshot and/or share link

No response

Operating System

Linux (alpine)

Terminal

any

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Reorganize and document dirs for config, agents, auth credentials, sessions #4170: Discusses the same XDG directory misuse — data vs state vs config dirs, and what should be stored where
• Running opencode locally and in docker while sharing config corrupts the database #14194: Describes container sharing issues caused by opencode mixing state into XDG_DATA_HOME, which is one of the exact problems raised here
• [FEATURE]: add environment variables for portable mode and profile isolation #8968: Requests configurable OPENCODE_CACHE_DIR / OPENCODE_LOG_DIR for isolation, motivated by similar concerns

Please review these issues to see if they already cover your report or if yours adds a distinct enough angle to remain open.

[github-actions]

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.