dsh-relay

Overview Schema Source Related Servers Discussions Admin

Dispatch a Harness run

start_run

Destructive

Create or reuse a Harness session with a chosen model, agent preset, and permissions, then submit a path-based review or implementation task. Returns a stable session link to monitor until completion.

Instructions

Create or reuse a native Harness session, select provider/model/reasoning, agent preset, and native permission preset, then submit the first task and return a stable session link. Task parameters are path-reference-only: provide the authorized workspace, reviewTargets, contextReadScope, excludedPaths, writeScope, and acceptance criteria. reviewTargets identify what to assess; they are not a read whitelist. contextReadScope declares where Harness may search and read supporting implementation, tests, configuration, and architecture material. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. These fields are task instructions, not enforced per-path filesystem isolation. The selected Harness model may send content it reads to its configured model provider even though Relay itself uses a loopback address. Sharing webUrl is not completion: keep wait_run until a terminal status, then consume assistantText.

Input Schema

TableJSON Schema

Name	Required	Description
`task`	No	Task parameters are path-reference-only: provide the authorized workspace, reviewTargets, contextReadScope, excludedPaths, writeScope, and acceptance criteria. reviewTargets identify what to assess; they are not a read whitelist. contextReadScope declares where Harness may search and read supporting implementation, tests, configuration, and architecture material. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. These fields are task instructions, not enforced per-path filesystem isolation. The selected Harness model may send content it reads to its configured model provider even though Relay itself uses a loopback address.
`model`	No
`content`	No	Task parameters are path-reference-only: provide the authorized workspace, reviewTargets, contextReadScope, excludedPaths, writeScope, and acceptance criteria. reviewTargets identify what to assess; they are not a read whitelist. contextReadScope declares where Harness may search and read supporting implementation, tests, configuration, and architecture material. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. These fields are task instructions, not enforced per-path filesystem isolation. The selected Harness model may send content it reads to its configured model provider even though Relay itself uses a loopback address.
`provider`	No
`sessionId`	No
`workspace`	Yes	Authorized absolute Harness workspace root; Harness reads named in-scope files from here.
`writeScope`	No	Paths Harness may modify. Must be empty for read-only runs; this is an instruction declaration in addition to native permissions.
`agentPreset`	No
`openBrowser`	No	Keep false unless the user explicitly asks to open the Harness page in the OS browser.
`sessionMode`	No
`excludedPaths`	No	Paths excluded from contextual reading. This is an instruction declaration, not filesystem enforcement.
`reviewTargets`	No	Subjects to assess. This is not a read whitelist; supply together with contextReadScope.
`idempotencyKey`	No
`reasoningEffort`	No
`contextReadScope`	No	Workspace paths Harness may search and read for evidence. Use only the targets when the user explicitly requests a target-only review.
`permissionPreset`	No
`authorizationBasis`	No	Truthful evidence that the user explicitly selected Harness to inspect this workspace. Set only when the current conversation contains that instruction. This records evidence and does not expand permissions or guarantee approval.
`confirmedDangerousPermission`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.2.13Sep 10, 2026

addedInput schema / properties / authorizationBasis

Added value: +{
+  "const": "explicit-user-request",
+  "description": "Truthful evidence that the user explicitly selected Harness to inspect this workspace. Set only when the current conversation contains that instruction. This records evidence and does not expand permissions or guarantee approval.",
+  "type": "string"
+}

changedInput schema / properties / content / description

Previous value: -"Task parameters are path-reference-only: provide the authorized workspace, file or directory locations, scope, and acceptance criteria. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. This rule is identical for read-only and write-capable permissions."New value: +"Task parameters are path-reference-only: provide the authorized workspace, reviewTargets, contextReadScope, excludedPaths, writeScope, and acceptance criteria. reviewTargets identify what to assess; they are not a read whitelist. contextReadScope declares where Harness may search and read supporting implementation, tests, configuration, and architecture material. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. These fields are task instructions, not enforced per-path filesystem isolation. The selected Harness model may send content it reads to its configured model provider even though Relay itself uses a loopback address."

changedInput schema / properties / content / items / oneOf

