Starred repos weekly — Oct 26 – Nov 1, 2026: VS Code 1.144 runs agent tasks in the cloud, the other four ship no stable

The completed week was October 26 – November 1, 2026. One of the five tracked repositories published a stable release: VS Code 1.144.0 on October 28 1. Next.js, React, Rust and Tailwind CSS published no stable at all.

Take the VS Code update. It is the only thing on the list to install, and it is the release that moves agent work off your machine: Copilot tasks can now run in GitHub's cloud, and Copilot Fusion is generally available 2.

The other four kept moving without publishing. Next.js shipped nine canaries over 122 commits, React 17 commits, Rust 508, Tailwind CSS five.

Comment counts below are the total comments on each open issue or pull request in this snapshot. A thread that opened years ago carries a large number whether or not anyone touched it this week.

Next.js

vercel/next.js published no stable. 16.4.3 from October 23 is still the newest release 3, and npm's latest tag still points at it 4.

Nine canaries went out, from v16.5.0-canary.28 on October 26 to v16.5.0-canary.36 on October 31 5 6. Behind them, 122 commits landed on main.

Three of those fixes change behaviour you can hit in production. PR #100159 fixes hangs and crashes when a route handler returns a 204 with no body, and when a fetch is deduped 7.

PR #100956 fixes prerendering when a 'use cache' error is caught, and PR #100830 fixes the server-reference transform of export const foo = function bar(){} 8 9.

PR #98726 puts back the App Router locale path matching fix for Pages i18n, which had been reverted once already 10. PR #100928 stops Turbopack panicking on transient chunk group indices 11.

Most of the merged work is Turbopack internals: a bitset type, parallel batch reads in turbo-persistence, and dropping the ASTs of tree-shaken modules 12 13 14.

One larger change is still open. PR #97625 adds remote consumption to Module Federation behind experimental.turbopackModuleFederation, and last moved on October 27 15.

The comment leaders held. #49279 sits at 145 comments, last touched October 24, and #64921 at 109, last moved October 9 16 17.

Inside the window, #53473, on the no-html-link-for-pages rule and pageExtensions, reached 80 comments on October 29 18. #50163, on a Server Action that reloads the whole app when it sets a cookie, reached 29 the same day 19.

Why included now: No stable, but the 204-response fix is the kind of defect that only shows up under load in production.
Upgrade call — Hold: 16.4.3 remains current. Nothing merged this week is in a release, so there is nothing new to install.

Loading content card…

VS Code

microsoft/vscode published 1.144.0 on October 28 1. No patch followed it. The notes open with a recap of the Agent Host, the Agents window and the Copilot harness default, then list what this version adds on top 2.

Cloud sessions are the headline. You pick Cloud in the Chat view or the Agents window, choose a repository, and the task runs in a managed environment on GitHub's infrastructure while your machine is off 2.

You can reopen a cloud session from the sessions list, or pick it up on github.com and in the GitHub mobile app 2. Cloud sessions need a paid Copilot plan, and they use a separate workspace, so local uncommitted changes do not travel with them 2.

Copilot Fusion is generally available and sits in the model picker as an alternative to choosing a model yourself. It selects the models, the reasoning effort and the execution pattern for each request, and you pick Standard, High or Max to trade quality against cost 2.

Fusion bills every model it uses at that model's standard rate, with a 30% discount through November 30, 2026, and its High and Max tiers need Copilot Pro+, Max, Business or Enterprise 2.

Model comparisons are now on by default for eligible new sessions in the Agents window, run from a folderless chat or a repository with no commits, and are not supported in Dev Containers 2.

Three features arrive in preview or experimental. Image generation sends prompts to GPT Image 2.5 Flare, spends AI credits on top of the conversation model, and switches off when chat.copilot.imageGeneration.model is set to off 2.

Computer Use lets a Copilot harness session see and drive desktop apps on macOS and Windows, after you allow it, and the working set records the harness's file edits so you can keep or undo each one — terminal commands stay out of that record 2.

Assisted permissions are generally available: an LLM scores every tool call for risk and approves the low-risk ones, while anything unclear still waits for you. The mode requires folder isolation, and an organization can disable it 2.

Copilot Memory reached the Copilot harness and is on by default. Repository facts an agent stores are shared with everyone who can access that repository; preferences stay with you, and both are reviewed at github.com/settings/copilot/memory 2.

The Agent Host Protocol reached 1.0, with libraries in six languages and a code agent endpoints command that prints the endpoints of your editor's agent host 2.

Copilot connectors (preview) are GitHub-managed MCP servers for Slack, Notion and Microsoft Learn, work only with the Copilot harness, and need an administrator to enable Editor preview features on Business and Enterprise plans 2.

Two changes matter on a managed install. Organization-managed session defaults now beat your remembered selections: a new chat starts on the organization's model, Fusion tier and permission level, and a blocked permission mode falls back to Manual 2.

Assisted and Allow All now stay visible but disabled when policy restricts them, with an explanation instead of disappearing 2.

