VS Code 1.118 and Copilot CLI remote control: Guidelines for bringing your own Copilot in custom development 2026

In early May 2026, VS Code 1.118 was released, introducing multiple changes directly impacting day-to-day custom development operations, such as remote control of Copilot CLI and defaulting to automatic "Co-Authored-by Copilot" commit attribution. On Zenn, "The VSCode 1.118 Update Is Super Exciting" has also become a hot topic.

Additionally, GitHub Copilot transitioned to a token-consumption-based billing model, and code reviews now consume GitHub Actions minutes. When bringing Copilot into client repositories during custom development, the pillars of "commit attribution," "billing," and "compliance policies" are all being shaken simultaneously. In this article, we outline guidelines for "bringing your own Copilot" in custom development.

Changes in VS Code 1.118 and the Copilot ecosystem (relevant scope for custom development)

We extract changes critical to custom development from the official release and release notes.

In particular, default Co-Authored-by Copilot attribution is an unexpectedly troublesome behavior in custom development, as leaving it unconfigured results in a Co-authored-by: Copilot <...> line being added to client Git histories without explicit permission.

The problematic "Co-Authored-by Copilot" issue in custom development

Here is the breakdown of the issue.

[開発者の VS Code]                  [クライアントのGitHubリポ]
   ↓ Copilot 補完を採用              ↓ git push
   ↓ git commit                      ↓
   commit message 末尾に           PR / commit log に
   Co-authored-by: Copilot          Copilot のメールアドレスが残る
   が自動挿入                        ↓
                                    クライアントが「これは何？」
                                    「監査でどう説明する？」

Some clients have policies "prohibiting email addresses of external AIs like Copilot from entering company repositories," creating the risk that custom development contractors might inadvertently violate them.

Initial steps to take in custom development

1. Verify client policies — Confirm whether external AI credit notations are permitted when executing the SOW
2. Explicitly define VS Code settings — Explicitly configure Co-Authored-by enablement in the project's .vscode/settings.json
3. Enforce with Git hooks — Verify presence or absence of the Co-Authored-by line using a commit-msg hook
4. Note in PR templates — Clearly state "AI used" for PRs created with Copilot

In custom development, committing .vscode/settings.json to the repository is strongly recommended. This standardizes behavior across newly onboarded members and developers on different machines.

// .vscode/settings.json（クライアント側で許容する場合）
{
  "github.copilot.chat.commitMessage.coAuthor": true,
  "github.copilot.advanced.debug.useTokens": true
}

// .vscode/settings.json（クライアント側で禁止する場合）
{
  "github.copilot.chat.commitMessage.coAuthor": false
}

How transitioning to token-based billing changes custom development estimates

GitHub Copilot's transition to a token-consumption-based pricing model directly affects estimates in custom development.

Teams in custom development that previously quoted "flat monthly Copilot usage fees" now need to factor variable token consumption costs into estimates. In practice, the cost breakdown looks as follows.

[Copilot 月額コスト = 基本料金 + 追加トークン消費 + Actions minutes]

基本料金: $10〜$39 / 開発者 / 月
追加トークン: 上位モデル使用量 × 単価
Actions minutes: Copilot Review が消費する分

In our custom development projects, we switched during kickoff to an operating model of "measuring actual token consumption over 1–2 months → budgeting for subsequent months." This corresponds to the editor-integrated version of "making token costs predictable" covered in Design Patterns for Cutting Agent Token Consumption by 70% with Cloudflare Code Mode MCP.

Copilot CLI remote control — Application in custom development reviews

In VS Code 1.118, being able to remotely control Copilot CLI from the editor transforms the custom development review workflow. Specific use cases include:

This represents an evolution that takes the "standalone CLI operation" discussed in the Complete Guide to GitHub Copilot CLI and Rubber Duck Debugging with GitHub Copilot CLI and makes it robust enough for team reviews in custom development.

10-item "bringing your own Copilot" checklist for custom development

Here is a checklist for bringing Copilot into projects while satisfying client compliance rules and risk constraints.

• Confirmed the client's "external AI usage policy"
• Explicitly specified whether Co-Authored-by Copilot is on or off in .vscode/settings.json
• Copilot prompt transmission logs are auditable in the client environment
• Stipulated the billing party (contractor / client) in the SOW
• Agreed on shutdown rules when exceeding token caps
• Secured a separate Actions minutes budget for Code Review
• Clarified contracting entity when using external models via BYOK
• Defined Copilot-permitted zones and restricted zones (confidential areas)
• Added a field to the PR template for noting "AI-assisted sections"
• Documented customer data classification sent via Copilot (PII included / excluded)

In particular, disabling Copilot during hours when editing "code containing PII" is a common practice in medical and financial custom development. Mechanisms such as switching settings per VS Code Workspace or re-verifying during commit check-ins become essential.

Conclusion — VS Code 1.118 as a turning point prompting clients to review policies

Changes surrounding VS Code 1.118 and Copilot represent an opportunity to review client-side AI usage policies and operational guidelines that goes beyond individual feature updates. Automatic Co-Authored-by attribution, token billing, BYOK enablement, CLI remote control—every one of these can easily cause incidents unless custom development teams clearly codify what is permissible to bring into projects.

At our company, we execute the "bringing Copilot checklist + client policy alignment" as a paired package when kicking off new custom development engagements. If you are experiencing challenges such as "We want to bring Copilot into the company but policy preparation cannot keep up" or "The transition to token billing disrupted our budget management," please feel free to reach out via our contact form.

Sources

• VS Code 1.118 Released, Defaulting to Remote Control of Copilot CLI and Copilot Co-Author Attribution (gihyo.jp)
• The VSCode 1.118 Update Is Super Exciting (Zenn)
• VS Code inserting ‘Co-Authored-by Copilot’ into commits regardless of usage（GitHub PR）
• GitHub Copilot is moving to usage-based billing（GitHub Blog）