Daily brief
The Copilot App Opens Up to GitHub Enterprise Server, and AI Scan Gets a REST Switch
By Steven Sorensen · 15 Nov 2026

At a glance
- Teams on GitHub Enterprise Server can now add that account to the GitHub Copilot app and work with its repositories, issues and pull requests.
- Security teams can turn AI Scan for whole repositories on or off with scripts instead of clicking through settings one repository at a time.
- Qwen Code has a new stable build that asks before risky actions in Auto Mode and marks full access clearly.
- Two GitHub deadlines remain on the calendar, one for older Arm runners and one for six Copilot models.
GitHub posted the Copilot app note at about 1:27 PM ET on Nov 13 and the AI Scan note at about 7:22 AM ET the same day, and the GitHub Changelog has nothing newer as of early Sunday. Qwen Code v0.27.4 reached GitHub at about 2:04 AM ET today. Claude Code, Copilot CLI, Codex and Gemini CLI have no new stable release since the Nov 14 brief. The Cursor changelog is unchanged since Nov 6, and the Cursor CLI changelog is unchanged since Oct 22.
Treat today as a plan for Monday day: check whether your enterprise developers can now use the Copilot app against your own server, decide who owns the AI Scan setting before anyone scripts it, and try Qwen Code v0.27.4 on one machine if your team already uses it.
Top Stories
1. The GitHub Copilot app now supports GitHub Enterprise Server
GitHub says you can now bring work on GitHub Enterprise Server into the GitHub Copilot app by adding your server account, then work with remote repositories, issues and pull requests from there. The feature was an opt in preview and is now generally available.
The setup has an order. You sign in with a GitHub.com or GHE.com account first, then open Settings, Accounts, Add account and choose GitHub Enterprise Server. It needs Copilot app v1.2.0 or later, and the post says cloud sessions are not available for server accounts.
Practical dev impact: If your company runs its code on its own GitHub Enterprise Server, developers can now reach those repositories from the Copilot app. Plan for the missing piece, because any workflow that depends on cloud sessions still has to run against a GitHub.com or GHE.com account.
2. AI Scan for repositories gets a REST API switch in public preview
GitHub code scanning's AI Scan for repositories can now be turned on or off through the REST API at the organization and repository levels. The public preview adds a repository_scan setting to the existing AI Scan enablement endpoints, so a rollout can live in scripts or infrastructure as code instead of a long list of manual settings changes.
The setting behaves like the existing pr_scan setting for pull requests. If an organization disables it, its repositories cannot enable it. If an organization enables it, repositories inherit it and can opt out one by one. When enterprise policy does not allow AI Scan, an enable request returns a 422 error, and if you change both settings in one request and either is blocked, neither changes.
Turning the setting on does not start a scan. Users with write access still run scans on demand, and each scan uses GitHub Code Security AI credits. Organization owners and security managers manage the organization setting, repository administrators can opt out, enterprise owners must allow AI Scan in policy first, and GitHub Enterprise Server is not supported.
Practical dev impact: Read the current setting before you script a change, and agree who owns the switch. Because scans spend AI credits only when someone runs one, enabling the setting widely does not start spending by itself, but it does let users with write access run scans that use credits.
3. Qwen Code v0.27.4 asks first in Auto Mode
Qwen Code shipped v0.27.4 overnight, and npm latest for @qwen-code/qwen-code now points to it. The release highlights say Auto Mode now requires explicit authorization for risky actions, reviews classifier timeouts, avoids filesystem lookups for HTTP and HTTPS addresses, and visibly marks full access.
The other highlights are about managed work. Managed Agent sessions can use granted local directories and open an interactive Managed Web Terminal without saving credentials or paths, outputs can go to Feishu and WeCom webhooks with long replies split into ordered segments, and the CLI /memory controls are back. The notes list no known breaking changes.
Practical dev impact: If you run Qwen Code in Auto Mode, expect more prompts on actions it now treats as risky. Try the update on one machine first and watch whether an unattended run stops to ask.
Practical Impact Analysis
Our read: the Copilot app story has the widest reach today, because it brings a whole class of enterprise developers into the app for the first time, while the AI Scan switch matters most to security teams that manage many repositories. Neither one forces a change this weekend, so the useful move is to decide owners and test on a small scope on Monday.
The deadlines are a better use of a Sunday hour than anything new. GitHub's Nov 12 note says hosted Actions runners end support for ARM32 job execution on Windows and Linux by Dec 8, 2026, because Node 24 does not support ARM32, so search your workflows for ARM32 jobs now. The six Copilot model retirements GitHub announced on Nov 13 still land on Dec 14. Qwen Code v0.27.4 is a small reach update. Our read: if you run it in Auto Mode, an unattended job may now stop and wait for a prompt.
Tutorial
- Open a test shell. Every active command below only reads tags, versions, settings or dates.
- In step 2, replace the two placeholder values with an organization repository you administer. The call is a read only GET.
- Uncomment the install line in step 3 only if you want the pinned Qwen Code build.
- Step 4 counts the days left before the Dec 8 and Dec 14 deadlines from your own clock.
# We have not run this script end to end on every platform. It prints and checks, and changes no files.
# Run it in a test shell. Nothing is written to your shell profile.
# 1. Snapshot at 5:58 AM ET Sun Nov 15 2026, npm registry channel:
# @qwen-code/qwen-code latest v0.27.4
# unchanged at the same check: @anthropic-ai/claude-code latest v2.1.325, @github/copilot latest v1.0.112
npm view @qwen-code/qwen-code dist-tags.latest
if command -v qwen >/dev/null; then qwen --version; else echo "no qwen on PATH"; fi
# 2. Read the AI Scan setting for one repository (GET only, needs the GitHub CLI and access).
# Replace the two values with an organization repository you administer.
owner="your-org"
repo="your-repo"
if command -v gh >/dev/null; then
gh api "repos/$owner/$repo/code-scanning/ai-scan"
else
echo "no gh on PATH"
fi
# 3. Optional install only. Pinned at 5:58 AM ET Sun Nov 15 2026, npm registry channel:
# npm install -g @qwen-code/qwen-code@0.27.4
# 4. Days left before the Dec 8 ARM32 runner change and the Dec 14 Copilot model retirements, from your clock.
python3 -c 'import datetime; t = datetime.date.today(); print((datetime.date(2026, 12, 8) - t).days, "days to ARM32 end", (datetime.date(2026, 12, 14) - t).days, "days to model retirements")'
echo "Done. Nothing was installed or changed on disk."
If npm view shows a newer tag, refresh before you pin.
Sources:
- GitHub Enterprise Server support in the GitHub Copilot app
- Manage AI Scan for repositories using the REST API
- Qwen Code v0.27.4 release
- Actions for ARM32 Linux and Windows retirement
- Upcoming deprecation of selected GitHub Copilot models in December
- Cursor changelog
- Cursor CLI changelog
- GitHub Changelog
Recommended AI prompt
Copy this paragraph into ChatGPT, Claude, Gemini, Grok, or whatever AI you use.
You are my developer tooling lead for Sun Nov 15, 2026. Story 1: the GitHub Copilot app now supports GitHub Enterprise Server accounts for remote repositories, issues and pull requests in Copilot app v1.2.0 and later, but cloud sessions are not available for those accounts. Story 2: AI Scan for repositories can be turned on or off with the repository_scan setting on the AI Scan REST endpoints in public preview, and turning it on does not start a scan. Story 3: Qwen Code v0.27.4 makes Auto Mode require explicit authorization for risky actions. Ask which GitHub hosting, security settings and coding agents my team uses, then give a short Monday checklist for each story plus the Dec 8 ARM32 runner change, and link the official notes instead of inventing settings, endpoints or flags.