Sync local skills, hooks, and settings to remote SSH environments

What variant of Codex are you using?

Codex Desktop App on Windows, connected to remote Linux machines through SSH.

What feature would you like to see?

Please add an opt-in way to synchronize a user's Codex configuration from the local Codex Desktop host to a connected remote SSH environment.

When I open a repository on a remote machine, Codex runs using the remote machine's own home directory and configuration. My local reusable skills, hooks, agents, rules, and preferences are therefore unavailable unless I manually copy and maintain them on every remote host.

A useful design would be a per-connection option such as Sync Codex configuration to this host, with selectable categories including:

• User skills, such as ~/.agents/skills
• Hooks and their referenced scripts
• User-level AGENTS.md
• Custom agents and rules
• Selected portable values from config.toml
• Potentially other user-installed Codex extensions or plugins

The feature should support both a one-time sync and optional automatic synchronization when the local configuration changes. A preview or diff before overwriting remote files would also help prevent accidental configuration loss.

Sensitive or machine-specific data should not be synchronized by default. In particular, authentication tokens, auth.json, conversation/session history, logs, caches, absolute local paths, and platform-specific settings should remain local. Remote-side authentication and explicitly configured remote overrides should be preserved.

Cross-platform handling is important for a Windows-to-Linux workflow. Hook commands and paths may need separate Windows and Unix forms, or the sync UI should identify entries that cannot be transferred safely.

Additional information

Project-specific skills and configuration can be committed inside each repository, but many skills and hooks are personal and reusable across multiple projects. Putting every personal tool into every repository is undesirable, while manually copying dotfiles to each remote machine creates configuration drift.

This feature would make remote SSH projects behave more like the user's normal Codex environment without silently transferring secrets or assuming that local and remote operating systems are identical.