Previous value: -[
-  {
-    "properties": {
-      "text": {
-        "description": "Task parameters are path-reference-only: provide the authorized workspace, file or directory locations, scope, and acceptance criteria. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. This rule is identical for read-only and write-capable permissions.",
-        "maxLength": 100000,
-        "type": "string"
-      },
-      "type": {
-        "const": "text",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "text"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "data": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "mediaType": {
-        "enum": [
-          "image/png",
-          "image/jpeg",
-          "image/webp",
-          "image/gif"
-        ],
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "type": {
-        "const": "image",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "mediaType",
-      "data"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "text": {
+        "description": "Task parameters are path-reference-only: provide the authorized workspace, reviewTargets, contextReadScope, excludedPaths, writeScope, and acceptance criteria. reviewTargets identify what to assess; they are not a read whitelist. contextReadScope declares where Harness may search and read supporting implementation, tests, configuration, and architecture material. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. These fields are task instructions, not enforced per-path filesystem isolation. The selected Harness model may send content it reads to its configured model provider even though Relay itself uses a loopback address.",
+        "maxLength": 100000,
+        "type": "string"
+      },
+      "type": {
+        "const": "text",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "text"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "data": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "mediaType": {
+        "enum": [
+          "image/png",
+          "image/jpeg",
+          "image/webp",
+          "image/gif"
+        ],
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "type": {
+        "const": "image",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "mediaType",
+      "data"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / contextReadScope

Added value: +{
+  "description": "Workspace paths Harness may search and read for evidence. Use only the targets when the user explicitly requests a target-only review.",
+  "items": {
+    "description": "Workspace-relative path, or an absolute path contained by the authorized workspace.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / excludedPaths

Added value: +{
+  "description": "Paths excluded from contextual reading. This is an instruction declaration, not filesystem enforcement.",
+  "items": {
+    "description": "Workspace-relative path, or an absolute path contained by the authorized workspace.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / openBrowser / description

Added value: +"Keep false unless the user explicitly asks to open the Harness page in the OS browser."

addedInput schema / properties / reviewTargets

Added value: +{
+  "description": "Subjects to assess. This is not a read whitelist; supply together with contextReadScope.",
+  "items": {
+    "description": "Workspace-relative path, or an absolute path contained by the authorized workspace.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}

changedInput schema / properties / task / description

Previous value: -"Task parameters are path-reference-only: provide the authorized workspace, file or directory locations, scope, and acceptance criteria. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. This rule is identical for read-only and write-capable permissions."New value: +"Task parameters are path-reference-only: provide the authorized workspace, reviewTargets, contextReadScope, excludedPaths, writeScope, and acceptance criteria. reviewTargets identify what to assess; they are not a read whitelist. contextReadScope declares where Harness may search and read supporting implementation, tests, configuration, and architecture material. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. These fields are task instructions, not enforced per-path filesystem isolation. The selected Harness model may send content it reads to its configured model provider even though Relay itself uses a loopback address."

addedInput schema / properties / writeScope

Added value: +{
+  "description": "Paths Harness may modify. Must be empty for read-only runs; this is an instruction declaration in addition to native permissions.",
+  "items": {
+    "description": "Workspace-relative path, or an absolute path contained by the authorized workspace.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "array"
+}

Changed4 schema fields changedv0.2.9Sep 1, 2026

addedInput schema / properties / content / description

Added value: +"Task parameters are path-reference-only: provide the authorized workspace, file or directory locations, scope, and acceptance criteria. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. This rule is identical for read-only and write-capable permissions."

changedInput schema / properties / content / items / oneOf

Previous value: -[
-  {
-    "properties": {
-      "text": {
-        "maxLength": 100000,
-        "type": "string"
-      },
-      "type": {
-        "const": "text",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "text"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "data": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "mediaType": {
-        "enum": [
-          "image/png",
-          "image/jpeg",
-          "image/webp",
-          "image/gif"
-        ],
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "type": {
-        "const": "image",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "mediaType",
-      "data"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "text": {
+        "description": "Task parameters are path-reference-only: provide the authorized workspace, file or directory locations, scope, and acceptance criteria. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. This rule is identical for read-only and write-capable permissions.",
+        "maxLength": 100000,
+        "type": "string"
+      },
+      "type": {
+        "const": "text",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "text"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "data": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "mediaType": {
+        "enum": [
+          "image/png",
+          "image/jpeg",
+          "image/webp",
+          "image/gif"
+        ],
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "type": {
+        "const": "image",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "mediaType",
+      "data"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / task / description

Added value: +"Task parameters are path-reference-only: provide the authorized workspace, file or directory locations, scope, and acceptance criteria. Never embed source text, diffs, file dumps, encoded source, or repository archives. Harness reads named files from the authorized workspace itself. This rule is identical for read-only and write-capable permissions."

addedInput schema / properties / workspace / description

Added value: +"Authorized absolute Harness workspace root; Harness reads named in-scope files from here."

First observedv0.2.6Aug 30, 2026

TDQS

A4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses consequential behaviors: task fields are instructions not filesystem enforcement, the selected model may send read content to its provider despite Relay's loopback, and webUrl sharing does not mean completion. It also clarifies that sessions can be created or reused, matching the destructiveHint while adding privacy-relevant detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The primary action is front-loaded and each sentence carries a distinct safety or lifecycle instruction; no filler. It is long, but the density is justified by the tool's destructive/open-world nature and the need to prevent source embedding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description explains the output at a high level (stable session link), tells the caller to continue with wait_run, and covers the main behavioral caveats. It does not spell out return shape or the meaning of some parameters, but it is largely sufficient for a complex, 18-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage around 50%, the description adds real semantics for the key task parameters: reviewTargets is not a read whitelist, contextReadScope declares where Harness may search, and writeScope/excludedPaths are instruction declarations rather than enforcement. It leaves some parameters (provider, model, reasoningEffort, idempotencyKey, confirmedDangerousPermission) without richer meaning, so it is strong but not exhaustive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly names the operation: create or reuse a native Harness session, select provider/model/reasoning and presets, submit the first task, and return a stable session link. This identifies the resource and action well, but it never contrasts with the sibling start_review, so an agent must infer the boundary between them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives strong operational guidance (path-reference-only task text, avoid embedding source, keep wait_run until terminal status), which clarifies how to invoke it. However, it does not state when to choose start_run over start_review or other siblings, leaving selection partly implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Dispatch a Harness run

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools