Automations & SSH runs
Schedule agent runs locally or delegate execution to remote Linux hosts over SSH — credentials stay encrypted.
Local automations
Automations pair saved prompts with a model choice and workspace target. They run in the desktop app's main process with full tool access, triggered by cron schedules (hourly, daily, weekdays, custom) or manually with Run now.
Remote runs over SSH
Remote targets connect to a Linux server and execute deyin run --json -y with a per-run Openference token passed via DEYIN_TOKEN stdin — never stored on the server and never visible in the remote command line or login shell environment.
Security
SSH host credentials (private keys, passphrases, passwords) are encrypted at rest via the OS keychain; host keys are pinned on first connection. Manage hosts under Settings → SSH hosts and automations from the sidebar Automations view. “Keep running in background” keeps the scheduler alive in the tray after windows close.
Cheat sheet
Automations are plain cron schedules bound to a prompt and a workspace. They run with the access level you assign — most teams keep them read-only or ask-level and review output in the morning.
deyin automation list
Fix flaky tests every 30 min deyin-gateway
Nightly deps audit 0 2 * * * skills-pack
Weekly changelog 0 9 * * 1 docs
deyin automation run <id> # fire now
deyin automation pause <id>SSH runs
Remote runs execute on the host over SSH with the same agent binary — results stream back to your fleet view as if the job ran locally. Host keys are verified on first connect and stored in the keychain.
deyin automation add --host build@ci.internal \
--cron "*/15 * * * *" \
--prompt "Rebuild the failing shard and post the log tail"