Platform notes

Termux and desktop targets

The adapter registry includes environment gates. Termux-only behavior can be skipped on desktop, while desktop-oriented targets can be skipped in Termux. Confirm the current environment and then inspect the target entry in the integration catalogue before changing paths manually.

MiXplorer cannot update its configuration

MiXplorer requires the adapter’s expected privileged access. A generated source alone does not grant permission to replace its live configuration. Resolve the privilege or root requirement first; retrying selection without it will not make the destination writable.

tman serve --open does not open a browser

The server starts locally and asks the operating system to open its URL. If the opener is unavailable, use the URL printed by the server in a browser yourself. The server has no documented bind-host guarantee, so do not treat it as a remote-access service.

Special adapter handoffs

Some targets intentionally use a non-obvious handoff:

• Eza requires conversion from generated YAML to EZA_COLORS.
• Neovim reads a generated pointer rather than a direct live-theme replacement.
• VS Code receives a generated package only.
• WezTerm writes an additional Lua pointer.
• Ghostty, OpenCode, Oh My Pi, Pi, Kitty, and Termux use target-specific reload behavior.

Inspect the adapter’s generated source and configured destination before retrying a failed apply.