@omdsh-plugins/omdsh-remdev

Configuration

One settings namespace, omdsh-remdev. The servers and mounts live in a hidden store written by this plugin's own dialog — a list of objects the generic form refuses to draw, holding credentials no form should render. It is declared role('secret') as well as hidden, and the two do different jobs: hidden keeps it out of a form, the role keeps it off the wire. Everything else is a plain field the panel draws:

Field	Default	What it decides
dshVersion	latest	which harness release to install on a server
nodeVersion	v22.20.0	which Node to install on a server whose own is older than 22
pnpmVersion	11.7.0	which pnpm to install on a server that has none; the harness installs profile plugins with it
allowUpload	true	whether a server with no internet may be set up by uploading from here
syncIntervalSeconds	60	how often conversations are copied down; 0 switches the background copy off
codeProfile	dsh-code	the profile name a Code terminal boots on a server
codeBundle	@omdsh-plugins/omdsh-tui-app	the terminal application that profile composes; space-separated for an application that ships as more than one package
tuiRepo	https://github.com/omdsh-plugins/omdsh-tui.git	the git repository the omdsh-tui terminal is installed from; point it at a mirror when servers cannot reach github.com
tuiProfile	omdsh-tui	the profile the omdsh-tui terminal installs into; the remote Code column boots it
forwardEnv	DEEPSEEK_API_KEY, DEEPSEEK_BASE_URL	environment copied from this machine onto a remote agent

Every field is applies: 'live': an edit is adopted as it commits, and the next dial, provisioning run, terminal or sync uses it. Nothing here asks for a restart. The versions are read when a server is set up, so changing one re-provisions the next server rather than the ones already installed.