You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/copilot/concepts/agents/copilot-cli/about-remote-access.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ docsTeamMetrics:
12
12
- copilot-cli
13
13
---
14
14
15
-
This article explains the concepts around remote access to {% data variables.copilot.copilot_cli_short %} sessions. For instructions on how to enable remote access, see [AUTOTITLE](/copilot/how-tos/copilot-cli/steer-remotely).
15
+
This article explains the concepts around remote access to {% data variables.copilot.copilot_cli_short %} sessions. For instructions on how to enable remote access, see [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/steer-remotely).
16
16
17
17
## Introduction
18
18
@@ -64,9 +64,9 @@ When connected to a session remotely from {% data variables.product.prodname_dot
64
64
65
65
If the connection between your local machine and {% data variables.product.prodname_dotcom %} is temporarily lost—for example, due to a network interruption—you can continue using the session remotely as soon as the connection is restored.
66
66
67
-
You can use the `/keep-alive` slash command to prevent your machine from going to sleep. See [Preventing your machine from going to sleep](/copilot/how-tos/copilot-cli/steer-remotely#preventing-your-machine-from-going-to-sleep).
67
+
You can use the `/keep-alive` slash command to prevent your machine from going to sleep. See [Preventing your machine from going to sleep](/copilot/how-tos/copilot-cli/use-copilot-cli/steer-remotely#preventing-your-machine-from-going-to-sleep).
68
68
69
-
If you closed a session that had remote access enabled, when you resume the session—either using `copilot --continue` or `copilot --resume=ID`—you must re-enable remote access. For more information, see [AUTOTITLE](/copilot/how-tos/copilot-cli/steer-remotely#resuming-a-session-with-remote-access).
69
+
If you closed a session that had remote access enabled, when you resume the session—either using `copilot --continue` or `copilot --resume=ID`—you must re-enable remote access. For more information, see [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/steer-remotely#resuming-a-session-with-remote-access).
Copy file name to clipboardExpand all lines: content/copilot/concepts/agents/copilot-cli/cancel-and-roll-back.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ As a rule of thumb, use <kbd>Esc</kbd> when you want to intervene selectively, a
46
46
47
47
While {% data variables.product.prodname_copilot_short %} is inactive and there is no text in the input area, you can press <kbd>Esc</kbd> twice to display a list of points in your current session that you can roll back to. Each point corresponds to a snapshot of your workspace that was taken immediately before {% data variables.product.prodname_copilot_short %} started working on the prompt shown in the list.
48
48
49
-
For full details of how to use the double <kbd>Esc</kbd> keypress to roll back changes made during a session, see [AUTOTITLE](/copilot/how-tos/copilot-cli/roll-back-changes).
49
+
For full details of how to use the double <kbd>Esc</kbd> keypress to roll back changes made during a session, see [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/roll-back-changes).
50
50
51
51
> [!WARNING]
52
52
> {% data reusables.copilot.copilot-cli.cli-rewind-warning %}
Copy file name to clipboardExpand all lines: content/copilot/concepts/agents/copilot-cli/chronicle.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ This session data powers several features:
23
23
***Asking questions about your history**: You can ask {% data variables.product.prodname_copilot_short %} questions about your past work, and it will query your session data to answer them.
24
24
***The `/chronicle` slash command**: A set of purpose-built subcommands that generate standup reports, personalized tips, and suggestions for improving your custom instructions—all derived from your session history.
25
25
26
-
This conceptual article explains how session data is stored, and how you can leverage it to enhance your workflow. For a practical guide to resuming a session, asking {% data variables.product.prodname_copilot_short %} about your CLI sessions, and using the `/chronicle` slash command, see [AUTOTITLE](/copilot/how-tos/copilot-cli/chronicle).
26
+
This conceptual article explains how session data is stored, and how you can leverage it to enhance your workflow. For a practical guide to resuming a session, asking {% data variables.product.prodname_copilot_short %} about your CLI sessions, and using the `/chronicle` slash command, see [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/chronicle).
27
27
28
28
{% data reusables.copilot.copilot-cli.cli-experimental-chronicle %}
29
29
@@ -92,5 +92,5 @@ To reindex the session store, use the following slash command in an interactive
Copy file name to clipboardExpand all lines: content/copilot/concepts/agents/copilot-cli/fleet.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ docsTeamMetrics:
17
17
18
18
The `/fleet` slash command in {% data variables.copilot.copilot_cli_short %} is designed to take an implementation plan and break it down into smaller, independent tasks that can be executed in parallel by subagents. This allows for faster completion of complex requests that involve multiple steps.
19
19
20
-
This article gives an overview of the `/fleet` slash command. For details of how to use it, see [AUTOTITLE](/copilot/how-tos/copilot-cli/speed-up-task-completion).
20
+
This article gives an overview of the `/fleet` slash command. For details of how to use it, see [AUTOTITLE](/copilot/how-tos/copilot-cli/use-copilot-cli/speed-up-task-completion).
21
21
22
22
## How `/fleet` works
23
23
@@ -70,6 +70,6 @@ For more information about autopilot mode, see [AUTOTITLE](/copilot/concepts/age
Copy file name to clipboardExpand all lines: content/copilot/how-tos/copilot-cli/customize-copilot/plugins-finding-installing.md
+3-48Lines changed: 3 additions & 48 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ docsTeamMetrics:
16
16
17
17
## Introduction
18
18
19
-
Plugins are packages that extend the functionality of {% data variables.copilot.copilot_cli_short %}. You can install a plugin from a marketplace that you have registered with the CLI, from a Git repository, or from a local path.
19
+
Plugins are packages that extend the functionality of {% data variables.copilot.copilot_cli_short %}. You can install a plugin from a marketplace that you have registered with the CLI.
20
20
21
21
For more information, see [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about-cli-plugins).
22
22
@@ -26,8 +26,6 @@ For more information, see [AUTOTITLE](/copilot/concepts/agents/copilot-cli/about
26
26
27
27
Plugins are collected together in marketplaces. A marketplace is a registry of plugins that you can browse and install from. You can add a marketplace to your CLI configuration, which allows you to use the CLI to browse and install plugins from that marketplace—see [Adding plugin marketplaces](#adding-plugin-marketplaces). {% data variables.product.prodname_copilot_short %} comes with two marketplaces already registered by default: `copilot-plugins` and `awesome-copilot`.
28
28
29
-
Alternatively, you can search for plugin marketplaces online and then add a plugin directly from a repository.
30
-
31
29
To use the CLI to browse the plugins in one of your registered marketplaces:
32
30
33
31
1.**Check which marketplaces are currently registered.**
@@ -55,11 +53,9 @@ To use the CLI to browse the plugins in one of your registered marketplaces:
55
53
56
54
## Installing plugins
57
55
58
-
Typically, you'll install a plugin from one of your registered marketplaces. However, you can also install a plugin directly from a Git repository, or from a local path.
59
-
60
-
For information on how to register additional marketplaces, see [Adding and removing plugin marketplaces](#adding-and-removing-plugin-marketplaces).
56
+
You can install plugins from a registered marketplace. For information on how to register additional marketplaces, see [Adding plugin marketplaces](#adding-plugin-marketplaces).
@@ -77,43 +73,6 @@ Alternatively, in an interactive session, enter:
77
73
/plugin install PLUGIN-NAME@MARKETPLACE-NAME
78
74
```
79
75
80
-
### Install directly from an online Git repository
81
-
82
-
You can install a plugin directly from a repository, rather than doing so using a registered marketplace.
83
-
84
-
To install a plugin directly from a repository **on {% data variables.product.prodname_dotcom_the_website %}**, enter:
85
-
86
-
```shell copy
87
-
copilot plugin install OWNER/REPO
88
-
```
89
-
90
-
To install a plugin from **any online Git repository**, enter:
91
-
92
-
```shell copy
93
-
copilot plugin install URL-OF-GIT-REPO
94
-
```
95
-
96
-
For example, `copilot plugin install https://gitlab.com/OWNER/REPO.git`.
97
-
98
-
> [!IMPORTANT]
99
-
> For these commands to work, the repository must contain a `plugin.json` file in a `.plugin`, `.github/plugin`, or `.claude-plugin` directory, or at the root of the repository.
100
-
101
-
To install a plugin directly from a repository on {% data variables.product.prodname_dotcom_the_website %} where the `plugin.json` file is located somewhere other than `.github/plugin`, `.claude-plugin`, or the repository root—for example, if you are installing a plugin directly from a marketplace repository such as [anthropics/claude-code](https://github.com/anthropics/claude-code)—enter:
102
-
103
-
```shell copy
104
-
copilot plugin install OWNER/REPO:PATH/TO/PLUGIN
105
-
```
106
-
107
-
Where `PATH/TO/PLUGIN` is the path from the root of the repository to a directory that contains `plugin.json`, `.github/plugin/plugin.json` or `.claude-plugin/plugin.json`.
108
-
109
-
For example, `copilot plugin install anthropics/claude-code:plugins/frontend-design`
110
-
111
-
### Install from a local path
112
-
113
-
```shell copy
114
-
copilot plugin install ./PATH/TO/PLUGIN
115
-
```
116
-
117
76
## Managing installed plugins
118
77
119
78
```bash
@@ -122,10 +81,6 @@ copilot plugin update PLUGIN-NAME # Update plugin to latest version
Plugins installed from a marketplace are stored at: `~/.copilot/installed-plugins/MARKETPLACE/PLUGIN-NAME/`. Plugins installed directly (for example, from a local path) are stored at: `~/.copilot/installed-plugins/_direct/SOURCE-ID/`.
128
-
129
84
## Adding plugin marketplaces
130
85
131
86
To add a marketplace to the list of registered marketplaces, enter the following command in the terminal:
You can use the `/review` slash command to have {% data variables.product.prodname_copilot_short %} analyze code changes without leaving the CLI. This lets you get quick feedback on your changes prior to committing.
0 commit comments