mirror of
https://github.com/github/awesome-copilot.git
synced 2026-08-11 11:49:14 +00:00
chore: publish from main
This commit is contained in:
@@ -3,7 +3,7 @@ title: 'Building Custom Agents'
|
||||
description: 'Learn how to create specialized GitHub Copilot agents with custom personas, tool integrations, and domain expertise.'
|
||||
authors:
|
||||
- GitHub Copilot Learning Hub Team
|
||||
lastUpdated: 2026-07-09
|
||||
lastUpdated: 2026-08-09
|
||||
estimatedReadingTime: '10 minutes'
|
||||
tags:
|
||||
- agents
|
||||
@@ -258,7 +258,7 @@ The agent can then query your database, analyze query plans, and suggest optimiz
|
||||
| Complex reasoning, analysis | Claude Sonnet 4 |
|
||||
| Code generation, tool-driven agentic work | GPT-5.6 *(v1.0.70+)* |
|
||||
| Code generation, refactoring | GPT-4.1 |
|
||||
| Code-specialized tasks, large context | kimi-k2.7-code *(v1.0.68+)* |
|
||||
| Code-specialized tasks, large context | kimi-k2.7-code *(v1.0.68+)*, kimi-k3 *(v1.0.79+)* |
|
||||
| Quick analysis, simple tasks | Claude Haiku or GPT-4.1-mini |
|
||||
| Large codebase understanding | Models with larger context windows |
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: 'Copilot Configuration Basics'
|
||||
description: 'Learn how to configure GitHub Copilot at user, workspace, and repository levels to optimize your AI-assisted development experience.'
|
||||
authors:
|
||||
- GitHub Copilot Learning Hub Team
|
||||
lastUpdated: 2026-08-06
|
||||
lastUpdated: 2026-08-09
|
||||
estimatedReadingTime: '10 minutes'
|
||||
tags:
|
||||
- configuration
|
||||
@@ -786,6 +786,14 @@ copilot --plan # start in plan mode (propose without executing)
|
||||
|
||||
This is useful in scripts or CI pipelines where you want the CLI to immediately begin working in a specific mode without an interactive prompt.
|
||||
|
||||
**Plan-then-implement (v1.0.79+)**: Combine `--plan` with `--mode autopilot` to have the agent draft a plan first and then implement it without waiting for approval, instead of pausing after the plan for manual confirmation:
|
||||
|
||||
```bash
|
||||
copilot --plan --mode autopilot "Add rate limiting to the API"
|
||||
```
|
||||
|
||||
This is useful for automated pipelines that still want the reasoning benefits of a planning phase but don't want a human in the loop between planning and execution.
|
||||
|
||||
The `--max-autopilot-continues` flag controls how many times Copilot can automatically continue in autopilot mode before pausing for confirmation. The default is 5:
|
||||
|
||||
```bash
|
||||
@@ -807,6 +815,10 @@ These flags apply only to the current invocation — your persisted sandbox pref
|
||||
|
||||
> **Breaking change (v1.0.79)**: The setting was renamed from `allowDevToolCaches` to `allowDevToolAccess`. If you previously set `allowDevToolCaches` to `false` to opt out, update your `settings.json` to use `allowDevToolAccess` — the old key is silently ignored.
|
||||
|
||||
**Sandbox auth settings** *(v1.0.79-8+, breaking change)*: The `/sandbox` configuration dialog now groups git, `gh`, and (on macOS) keychain settings under a new **Auth** tab. The underlying settings keys moved from `sandbox.gitAuth`/`sandbox.ghAuth` to `sandbox.auth.git`/`sandbox.auth.gh`. There is no automatic migration — the old keys are silently ignored in settings files, and SDK requests that still send them are rejected as invalid. Update any saved configuration to the new key names.
|
||||
|
||||
**`worktreeBaseRef` setting** *(v1.0.79-8+)*: Controls whether `/worktree`, `/worktree new`, and the `--worktree` startup flag create the new worktree from `HEAD` or from the remote default branch. All three now default to `HEAD`; previously `--worktree` defaulted to starting from the remote default branch. Set this in `/settings` if you want worktrees to branch from the remote default instead.
|
||||
|
||||
The `--attachment` flag (available in prompt mode, `-p`) lets you attach files — images or native documents — to the initial prompt in non-interactive mode:
|
||||
|
||||
**Browser-based OAuth login** *(v1.0.77+)*: `copilot login` now defaults to the browser (web) flow on local interactive terminals. A browser tab opens, you authenticate with GitHub, and the CLI is authorized without typing a device code. On remote or headless terminals (SSH sessions, CI), device code remains the default. You can force a specific flow with `--web-flow` or `--device-code`, or choose interactively with the `/login` command:
|
||||
|
||||
Reference in New Issue
Block a user