Skip to content

Commit 0097428

Browse files
docs: fix stale safe-outputs.memory references and document McpOptions.enabled (#327)
* Initial plan * docs: fix stale safe-outputs.memory refs and document MCP enabled field Agent-Logs-Url: https://github.com/githubnext/ado-aw/sessions/3e3de837-466e-4294-958f-f31b3b08f6ef Co-authored-by: jamesadevine <4742697+jamesadevine@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jamesadevine <4742697+jamesadevine@users.noreply.github.com>
1 parent 28c23e8 commit 0097428

3 files changed

Lines changed: 5 additions & 2 deletions

File tree

AGENTS.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -399,7 +399,7 @@ Parameters can be referenced in custom steps using `${{ parameters.paramName }}`
399399

400400
#### Auto-injected `clearMemory` Parameter
401401

402-
When `safe-outputs.memory` is configured, the compiler automatically injects a `clearMemory` boolean parameter (default: `false`) at the beginning of the parameters list. This parameter:
402+
When `tools.cache-memory` is configured, the compiler automatically injects a `clearMemory` boolean parameter (default: `false`) at the beginning of the parameters list. This parameter:
403403

404404
- Is surfaced in the ADO UI when manually queuing a run
405405
- When set to `true`, skips downloading the previous agent memory artifact
@@ -566,7 +566,7 @@ Explicit markings are embedded in these templates that the compiler is allowed t
566566

567567
Should be replaced with the top-level `parameters:` block generated from the `parameters` front matter field. If no parameters are defined (and no auto-injected parameters apply), this marker is replaced with an empty string.
568568

569-
When `safe-outputs.memory` is configured, the compiler auto-injects a `clearMemory` boolean parameter (default: `false`) unless one is already user-defined.
569+
When `tools.cache-memory` is configured, the compiler auto-injects a `clearMemory` boolean parameter (default: `false`) unless one is already user-defined.
570570

571571
Example output:
572572
```yaml
@@ -1648,6 +1648,7 @@ mcp-servers:
16481648
- `headers:` - HTTP headers to include in requests (e.g., `Authorization`, `X-MCP-Toolsets`)
16491649

16501650
**Common (both types):**
1651+
- `enabled:` - Whether this MCP server is active (default: `true`). Set to `false` to temporarily disable an entry without removing it from the front matter.
16511652
- `allowed:` - Array of tool names the agent is permitted to call (required for security)
16521653
- `env:` - Environment variables for the MCP server process. Use `""` (empty string) for passthrough from the pipeline environment.
16531654

README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -328,6 +328,7 @@ mcp-servers:
328328
container: "node:20-slim"
329329
entrypoint: "node"
330330
entrypoint-args: ["path/to/mcp-server.js"]
331+
# enabled: set to false to temporarily disable without removing the entry
331332
# args: additional Docker runtime arguments inserted before the image name
332333
# (e.g. ["--memory", "512m"]). Dangerous flags like --privileged trigger
333334
# a compile-time warning.

prompts/create-ado-agentic-workflow.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -201,6 +201,7 @@ mcp-servers:
201201
container: "node:20-slim"
202202
entrypoint: "node"
203203
entrypoint-args: ["path/to/server.js"]
204+
enabled: false # Set to false to temporarily disable without removing
204205
env:
205206
API_KEY: "$(MY_SECRET)"
206207
allowed:

0 commit comments

Comments
 (0)