AI Agent Hub
Back to plugins
⚙️

cortex-harness-open

Workflow Updated 2026.09.09

Run the following command in DeepSeek Harness:

dsh plugin install mobfish-ai/cortex-harness-open

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install mobfish-ai/cortex-harness-open in DeepSeek Harness to install this plugin; the source repository is https://github.com/mobfish-ai/cortex-harness-open.

About this plugin

Many teams already run a CORTEX task-pool server in production yet lack a secure command channel from the DSH Web host side. cortex-harness-open closes that gap by publicly exporting the CORTEX Harness protocol command surface as an installable plugin. It injects a /cortex command into DSH Web so operators can trigger local CORTEX workflows directly from the browser, while guaranteeing that the CORTEX token is never carried in browser input.

The plugin's core responsibility is authenticated loopback request forwarding on the host side. All sensitive credentials stay within the local server environment; browser input carries only command intent. Meanwhile, lease management, replay control, receipt verification, and final completion decisions remain authoritative on the CORTEX kernel side, ensuring the workflow engine's security model is never compromised by a thin bridge layer.

This plugin is best suited for developers and platform operations teams integrating the CORTEX protocol into their DSH Web workflows. The repository exports only the allowlisted plugin package and contains no credentials, local databases, or internal runtime state, making it safe to use as a public reference for integration and audit.

Use Cases

  • Trigger local CORTEX task-pool workflows from the DSH Web browser without carrying any token in browser input
  • Add a /cortex host-side command surface to an existing CORTEX deployment without building a custom bridge service
  • Standardize workflow trigger paths in multi-user environments while keeping leases and receipts authoritative on the CORTEX kernel side

Best For

  • Developers integrating the CORTEX protocol into DSH Web workflows
  • Platform operations teams managing local CORTEX task-pool servers
  • Integrators who need a publicly auditable protocol reference without internal runtime state