Outside the agent surface, the issue reporter became a single page that takes logs and zip archives and can file into other repositories listed in issueReporter.additionalRepositories 2.

On Windows, dialogs opened by terminal commands now appear in front of the window rather than behind it, which terminal.integrated.windowsReparentConsoleWindow controls 2.

Extension publishers can stop storing a personal access token: vsce publish --oidc trades a short-lived GitHub OIDC token for a Marketplace credential valid for up to 15 minutes, needs @vscode/vsce 4.0.2 or later, and does not fall back to a token 2. Azure DevOps global tokens retire on December 1, 2026 2.

The comment leaders held: #519 at 604 comments, last touched October 10, #3130 at 453, and #40239 at 437 20 21 22.

Two threads moved inside the window. #253136, the meta thread for failed agent requests, reached 415 comments on October 28, and #339363, feedback on granular control over Copilot changes, went from 207 to 232 by October 30 23 24.

Two interface requests also climbed: #108264, vertical tabs, at 187 on October 28, and #100335, grouped tabs, at 164 on October 31 25 26.

Why included now: 1.144.0 is the only stable released in the window, and the first version that can run a Copilot task in the cloud while your machine is off.
Upgrade call — Yes: Install 1.144.0. Before you sign in, decide two defaults: Copilot Memory arrives switched on, and Fusion bills every model it routes through.

Loading content card…

React

react/react, the canonical public repository behind the facebook/react whitelist entry, published nothing this week. 19.3.1 from October 14 is still the newest release 27.

Seventeen commits landed on main, and they pair up by subsystem. In Fizz, PR #38071 forwards crossOrigin to the external runtime script, and PR #38059 preserves the external runtime configuration when a prerender resumes 28 29.

In Fiber, PR #38061 pings a throttled retry when a new render cancels its timeout, and PR #37965 fixes a crash when a deleted hidden Activity's suspended data resolves 30 31.

Four commits come from the compiler. PR #37995 preserves signed zero in constant propagation and code generation, and PR #37996 allows ref access in PerformanceObserver and ReportingObserver callbacks 32 33.

PR #36921 preserves AST source offsets and declarator ranges, which keeps diagnostics pointing at the right columns 34. PR #37970 types PanResponder.create to clear a false positive in the React Native lint rule 35.

DevTools took three commits at the weekend, all in how the facade inspects and formats what it finds 36 37. The remaining fixes reach events: PR #38007 calls dispatchNativeEvent when a React Native event target is null 38.

The comment leaders are unchanged: #13991 at 515 comments, last touched July 10, and #11347 at 286 39 40.

The busiest thread that moved was #17256, on a removeChild NotFoundError with fragments, at 41 comments on November 1 41. #35395, on how slow the hooks lint rules are, reached 21 on October 28 42.

Why included now: Seventeen commits landed with nothing published, and the compiler and prerelease fixes are the ones that will reach you first.
Upgrade call — Hold: 19.3.1 remains the version to be on. Nothing from this week is in a release.

Loading content card…

Rust

rust-lang/rust published no release. 1.99.1 from October 16 is still the newest stable 43, and 508 commits landed on main during the week, most of them rollups.

The commit that changes generated code is PR #165133, an LLVM submodule update merged on November 1 that names six compiler issues it should fix 44.

The next toolchain is already in beta: the beta channel carries 1.100.0, so 1.100.0 is what ships next 45.

Three long-running threads decide what that release and the one after it can contain. PR #146369 wants -Zstack-protector stabilized as -Cstack-protector, and it sits at 76 comments, last touched October 29 46.

Issue #43467, the tracking issue for extern types, reached 293 comments on October 26 47. PR #129249, which lints a redundant <T as Into<T>>::into, reached 241 on October 28 48.

Two lesser threads also moved. PR #161149 fixes the maximum Unix domain socket path length on macOS, NetBSD and DragonFlyBSD, at 55 comments on October 28 49.

PR #149543 reduces unreachable-code churn after a todo!(), at 95 comments on October 29 50. The leader is unchanged: PR #112049, the CI experiments thread, holds 2,466 comments and last moved October 21 51.

Why included now: No release, but an LLVM update landed that fixes six compiler bugs, and 1.100.0 is now in beta.
Upgrade call — Hold: 1.99.1 remains the newest stable. The six fixes reach you in a later toolchain, not this week.

Loading content card…

Tailwind CSS

tailwindlabs/tailwindcss published no release. v4.3.3 from July 16 is still the newest stable 52, and npm's latest tag still points at it 53.

Five commits landed on main. One changes compiler output: PR #20627 stops treating !important inside a declaration value as the important flag 54.

The other four are housekeeping: changelog fragments moved into a .changelog/ directory, CI left the retired macos-14 runner image, and a flaky Bun upgrade test was fixed 55.

A stable is still staged. PR #20447, titled "4.3.4", has been open since August 31 and last moved on November 1; nothing has been tagged from it 56.

