1
00:00:00,140 --> 00:00:04,540
Ever had six terminal tabs open, each
running its own Claude session,

2
00:00:04,940 --> 00:00:07,220
and lost track of which one was fixing
what?

3
00:00:08,080 --> 00:00:09,080
Yeah, me too.

4
00:00:10,120 --> 00:00:14,360
This is The Claude Code Changelog, brought
to you by Jellypod AI.

5
00:00:15,080 --> 00:00:15,600
I'm Lachlan.

6
00:00:16,190 --> 00:00:16,910
And I'm James.

7
00:00:17,470 --> 00:00:22,250
Last time we covered 2.1.302 and the
client side auto mode classifier.

8
00:00:22,870 --> 00:00:26,950
Today is a bigger architectural shift: the
redesigned Claude Projects,

9
00:00:27,170 --> 00:00:29,610
rolling out in public beta for Pro and Max
accounts.

10
00:00:30,150 --> 00:00:34,210
You'll find it at claude.ai/code, in the
Code tab of the desktop app,

11
00:00:34,530 --> 00:00:35,290
and in the mobile app.

12
00:00:35,990 --> 00:00:39,330
It's rolling out gradually, starting with
people who have run cloud sessions,

13
00:00:39,790 --> 00:00:43,250
and existing chat projects are being moved
across as of mid October.

14
00:00:43,830 --> 00:00:47,750
It is not in the terminal CLI, the VS Code
extension, or on Bedrock,

15
00:00:47,870 --> 00:00:48,890
Vertex or Foundry.

16
00:00:49,578 --> 00:00:54,338
So the old idea of a project, a folder of
chats and uploaded files,

17
00:00:54,738 --> 00:00:55,198
is gone.

18
00:00:55,918 --> 00:01:01,138
Now a project is one ongoing coordinator
session, a sort of chief of staff.

19
00:01:01,798 --> 00:01:06,118
You hand it a goal, it breaks the goal up,
and it dispatches worker threads.

20
00:01:07,018 --> 00:01:13,038
Each thread is a full, separate Claude
Code cloud session on its own Ubuntu 24.04

21
00:01:13,098 --> 00:01:18,598
container, with 4 vCPUs, 16 gigs of RAM
and 30 gigs of disk.

22
00:01:19,178 --> 00:01:24,158
Its own context window, its own git
branch, it runs tests, and it opens pull

23
00:01:24,218 --> 00:01:24,738
requests.

24
00:01:25,458 --> 00:01:28,918
There's a cap of 200 new threads per day
across your projects.

25
00:01:29,845 --> 00:01:32,705
The practical upside is that you can drop
a backlog of issues,

26
00:01:32,885 --> 00:01:36,525
or a refactor that spans several repos,
into the project conversation.

27
00:01:37,085 --> 00:01:40,905
Claude assigns a thread per task or per
repository, writes the code,

28
00:01:41,165 --> 00:01:44,645
runs CI, and opens draft PRs while your
laptop is closed.

29
00:01:45,345 --> 00:01:46,745
No local worktree juggling.

30
00:01:47,340 --> 00:01:48,360
But here's the catch.

31
00:01:48,900 --> 00:01:51,960
Every thread is a full session, and they
run in parallel.

32
00:01:52,400 --> 00:01:56,600
So a project burns through your rolling
five hour and weekly limits much faster than

33
00:01:56,640 --> 00:01:57,860
a single CLI run.

34
00:01:58,380 --> 00:02:02,020
And a new project defaults to running
every thread on Opus at high effort.

35
00:02:02,822 --> 00:02:05,562
Which is a bit like leaving every tap in
the house running.

36
00:02:06,462 --> 00:02:07,662
So, setup first.

37
00:02:08,182 --> 00:02:14,762
Go to claude.ai/code, hit Projects, then
New project, and attach your GitHub

38
00:02:14,822 --> 00:02:15,322
repos.

39
00:02:15,822 --> 00:02:20,122
That needs the Claude GitHub App with push
access, on github.com.

40
00:02:21,082 --> 00:02:26,062
Next, open Project settings, then Memory,
then Project instructions.

41
00:02:26,542 --> 00:02:28,382
You get up to 16,000 characters.

42
00:02:28,982 --> 00:02:33,902
Put in the starting branch, the
verification commands like make test and make lint,

43
00:02:34,362 --> 00:02:35,522
and the fallback rules.

44
00:02:36,042 --> 00:02:40,482
For example: if an API key or secret is
missing, stop immediately,

