From 909a6feea6cbb75b94b8a7a3d8c44cb9306b1d33 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 19 Feb 2026 06:15:29 +0000
Subject: [PATCH 1/3] Initial plan


From 42032faa8ac9c6f4a4b01f62348ecff019a1a1b7 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 19 Feb 2026 06:22:35 +0000
Subject: [PATCH 2/3] Document engine.command field in engines.md

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
---
 docs/src/content/docs/reference/engines.md | 44 ++++++++++++++++++++++
 1 file changed, 44 insertions(+)

diff --git a/docs/src/content/docs/reference/engines.md b/docs/src/content/docs/reference/engines.md
index e21f3024157..25b937db8dc 100644
--- a/docs/src/content/docs/reference/engines.md
+++ b/docs/src/content/docs/reference/engines.md
@@ -86,6 +86,7 @@ engine:
   id: copilot
   version: latest                       # defaults to latest
   model: gpt-5                          # defaults to claude-sonnet-4
+  command: /usr/local/bin/copilot       # custom executable path
   args: ["--add-dir", "/workspace"]     # custom CLI arguments
   agent: agent-id                       # custom agent file identifier
 ```
@@ -131,6 +132,49 @@ engine:
 
 Arguments are added in order and placed before the `--prompt` flag. Common uses include adding directories (`--add-dir`), enabling verbose logging (`--verbose`, `--debug`), and passing engine-specific flags. Consult the specific engine's CLI documentation for available flags.
 
+### Custom Engine Command
+
+All engines support specifying a custom executable path through the `command` field. When specified, the workflow will skip the standard installation steps and use the provided command instead:
+
+```yaml wrap
+engine:
+  id: copilot
+  command: /usr/local/bin/custom-copilot
+```
+
+The `command` field can be:
+
+- **Absolute path**: Full path to a custom engine executable (e.g., `/usr/local/bin/copilot`)
+- **Relative path**: Path relative to the workflow directory (e.g., `./bin/claude-cli`)
+- **Command with environment variable**: Use environment variable expansion (e.g., `$HOME/.local/bin/codex`)
+- **Command in PATH**: Any executable available in the system PATH (e.g., `copilot-dev`)
+
+**Use cases:**
+
+- Testing pre-release versions of an engine
+- Using a custom build or fork of an engine
+- Running engines installed in non-standard locations
+- Using engine binaries built from source
+
+**Example with custom Copilot build:**
+
+```yaml wrap
+engine:
+  id: copilot
+  command: /workspace/copilot-dev/bin/copilot
+  args: ["--verbose"]
+```
+
+**Example with environment variable:**
+
+```yaml wrap
+engine:
+  id: codex
+  command: $HOME/.local/bin/codex-experimental
+```
+
+When a custom `command` is specified, the workflow assumes the engine is already installed and available at the specified path. Installation steps will be skipped.
+
 ## Related Documentation
 
 - [Frontmatter](/gh-aw/reference/frontmatter/) - Complete configuration reference

From 2171d64ee0aaa1edbd1c02641a029716950ecc4c Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 19 Feb 2026 06:36:15 +0000
Subject: [PATCH 3/3] Make engine.command documentation more concise

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
---
 docs/src/content/docs/reference/engines.md | 36 ++--------------------
 1 file changed, 3 insertions(+), 33 deletions(-)

diff --git a/docs/src/content/docs/reference/engines.md b/docs/src/content/docs/reference/engines.md
index 25b937db8dc..4d07809b533 100644
--- a/docs/src/content/docs/reference/engines.md
+++ b/docs/src/content/docs/reference/engines.md
@@ -134,46 +134,16 @@ Arguments are added in order and placed before the `--prompt` flag. Common uses
 
 ### Custom Engine Command
 
-All engines support specifying a custom executable path through the `command` field. When specified, the workflow will skip the standard installation steps and use the provided command instead:
+Override the default engine executable using the `command` field. Useful for testing pre-release versions, custom builds, or non-standard installations. Installation steps are automatically skipped.
 
 ```yaml wrap
 engine:
   id: copilot
-  command: /usr/local/bin/custom-copilot
-```
-
-The `command` field can be:
-
-- **Absolute path**: Full path to a custom engine executable (e.g., `/usr/local/bin/copilot`)
-- **Relative path**: Path relative to the workflow directory (e.g., `./bin/claude-cli`)
-- **Command with environment variable**: Use environment variable expansion (e.g., `$HOME/.local/bin/codex`)
-- **Command in PATH**: Any executable available in the system PATH (e.g., `copilot-dev`)
-
-**Use cases:**
-
-- Testing pre-release versions of an engine
-- Using a custom build or fork of an engine
-- Running engines installed in non-standard locations
-- Using engine binaries built from source
-
-**Example with custom Copilot build:**
-
-```yaml wrap
-engine:
-  id: copilot
-  command: /workspace/copilot-dev/bin/copilot
+  command: /usr/local/bin/copilot-dev  # absolute path
   args: ["--verbose"]
 ```
 
-**Example with environment variable:**
-
-```yaml wrap
-engine:
-  id: codex
-  command: $HOME/.local/bin/codex-experimental
-```
-
-When a custom `command` is specified, the workflow assumes the engine is already installed and available at the specified path. Installation steps will be skipped.
+The command supports absolute paths (`/usr/local/bin/copilot`), relative paths (`./bin/claude`), environment variables (`$HOME/.local/bin/codex`), or commands in PATH.
 
 ## Related Documentation