Skip to main content
Glama
tonytanglab

dsh-relay

by tonytanglab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Continue a Harness session

reply_run
Destructive

Submit a new queued turn to a completed run session, optionally selecting a different model, and track it as a new run.

Instructions

Submit a new queued turn to the completed run session, optionally selecting a different model, and track it as a new run. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskNoTask 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.
modelNo
runIdYes
contentNoTask 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.
providerNo
writeScopeNoPaths Harness may modify. Must be empty for read-only runs; this is an instruction declaration in addition to native permissions.
openBrowserNoKeep false unless the user explicitly asks to open the Harness page in the OS browser.
excludedPathsNoPaths excluded from contextual reading. This is an instruction declaration, not filesystem enforcement.
reviewTargetsNoSubjects to assess. This is not a read whitelist; supply together with contextReadScope.
idempotencyKeyNo
reasoningEffortNo
contextReadScopeNoWorkspace paths Harness may search and read for evidence. Use only the targets when the user explicitly requests a target-only review.
permissionPresetNo
authorizationBasisNoTruthful evidence that the user explicitly selected Harness or this named Harness model to inspect the stated workspace scope. The current explicit request is sufficient authorization for that selected provider to process in-scope reads; do not ask the user to repeat authorization solely because provider processing is external. This field does not broaden the workspace, scope, permissions, destination, or allowed external actions.
confirmedDangerousPermissionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.17
    • changedInput schema / properties / authorizationBasis / description
      Previous value: -"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."New value: +"Truthful evidence that the user explicitly selected Harness or this named Harness model to inspect the stated workspace scope. The current explicit request is sufficient authorization for that selected provider to process in-scope reads; do not ask the user to repeat authorization solely because provider processing is external. This field does not broaden the workspace, scope, permissions, destination, or allowed external actions."
  2. Changed9 schema fields changedv0.2.13
    • 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"
+}
  3. Changed3 schema fields changedv0.2.9
    • 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."
  4. First observedv0.2.6

TDQS

B3.1/5.0
Behavior4/5

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

The description discloses important behavioral traits beyond annotations: it warns that the selected Harness model may send content to its external provider, and it explicitly states that path fields are instructions not filesystem enforcement. These add significant context that the annotations (openWorldHint, destructiveHint) do not fully specify.

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

Conciseness2/5

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

The description is verbose and repeats the same long paragraph verbatim in the schema for task, content.text, and the content array. This duplication is wasteful and hinders quick scanning, even though the main description is front-loaded with the action.

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

Completeness2/5

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

With 15 parameters, no output schema, and a complex operational context, the description covers only a subset (mostly path and data-handling rules). It omits guidance on model selection, permission presets, idempotency, and dangerous confirmation, leaving the agent with significant gaps for correct invocation.

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

Parameters3/5

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

Schema coverage is 53%, and the description compensates for key path-based parameters (reviewTargets, contextReadScope, excludedPaths, writeScope) by explaining their semantics and constraints. However, it does not address other parameters like model, provider, reasoningEffort, permissionPreset, or idempotencyKey, so it is only partially compensating.

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 states a specific action: 'Submit a new queued turn to the completed run session' and clarifies it tracks as a new run, which distinguishes it from starting fresh runs. However, the phrase 'completed run session' is slightly ambiguous and does not explicitly name sibling tools like start_run or steer_run, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

The description implies usage context (continuing a completed run) but does not explicitly state when to use this tool versus alternatives such as start_run or steer_run, nor does it mention any exclusions or prerequisites. The focus is on parameter semantics rather than routing the agent to the correct tool.

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

Deploy Server

Other Tools