45
00:02:40,782 --> 00:02:42,082
do not mock or guess.

46
00:02:42,742 --> 00:02:46,342
And: do not merge or force push without
confirmation.

47
00:02:47,282 --> 00:02:52,262
Then go to Project settings, General, and
dial down Thread model and Thread effort.

48
00:02:53,022 --> 00:02:56,782
Sonnet at low or medium effort is a
sensible start for routine tickets.

49
00:02:57,442 --> 00:02:59,442
You can also throttle in the conversation
itself.

50
00:03:00,042 --> 00:03:03,362
Tell it, propose threads and wait for my
go ahead before starting them.

51
00:03:03,742 --> 00:03:05,962
Or, run at most two threads at a time.

52
00:03:06,867 --> 00:03:10,607
And if a task needs something the cloud
can't reach, like a VPN,

53
00:03:10,807 --> 00:03:16,307
a local database, or a hardware emulator,
click the plus button and pick Work

54
00:03:16,367 --> 00:03:18,647
locally, or just say so in the prompt.

55
00:03:19,467 --> 00:03:22,647
That thread gets routed to your machine
through Remote Control.

56
00:03:23,227 --> 00:03:28,827
You'll need Claude Code 2.1.280 or later,
running claude remote-control with the

57
00:03:28,947 --> 00:03:30,167
spawn worktree option.

58
00:03:30,788 --> 00:03:33,948
For files, use the Library tab under
Overview.

59
00:03:34,228 --> 00:03:38,988
It takes up to 100 files, 2 gigabytes
total, and 480 megabytes per file.

60
00:03:39,568 --> 00:03:43,748
The New project modal skips anything over
30 megabytes, so don't upload big stuff

61
00:03:43,808 --> 00:03:43,988
there.

62
00:03:45,002 --> 00:03:45,762
Now the gotchas.

63
00:03:46,362 --> 00:03:48,662
Sandboxes pause between turns.

64
00:03:49,142 --> 00:03:54,082
If an idle container can't be resumed,
Claude clones fresh from GitHub,

65
00:03:54,562 --> 00:03:56,242
so uncommitted work is gone.

66
00:03:56,822 --> 00:04:00,582
On long tasks, tell it to commit and push
work in progress.

67
00:04:01,540 --> 00:04:02,440
Two cost traps.

68
00:04:02,940 --> 00:04:07,540
First, threads watching an open pull
request wake up on their own to fix CI failures

69
00:04:07,600 --> 00:04:08,780
or answer review comments.

70
00:04:09,420 --> 00:04:12,580
Second, if a running thread hits your
usage limit, it doesn't abort.

71
00:04:12,960 --> 00:04:16,920
It pauses and resumes the moment the limit
resets, so it can quietly eat your next

72
00:04:16,979 --> 00:04:17,740
five hour window.

73
00:04:18,380 --> 00:04:21,580
If things run away, use Pause in Project
settings, General.

74
00:04:22,240 --> 00:04:26,240
And resuming an idle thread after its one
hour prompt cache has expired re-reads the

75
00:04:26,300 --> 00:04:29,700
whole history, so for a new subtask, a
fresh thread is cheaper.

76
00:04:30,728 --> 00:04:33,548
One more: it's strictly single user for
now.

77
00:04:34,248 --> 00:04:37,648
Threads can't be shared with teammates or
moved between projects.

78
00:04:38,330 --> 00:04:39,250
A few smaller things.

79
00:04:39,750 --> 00:04:45,450
In 2.1.302, the design sync and design
login commands now show a notice that

80
00:04:45,550 --> 00:04:49,090
standalone Claude Design closes by
December 14, 2026.

81
00:04:49,730 --> 00:04:53,610
The Claude in Chrome instructions moved
within the system prompt so new sessions can

82
00:04:53,650 --> 00:04:55,190
read them from the shared prompt cache.

83
00:04:55,910 --> 00:05:01,310
In 2.1.301, vim mode gained the percent
motion, which jumps to the matching bracket,

84
00:05:01,570 --> 00:05:03,390
alone or with d, c or y.

85
00:05:03,910 --> 00:05:08,050
And both releases fixed worktrees and git
plugins that broke or kept re-cloning when

86
00:05:08,090 --> 00:05:10,210
git defaults to the reftable ref format.

87
00:05:10,810 --> 00:05:11,450
Cheers for listening.

88
00:05:11,810 --> 00:05:15,310
Set your thread model before your first
project, and we'll catch you next time.