Skip to content

[Feature]: oh-my-opencode should NOT write to its config file #1744

@jgbailey-well

Description

@jgbailey-well

Prerequisites

  • I will write this issue in English (see our Language Policy)
  • I have searched existing issues and discussions to avoid duplicates
  • This feature request is specific to oh-my-opencode (not OpenCode core)
  • I have read the documentation or asked an AI coding agent with this project's GitHub URL loaded and couldn't find the answer

Problem Description

oh-my-opencode (and opencode) both want to write to their own config file.

I like to manage my config files with version control in a seperate directory (I use home-manager w/ nix). My config files are all symbolic links to read-only files under /nix/store. That means oh-my-opencode isn't able to write to those files.

Proposed Solution

Please move state management to somewhere that's supposed to be ephermeal, like .local/state or similar.

Alternatives Considered

I don't have to use nix for these files but I'd rather not do that; its nice to be able to re-create my whole home directory setup wtih one command.

Doctor Output (Optional)

Additional Context

No response

Feature Type

New Agent

Contribution

  • I'm willing to submit a PR for this feature
  • I can help with testing
  • I can help with documentation

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions