### System details

amd ryzon 5700 

### What's wrong?

I have been using Omarchy for around six months, and overall I have had a really great experience with it. I really appreciate the work that has gone into making Omarchy such a smooth and productive environment.

However, after upgrading to/using the latest Omarchy v4 version, I have started experiencing a serious configuration-related issue, particularly when using AI coding tools such as Claude Code, OpenCode, and similar CLI-based AI development tools.

Issue Description

The main problem appears to be related to configuration files being automatically modified or reverted in the background.

In some cases, configuration files contain duplicate or conflicting configuration entries. For example, a particular configuration value such as a model or codec version may be defined as latest, but the same key can appear more than once in the configuration file.

When I manually edit the configuration file and remove the duplicate entry or correct the configuration, the change initially appears to work. However, after approximately 2–3 seconds, the configuration is automatically modified again and the previous/duplicate configuration is restored.

Because of this, I am unable to permanently modify the configuration.

Impact on AI Coding Tools

This becomes particularly problematic when using AI coding tools.

The AI tool reads the incorrect or duplicated configuration and can enter a repetitive loop. Instead of continuing with the requested task, it repeatedly encounters the same configuration/state and keeps retrying or executing the same operation.

This makes the AI coding tools practically unusable in certain situations.

The behavior looks roughly like this:

AI coding tool starts normally.
The tool reads its configuration.
A duplicate or conflicting configuration value is detected.
The tool enters a retry/looping behavior.
I manually open the configuration file and fix/remove the duplicate entry.
The configuration initially looks correct.
After approximately 2–3 seconds, something automatically rewrites the configuration file.
The duplicate/previous configuration entry appears again.
The AI tool encounters the same configuration problem and starts looping again.
Another Important Observation

The most confusing part is that I cannot determine what process is rewriting the configuration file.

It does not appear to be a normal manual modification. Even after I remove the duplicate key and save the file, the configuration is automatically reverted shortly afterward.

For example, if a configuration contains something similar to:

codec_version = latest
codec_version = latest

and I remove one of the duplicate entries, the file may initially become:

codec_version = latest

But after a few seconds, the duplicate entry can reappear automatically.

This makes troubleshooting extremely difficult because the configuration cannot be kept in the desired state long enough to determine whether the actual application is functioning correctly.

Expected Behavior

Once I manually modify and save a configuration file, the configuration should remain unchanged unless:

the application itself intentionally modifies it,
a package/update process modifies it,
a system configuration manager regenerates it, or
another explicitly configured service is responsible for managing that file.

If another Omarchy component or background process is intentionally managing the configuration, it would be helpful to know which component is responsible and why it is rewriting the file.

Actual Behavior

The configuration file is automatically modified/reverted within a few seconds after I manually edit it.

This can result in:

duplicate configuration keys,
previously removed configuration values returning,
conflicting settings,
AI coding tools entering repetitive loops,
configuration changes not persisting, and
difficulty identifying the actual source of the problem.
Request

Could someone please help identify what is responsible for automatically regenerating or reverting these configuration files in Omarchy v4?

It would also be helpful to know whether this is a known issue with the latest Omarchy release or with any of the default configuration-management scripts/services.

If there is a specific service, script, package, or watcher responsible for these automatic changes, I would appreciate instructions for identifying it and fixing the underlying issue rather than manually editing the configuration every time.

I really like Omarchy and have been using it for around six months, so I would appreciate any help in diagnosing this. The issue is especially disruptive because it directly affects my AI-assisted development workflow.