Personal Runtime Configuration Files
Manage personal runtime CLI configuration files in Mopheus.
Personal runtime configuration templates are grouped by CLI. A group can contain several files. For example, the mes-cli group contains ~/.mes/config.yaml and the sensitive ~/.mes/token.env file. Templates are starter file lists; additional files can be added under a group's server-allowed path prefix.
The server controls each group's path prefix. Uploads use the selected group's prefix and a controlled relative path; a local absolute path is never stored as the runtime path.
Supported CLI Configurations
These are the current built-in templates and default file paths. ~ means the home directory of the runtime user.
| CLI / template | Default files | Notes |
|---|---|---|
codex | ~/.codex/config.toml | Codex configuration |
~/.codex/auth.json | Sensitive file | |
mes-cli | ~/.mes/config.yaml | Mes CLI configuration |
~/.mes/token.env | Sensitive file | |
wecom-cli | ~/.config/wecom/.encryption_key | Sensitive credential material; see WeCom integration |
~/.config/wecom/credentials.enc | Sensitive credential material | |
lark-cli | ~/.lark-cli/config.json | App configuration; does not contain user login credentials. See Feishu integration for platform storage details |
lark-cli-data | Keychain data under ~/.local/share/lark-cli/ | Linux file-based keychain only; all files in the directory are sensitive. See Feishu integration for transfer details |
claude | ~/.claude/settings.json | Claude configuration |
kimi-code | ~/.kimi-code/config.toml | Kimi Code configuration |
opencode | ~/.config/opencode/opencode.json | OpenCode configuration |
mimo-code | ~/.config/mimocode/mimocode.json | Mimo Code configuration |
pi | ~/.pi/agent/settings.json | Pi configuration |
ssh | ~/.ssh/config | SSH client configuration |
For Mopheus channel integration setup, see WeCom integration and DingTalk integration. There is currently no built-in file template for the DingTalk DWS CLI.
CLI
mopheus user config-file templates
mopheus user config-file render --template mes-cli --output-dir ./runtime
mopheus user config-file upload token ./token.env
mopheus user config-file get <id>
mopheus user config-file delete <id>render writes the whole group unless --path selects one declared file. upload keeps a relative subdirectory under the group's prefix and rejects traversal or cross-prefix paths.
Sensitive files are encrypted at rest and hidden in normal API and CLI reads. The mes-cli token file uses mode 0600.
Web UI
In User Settings → Runtime configuration files, hover or focus a directory and activate its + action to create a file draft under that directory. The draft inherits the directory's CLI metadata when available. The server repeats all path and workspace checks before saving.