Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update experiments.md and settings.md to be up-to-date #70

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 9 additions & 18 deletions experiments.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,30 +10,21 @@ We greatly appreciate any [feedback](https://github.com/githubnext/copilot-works

There are several active "Experiments" available related to things we are working on. We invite you to activate these and will update this document with new experiments when they are available. These features aren't set in stone, and any feedback regarding them would be greatly appreciated.

### Use line numbers always (🥼)
### Use emoji in topic and explorations 😊

We are experimenting with a feature that allows Copilot Workspace to always use line numbers when generating code. Enable this using the "Use line numbers always" feature in Copilot Workspace.
We are experimenting with a feature that allows Copilot Workspace to use emoji in the topic and explorations. Enable this using the "Use emoji in topic and explorations" feature in Copilot Workspace.

### Use emoji in topic and specs (🥼)
### Enable follow up 🔄

We are experimenting with a feature that allows Copilot Workspace to use emoji in the topic and specifications. Enable this using the "Use emoji in topic and specs" feature in Copilot Workspace.
When working with large repositories that have complex inter-file dependencies, a simple change or refactoring can impact many other parts of the codebase (e.g., updating a shared method signature). While the plan does a great job of identifying the core changes needed for a task (the "primary edits"), it can sometimes miss transitive changes that are needed in response (e.g., updating callers of a changed function).

### Utilize linked issues, PRs, and GitHub file links in analysis (🥼)
To address this, after implementing a plan, you can open the Commands tab and click the new Follow up button. This will perform a thorough, fine-grained check on your codebase and edits to see if any additional changes are required to complete your task. If any follow-ups are detected, it will edit the necessary files and add them to your existing implementation.

We are experimenting with a feature that allows Copilot Workspace to utilize linked issues, pull requests, and GitHub file links when analyzing tasks. This allows CW to have more context related to linked issues, PRs, and GitHub file links in analysis. Enable this using the "Utilize linked issues, PRs, and GitHub file links in analysis" feature in Copilot Workspace.

### Utilize referenced generic web content in analysis (🥼)
### Use summaries of images in the context 🖼️

We are experimenting with a feature that allows Copilot Workspace to utilize referenced generic web content when analyzing tasks. Currently, the contents of the URL are summarized and given to Copilot Workspace, in order to aid Copilot Workspace more focused on relevant details.
We are experimenting with a feature that allows Copilot Workspace to use summaries of images in the context. This helps provide more relevant information and improve the accuracy of the generated specifications and plans. Enable this using the "Use summaries of images in the context" feature in Copilot Workspace.

### Use code search during task analysis (🥼)
### Allow file(s) to be attached as additional context 📎

We are experimenting with a feature that allows Copilot Workspace to utilize code search during task analysis. This helps Copilot Workspace identify relevant files and code snippets more effectively, improving the overall accuracy and relevance of the generated specifications and plans. Enable this using the "Use code search during task analysis" feature in Copilot Workspace. Note that this experiment may result in slower completion times for spec/plan generation, but will cause Copilot Workspace to be more "focused" on your codebase.

### Clarify ambiguous specifications (🥼)

We are experimenting with a feature that allows Copilot Workspace to detect and warn about ambiguous specifications, in cooperation with the user. Enable this using the "Clarify ambiguous specifications" feature in Copilot Workspace.

### Allow skipping the spec and going straight to plan (🥼)

We are experimenting with a feature that allows users to skip the specification step and go straight to the plan. This is especially useful if you have already written a very detailed task description and want Copilot Workspace to go straight to implementing the task. Enable this using the "Allow skipping the spec and going straight to plan" feature in Copilot Workspace.
We are experimenting with a feature that allows Copilot Workspace to allow file(s) to be attached as additional context. This helps provide more relevant information and improve the accuracy of the generated specifications and plans. Enable this using the "Allow file(s) to be attached as additional context" feature in Copilot Workspace.
20 changes: 18 additions & 2 deletions settings.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,18 @@

These settings are preferences for how you want Copilot Workspace to behave with your workflows.

## Automatically include external URLs in context

When this setting is enabled, Copilot Workspace will automatically include external URLs referenced in the task description as part of the context. This helps provide more relevant information and improve the accuracy of the generated specifications and plans.

## Collapse timeline on implement

When this setting is enabled, the timeline panel on the left side of the workspace will automatically collapse after you click the "Implement" button. This allows you to focus more on the code changes and less on the timeline, while still being able to revise with natural language.

## Show notification after long-running operations

When this setting is enabled, Copilot Workspace will notify you when it has completed long-running operations, such as implementing a plan. This allows you to get back into the flow as soon as possible, without having to constantly check the status of the operation. You can enable or disable this setting based on your preference.

## Spin up a codespace when a session is created

When this setting is enabled, a Codespace will be automatically created when you start a new session. This provides a full development environment with language services, making it easier to work on your tasks. Note that selecting this option may cause code generated by Copilot Workspace to be executed before you are able to review it. By selecting this, you acknowledge the risks of auto-running AI-generated code.
Expand All @@ -14,6 +22,14 @@ When this setting is enabled, a Codespace will be automatically created when you

When this setting is enabled, a Codespace will be automatically created when you click the "Implement" button. This provides a full development environment with language services, making it easier to work on your tasks. Note that selecting this option may cause code generated by Copilot Workspace to be executed before you are able to review it. By selecting this option, you acknowledge the risks of auto-running AI-generated code.

## Show notification after implementing
## Mark sessions as complete after committing

When this setting is enabled, Copilot Workspace will automatically mark sessions as complete after you create a PR, branch, or commit for them. This helps keep your recent sessions list clean and organized. If you later decide that you need to continue a session that was marked as complete, you can always resume it from the Completed sessions list at any time.

## Enable high contrast mode

When this setting is enabled, Copilot Workspace will use a high contrast color theme, making it easier to read and navigate the interface for users with visual impairments or those who prefer a higher contrast display.

## Open in VS Code Insiders

When this setting is enabled, Copilot Workspace will notify you when it has completed its implementation. This allows you to get back into the flow as soon as possible, without having to constantly check the status of the implementation. You can enable or disable this setting based on your preference.
When this setting is enabled, the "Open in VS Code" button will launch VS Code Insiders instead of the stable version. This allows you to use the latest features and improvements available in the Insiders build of VS Code.