docs: update copilot-cli content from source docs (#60146)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: hubwriter <hubwriter@github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Author: 4 people

content/copilot/concepts/agents/copilot-cli/about-copilot-cli.md

@@ -49,7 +49,7 @@ You can also pass the CLI a single prompt directly on the command line. The CLI
 To use the CLI programmatically, include the `-p` or `--prompt` command-line option in your command. To allow {% data variables.product.prodname_copilot_short %} to modify and execute files you should also use one of the approval options described later in this article—see [Allowing tools to be used without manual approval](#allowing-tools-to-be-used-without-manual-approval) ). For example:
 
   ```bash copy
-  copilot -p "Show me this week's commits and summarize them" --allow-tool 'shell(git)'
+  copilot -p "Show me this week's commits and summarize them" --allow-tool='shell(git)'
   ```
 
   Alternatively, you can use a script to output command-line options and pipe this to `copilot`. For example:
@@ -245,22 +245,22 @@ The `--deny-tool` and `--allow-tool` options require one of the following argume
   For `git` and `gh` commands, you can specify a particular first-level subcommand to allow or deny. For example:
 
   ```shell
-  copilot --deny-tool 'shell(git push)'
+  copilot --deny-tool='shell(git push)'
   ```
 
-  The tool specification is optional. For example, `copilot --allow-tool 'shell'` allows {% data variables.product.prodname_copilot_short %} to use any shell command without individual approval.
+  The tool specification is optional. For example, `copilot --allow-tool='shell'` allows {% data variables.product.prodname_copilot_short %} to use any shell command without individual approval.
 
 * `'write'`
 
   This argument allows or denies tools—other than shell commands—permission to modify files.
 
-  For example, `copilot --allow-tool 'write'` allows {% data variables.product.prodname_copilot_short %} to edit files without your individual approval.
+  For example, `copilot --allow-tool='write'` allows {% data variables.product.prodname_copilot_short %} to edit files without your individual approval.
 
 * `'MCP_SERVER_NAME'`
 
   This argument allows or denies tools from the specified MCP server, where `MCP_SERVER_NAME` is the name of an MCP server that you have configured. Tools from the server are specified in parentheses, using the tool name that is registered with the MCP server. Using the server name without specifying a tool allows or denies all tools from that server.
 
-  For example, `copilot --deny-tool 'My-MCP-Server(tool_name)'` prevents {% data variables.product.prodname_copilot_short %} from using the tool called `tool_name` from the MCP server called `My-MCP-Server`.
+  For example, `copilot --deny-tool='My-MCP-Server(tool_name)'` prevents {% data variables.product.prodname_copilot_short %} from using the tool called `tool_name` from the MCP server called `My-MCP-Server`.
 
   You can find an MCP server's name by entering `/mcp` in the CLI's interactive interface, then selecting the server from the list that's displayed.
 
@@ -271,13 +271,13 @@ You can use a combination of approval options to determine exactly which tools {
 For example, to prevent {% data variables.product.prodname_copilot_short %} from using the `rm` and `git push` commands, but automatically allow all other tools, use:
 
 ```shell
-copilot --allow-all-tools --deny-tool 'shell(rm)' --deny-tool 'shell(git push)'
+copilot --allow-all-tools --deny-tool='shell(rm)' --deny-tool='shell(git push)'
 ```
 
 To prevent {% data variables.product.prodname_copilot_short %} from using the tool `tool_name` from the MCP server named `My-MCP-Server`, but allow all other tools from that server to be used without individual approval, use:
 
 ```shell
-copilot --allow-tool 'My-MCP-Server' --deny-tool 'My-MCP-Server(tool_name)'
+copilot --allow-tool='My-MCP-Server' --deny-tool='My-MCP-Server(tool_name)'
 ```
 
 #### Security implications of automatic tool approval

content/copilot/how-tos/copilot-cli/cli-best-practices.md

@@ -76,7 +76,7 @@ To reset previously approved tools, use:
 You can also preconfigure allowed tools via CLI flags:
 
 ```bash
-copilot --allow-tool 'shell(git:*)' --deny-tool 'shell(git push)'
+copilot --allow-tool='shell(git:*)' --deny-tool='shell(git push)'
 ```
 
 **Common permission patterns:**

content/copilot/how-tos/copilot-cli/set-up-copilot-cli/configure-copilot-cli.md

@@ -109,7 +109,7 @@ Use `--deny-tool` to prevent {% data variables.product.prodname_copilot_short %}
 * For example:
 
   ```shell
-  copilot --deny-tool 'shell(git push)'
+  copilot --deny-tool='shell(git push)'
   ```
 
 This option takes precedence over the `--allow-all-tools` and `--allow-tool` options.
@@ -121,7 +121,7 @@ Use `--allow-tool` to allow {% data variables.product.prodname_copilot_short %}
 * For example:
 
   ```shell
-  copilot --allow-tool 'shell'
+  copilot --allow-tool='shell'
   ```
 
 ### Specifying which tool you want to allow or deny
@@ -139,18 +139,18 @@ Use `shell(COMMAND)` to allow or deny a specific shell command.
 * For example, to prevent {% data variables.product.prodname_copilot_short %} from using any `rm` command, use:
 
   ```shell
-  copilot --deny-tool 'shell(rm)'
+  copilot --deny-tool='shell(rm)'
   ```
 
 For `git` and `gh` commands, specify a particular first-level subcommand to allow or deny.
 
 * For example, to prevent {% data variables.product.prodname_copilot_short %} from using `git push`, use:
 
   ```shell
-  copilot --deny-tool 'shell(git push)'
+  copilot --deny-tool='shell(git push)'
   ```
 
-The tool specification is optional. For example, `copilot --allow-tool 'shell'` allows {% data variables.product.prodname_copilot_short %} to use any shell command without individual approval.
+The tool specification is optional. For example, `copilot --allow-tool='shell'` allows {% data variables.product.prodname_copilot_short %} to use any shell command without individual approval.
 
 #### Allowing or denying `'write'` tools
 
@@ -159,7 +159,7 @@ Use `'write'` to allow or deny tools—other than shell commands—permission to
 * For example, to allow {% data variables.product.prodname_copilot_short %} to edit files without your individual approval, use:
 
   ```shell
-  copilot --allow-tool 'write'
+  copilot --allow-tool='write'
   ```
 
 #### Allowing or denying MCP server tools
@@ -169,7 +169,7 @@ Use `'MCP_SERVER_NAME'` to allow or deny a specific tool from the specified MCP
 * For example, to prevent {% data variables.product.prodname_copilot_short %} from using the tool called `tool_name` from the MCP server called `My-MCP-Server`, use:
 
   ```shell
-  copilot --deny-tool 'My-MCP-Server(tool_name)'
+  copilot --deny-tool='My-MCP-Server(tool_name)'
   ```
 
 `MCP_SERVER_NAME` is the name of an MCP server that you have configured.
@@ -187,13 +187,13 @@ To determine exactly which tools {% data variables.product.prodname_copilot_shor
 * To prevent {% data variables.product.prodname_copilot_short %} from using the `rm` and `git push` commands, but automatically allow all other tools, use:
 
   ```shell
-  copilot --allow-all-tools --deny-tool 'shell(rm)' --deny-tool 'shell(git push)'
+  copilot --allow-all-tools --deny-tool='shell(rm)' --deny-tool='shell(git push)'
   ```
 
 * To prevent {% data variables.product.prodname_copilot_short %} from using the tool `tool_name` from the MCP server named `My-MCP-Server`, but allow all other tools from that server to be used without individual approval, use:
 
   ```shell
-  copilot --allow-tool 'My-MCP-Server' --deny-tool 'My-MCP-Server(tool_name)'
+  copilot --allow-tool='My-MCP-Server' --deny-tool='My-MCP-Server(tool_name)'
   ```
 
 ### Limiting available tools
@@ -246,15 +246,15 @@ To disable URL verification, use the `--allow-all-urls` flag.
 
 ### Pre-approving specific domains
 
-To pre-approve specific domains, use `--allow-url <domain>`.
+To pre-approve specific domains, use `--allow-url=DOMAIN`.
 
-* For example, `--allow-url github.com`.
+* For example, `--allow-url=github.com`.
 
 ### Denying specific domains
 
-To deny specific domains, use `--deny-url <domain>`.
+To deny specific domains, use `--deny-url=DOMAIN`.
 
-* For example, `--deny-url github.com`.
+* For example, `--deny-url=github.com`.
 
 ## Allowing all tools, paths, and URLs
 

content/copilot/how-tos/use-copilot-agents/manage-agents.md

@@ -15,7 +15,7 @@ category:
 ## 1. Select a repository and choose your agent
 
 1. Start a new agent task.
-    
+
     * Open the **{% octicon "agent" aria-label="The Agents icon" %} Agents** tab in a repository
     * Open the [Agents page](https://github.com/copilot/agents?ref_product=copilot&ref_type=engagement&ref_style=text)
     * Use the **Task** button or `/task` command from [{% data variables.copilot.copilot_chat_short %}](https://github.com/copilot?ref_product=copilot&ref_type=engagement&ref_style=text)
@@ -40,7 +40,7 @@ For more information on ways to start new agent tasks, see [AUTOTITLE](/copilot/
 
 Once the agent starts working, it will continue to update the session log and overview with its progress and thought process.
 
-Each session displays its status. Click on a session to open the session log, where you can monitor the agent's progress, see the tools it's using, and track how long the session has been running. 
+Each session displays its status. Click on a session to open the session log, where you can monitor the agent's progress, see the tools it's using, and track how long the session has been running.
 
 {% data variables.copilot.copilot_coding_agent %} sessions can also be tracked from the {% data variables.product.prodname_cli %}, {% data variables.product.prodname_mobile %}, {% data variables.product.prodname_vscode %}, Raycast, and JetBrains IDEs. For more information, see [AUTOTITLE](/copilot/how-tos/use-copilot-agents/coding-agent/track-copilot-sessions).
 
@@ -68,14 +68,14 @@ In the prompt box under the agent session log, prompt {% data variables.product.
 You can guide the agent in your local development environment on further changes, or make any edits that require human expertise.
 
 ### {% data variables.product.prodname_vscode_shortname %}
-  
+
 At the bottom of the agent session view, click the **{% octicon "vscode" aria-label="VS Code" %} Open in {% data variables.product.prodname_vscode_shortname %}** button to launch the session directly in {% data variables.product.prodname_vscode_shortname %}.
 
 {% data reusables.copilot.coding-agent.use-latest-vscode %}
 
 ### {% data variables.copilot.copilot_cli %}
   1. At the bottom of the agent session view, click the dropdown list next to **{% octicon "vscode" aria-label="VS Code" %} Open in {% data variables.product.prodname_vscode_shortname %}**.
-  1. Click **{% octicon "agent" aria-label="Agent" %} Continue in {% data variables.copilot.copilot_cli %}** to copy the `copilot --resume=<session ID>` command to your clipboard. 
+  1. Click **{% octicon "agent" aria-label="Agent" %} Continue in {% data variables.copilot.copilot_cli %}** to copy the `copilot --resume=SESSION-ID` command to your clipboard.
       ![Screenshot of the session action dropdown list, "Continue in Copilot CLI" is highlighted with a dark orange outline.](/assets/images/help/copilot/coding-agent/open-agent-session-in-copilot-cli.png)
   1. In your terminal, paste and run the command to resume the agent session.
 
@@ -85,7 +85,7 @@ Once the agent completes a session, you can navigate to the pull request to revi
 
 ## 6. Archive agent sessions
 
-Sessions that have been stopped can be archived to remove them from the sessions list. 
+Sessions that have been stopped can be archived to remove them from the sessions list.
 
 1. Open the agent session you want to archive.
 1. In the top right corner, click **{% octicon "kebab-horizontal" aria-label="More actions" %}**, then click **{% octicon "inbox" aria-hidden="true" aria-label="inbox" %} Archive session**.