DSH Proactive Heartbeat & Autonomous Daemon

@john-walks-slow/dsh-proactive · v1.4.0

A production-grade asynchronous heartbeat and persistent daemon runtime for DeepSeek Harness agents. Features declarative cron scheduling, session state persistence, and event-driven wakeups for autonomous background workflows.

ProactiveDaemonCronMicrokernel
GitHub Stars
19 K+
+12.4% this month
Monthly Downloads
90 K+
Monthly registry pulls
Reach Score
97.4/ 100
Top Tier Ecosystem
Runtime
Cordis v3+
Node 18+ / Bun / Deno

Installation & Integration

CLI one-click launch, package managers, and Cordis integration

bash
manager:
$ pnpm add @john-walks-slow/dsh-proactive

Architecture

DSH Proactive equips DeepSeek Harness agents with an asynchronous event loop and resilient daemon supervisor. Traditional LLM workflows remain strictly reactive, failing to address continuous monitoring or automated infrastructure maintenance. By injecting persistent timer interrupts into the Cordis microkernel, agents can autonomously register cron expressions and asynchronous callbacks. Dormant sessions serialize context state into disk storage during idle phases and rehydrate seamlessly upon trigger delivery, optimizing token expenditure while enabling true autonomous background operation.

Architectural Principles & Constraints

01
Strict Type Isolation

Guaranteed by TypeScript compile-time contracts, inter-plugin event bus calls enjoy zero-drift safety.

02
Sub-Millisecond Hot Reload

Supports dynamic runtime mounting and graceful unloading without restarting the primary host process.

03
Deterministic State Machine

Embeds multi-phase execution lifecycle guards, preventing context loss during long-horizon reasoning.

04
Zero Native Build Dependencies

Designed for lightweight cross-platform environments, booting instantly across Node.js, Bun, and Deno.

Core Features

01
Declarative Cron Syntax: Standard crontab registration with second-level precision and live cancellation
02
Zero-Waste Session Sleep: Persists dormant stacks to storage, eliminating idle token burn
03
Quiet Hours & Rate Limiter: Enforces daily dispatch thresholds and quiet-hour windows to curb alerts
04
Distributed Lock Safeguard: Built-in Redis and file locks prevent duplicate execution across clusters

Core Workflow

01

Schedule Registration

Agent registers cron expressions and wakeup intent via strongly typed schema tools.

02

Session Hibernation

Cordis interceptor serializes stack frames to lightweight persistence, releasing runtime locks.

03

Timer Interrupt Delivery

Host daemon identifies target interval and broadcasts execution wakeup signal to the bus.

04

Context Rehydration & Inference

Restores session context and environment variables, advancing downstream autonomous actions.

Configuration Parameters Reference (YAML / JSON)

ParameterTypeDefaultDescription
minIdleSecondsnumber60Minimum idle duration before state hibernation
quietHoursStartstring22:00Quiet window start timestamp (HH:mm)
dailyQuotanumber50Global maximum limit on autonomous wakeups per day

Use Cases

Enterprise Production Agent

Relies on microkernel lifecycle guards and fault-tolerant state machines for continuous reliability.

SWE-bench Benchmark Evaluation

Native integration with SWE-bench workflows, automatically capturing diffs and verification metrics.

Autonomous Code Refactoring

Separates reasoning from tool actions to independently locate and refactor multi-file codebases.

Cross-Tool Workflow Automation

Safely orchestrates events across sandboxes to seamlessly link enterprise developer tooling.

Best Practices

01
Sandbox Permission Guard

Strictly isolate sub-process calls and network scope; deploy within Docker containers in production.

02
Exponential Backoff Retries

Configure adaptive exponential retries with strict timeouts to mitigate upstream model rate limits.

03
Session State Checkpointing

Persist state machine snapshots to survive hardware interruptions and resume instantly without loss.

04
Full Trajectory Audit Logs

Enable full trace logging, aggregating reasoning thought streams and tool I/O into your observability hub.

FAQ

Q1:How to handle timeouts in long-running autonomous tasks?

Increase the timeout parameter inside your YAML configuration and dispatch periodic heartbeat signals across the Cordis event bus. For long-running tool execution and model reasoning, configure persistent session snapshotting so suspended tasks can safely resume their exact context after interruptions, preventing the kernel from recycling active agent sessions prematurely.

Q2:How to capture and stream the model reasoning thought process?

The harness runtime natively provides end-to-end streaming hooks while its state machine automatically intercepts and strips <think> reasoning tags from model responses. Subscribe directly to the onThink event listener to consume live reasoning token streams in real-time, delivering typewriter animation to the user interface while persisting full trajectories for audit compliance.

Q3:How to resolve dependency conflicts across multiple plugins?

Cordis microkernel uses directed acyclic graph topological sorting to dynamically resolve plugin dependencies. When shared services or runtime versions conflict, assign distinct isolated namespaces at the application entrypoint. Leveraging context injection alongside lazy activation ensures dependencies load strictly on-demand when tools are triggered, maintaining system stability and preventing memory bloat.

Q4:How to enforce permissions and sandbox isolation in production?

Combine isolated container sandboxing with fine-grained capability checks to prevent plugins from accessing sensitive files or unauthorized external networks. Enforce explicit runtime system call whitelisting through the microkernel, executing all third-party tool scripts inside isolated ephemeral containers to block arbitrary code execution and eliminate security privilege escalation risks entirely.

Recommended Ecosystem Plugins

Explore related Cordis extensions designed to work synergistically