Twenty-one open issues and pull requests were touched during the week, and the cluster is integration fixes. PR #20649 keeps a single-file @source exact while automatic source detection is on 57.

PR #20639 retries an @import that failed in an earlier compile once the file exists, and PR #20629 loads Lightning CSS lazily so optimize: false works without a native binding 58 59.

Two parser and platform fixes round it out: PR #20630 treats a lone carriage return and a form feed as line breaks, and PR #19774 fixes case-sensitive path comparison in watch mode on Windows 60 61.

The comment leaders hold: #17958 at 38 comments on the missing lightningcss.linux-x64-musl.node, #15005 at 33 on @property inside shadow roots, and #17246 at 27 on --watch pinning two cores 62 63 64.

Why included now: One output-changing fix and an open release pull request that moved on November 1 — the 4.3.4 queue is filling up.
Upgrade call — Hold: v4.3.3 remains the newest stable. If a stray !important in a value is miscompiling for you, the fix is on main and not in a release.

Loading content card…

Quick reference

Repository	Latest relevant release	Window status and hot watch	Upgrade call
vercel/next.js	`16.4.3`, Oct 23 3	No stable; nine canaries to `v16.5.0-canary.36`; 122 commits fixing `204` responses, caught `'use cache'` prerenders and the server-reference transform 7; #49279 has 145 comments and #53473 80 18	Hold
microsoft/vscode	`1.144.0`, Oct 28 1	Cloud sessions need a paid Copilot plan; Copilot Fusion GA bills per model used; model comparisons on by default; Copilot Memory on by default; org defaults beat remembered selections 2	Yes
react/react	`19.3.1`, Oct 14 27	No release; 17 commits across Fizz, Fiber and the compiler; #13991 has 515 comments and did not move, #17256 moved to 41 41	Hold
rust-lang/rust	`1.99.1`, Oct 16 43	No release; 508 commits; LLVM submodule update merged Nov 1; `1.100.0` now in beta; `-Cstack-protector` stabilization at 76 comments 46	Hold
tailwindlabs/tailwindcss	`v4.3.3`, Jul 16 52	No release; five commits, one output-changing; 21 open threads moved; the `4.3.4` release PR last moved Nov 1 56	Hold

References

1
Visual Studio Code 1.144.0 release
github.com
2
Visual Studio Code 1.144 update notes
code.visualstudio.com
3
Next.js v16.4.3 release
github.com
4
npm registry: next dist-tags
registry.npmjs.org
5
Next.js v16.5.0-canary.28 release
github.com
6
Next.js v16.5.0-canary.36 release
github.com
7
Next.js pull request #100159
github.com
8
Next.js pull request #100956
github.com
9
Next.js pull request #100830
github.com
10
Next.js pull request #98726
github.com
11
Next.js pull request #100928
github.com
12
Next.js pull request #100566
github.com
13
Next.js pull request #100620
github.com
14
Next.js pull request #100871
github.com
15
Next.js pull request #97625
github.com
16
Next.js issue #49279
github.com
17
Next.js issue #64921
github.com
18
Next.js issue #53473
github.com
19
Next.js issue #50163
github.com
20
VS Code issue #519
github.com
21
VS Code issue #3130
github.com
22
VS Code issue #40239
github.com
23
VS Code issue #253136
github.com
24
VS Code issue #339363
github.com
25
VS Code issue #108264
github.com
26
VS Code issue #100335
github.com
27
React v19.3.1 release
github.com
28
React pull request #38071
github.com
29
React pull request #38059
github.com
30
React pull request #38061
github.com
31
React pull request #37965
github.com
32
React pull request #37995
github.com
33
React pull request #37996
github.com
34
React pull request #36921
github.com
35
React pull request #37970
github.com
36
React pull request #38067
github.com
37
React pull request #38069
github.com
38
React pull request #38007
github.com
39
React issue #13991
github.com
40
React issue #11347
github.com
41
React issue #17256
github.com
42
React issue #35395
github.com
43
Rust 1.99.1 release
github.com
44
Rust pull request #165133
github.com
45
Rust beta channel manifest
static.rust-lang.org
46
Rust pull request #146369
github.com
47
Rust issue #43467
github.com
48
Rust pull request #129249
github.com
49
Rust pull request #161149
github.com
50
Rust pull request #149543
github.com
51
Rust pull request #112049
github.com
52
Tailwind CSS v4.3.3 release
github.com
53
npm registry: tailwindcss dist-tags
registry.npmjs.org
54
Tailwind CSS pull request #20627
github.com
55
Tailwind CSS pull request #20592
github.com
56
Tailwind CSS pull request #20447
github.com
57
Tailwind CSS pull request #20649
github.com
58
Tailwind CSS pull request #20639
github.com
59
Tailwind CSS pull request #20629
github.com
60
Tailwind CSS pull request #20630
github.com
61
Tailwind CSS pull request #19774
github.com
62
Tailwind CSS issue #17958
github.com
63
Tailwind CSS issue #15005
github.com
64
Tailwind CSS issue #17246
github.com