dsh-keep-awake

Keep-awake plugin for the DeepSeek Harness (UI follows the DSH global language)

Blocks OS sleep while any agent / subagent / background job runs · auto-release after a configurable grace period once idle · manual hold · optional display-on · optional: stay awake while scheduled tasks are pending · Windows / macOS / Linux · persisted settings · multilingual web settings page

English | 中文

Features

How it works

Polls every 5 seconds, with instant re-scan on events (agent/status, subagent/start|end, job set changes):

• Running agents: agents with status === 'running' in agents.list() (covers the main agent, subagents, and workflow children)
• Background jobs: running/stopping jobs from jobs.list() (unowned) plus jobs.list(sessionId) for every live session (covers run_in_background commands and background subagent tasks); job events come from jobs.events.subscribe({ owners: 'all' }, ...)
• Scheduled tasks (optional, off by default): with scheduleHold enabled, each rescan reads the Host schedule service's catalog() and counts tasks with status === 'active'; any pending task keeps the lock held. schedule/changed fires on the schedule service's own context and cordis events only bubble upward, so this plugin cannot subscribe — detection rides the 5 s poll: a newly created task arms the hold within one poll, deletions/pauses release through the grace period within one poll

When activity is detected, a platform helper process is started via the subprocess service (tree-level termination — the sleep flags release as soon as the process exits):

Settings

Changes made on the settings page are written through DSH's settings service into the profile's plugin patch (this plugin's own Loader row) and survive a restart:

All of these fields are marked volatile in Config, so a change applies live without remounting the plugin. Every write carries a revision for optimistic concurrency: if two settings pages write at once, the later one gets a 409 and reloads the live values. On a host without a settings service (older DSH) the page still works, but changes last only until DSH restarts and the UI says so.

Compatibility

dsh.compatibility.dshReleases declares the releases actually verified: 0.2.1-rc.2 and 0.2.1-rc.4. scheduleHold relies on the Host's schedule service (bundled with every 0.2-line host); on a host without it the option degrades to a no-op and the settings page says so.

Localization

The UI uses the framework locale service (this plugin's locale namespace is keep-awake, zh/en dictionaries): when no language is explicitly set, the browser/system language is used; switching in DSH's language settings takes effect instantly (both the settings page body and the sidebar label follow).

HTTP routes (loopback)

• GET /dsh-keep-awake/state — current state (activity counts, schedule-hold view (pendingSchedules / nextDueAt / scheduleService), helper process, config, plus revision and persistent)
• PUT /dsh-keep-awake/config — update config, body { "section": {...}, "revision": <optional> }; a stale revision returns 409 with the live state, an unknown key returns 400

Install

# Inside the profile directory (e.g. ~/.dsh/profiles/web)
pnpm add "dsh-keep-awake@<source>"   # npm / github:bearice/dsh-keep-awake / link:<local path>
# and add "dsh-keep-awake" to dsh.profile.bundles in package.json
pnpm install
# restart the profile

Development

• For local development, mount the package into the profile via link: (see Install above) and use node --check lib/*.js for syntax checks
• Layout: lib/index.js (Host), lib/client.js (web settings page), cordis.patch.yml (mount line)