1
00:00:00,060 --> 00:00:03,600
Have you ever stretched your terminal
across a massive ultrawide monitor,

2
00:00:03,700 --> 00:00:08,460
like, 200 plus columns wide, and then
tried to read a wall of text from Claude?

3
00:00:08,920 --> 00:00:09,260
It is...

4
00:00:10,840 --> 00:00:14,420
mate, it is like watching a tennis match
just to read a single paragraph.

5
00:00:14,920 --> 00:00:18,820
Your eyes are literally tracing back and
forth across three feet of screen space

6
00:00:19,160 --> 00:00:20,140
just to follow one thought.

7
00:00:20,840 --> 00:00:24,740
But at the same time, if you shrink the
window, your code diffs and markdown tables

8
00:00:24,780 --> 00:00:27,120
turn into an unreadable, wrapped disaster.

9
00:00:27,167 --> 00:00:27,647
Right!

10
00:00:27,737 --> 00:00:29,087
Exactly that.

11
00:00:29,167 --> 00:00:32,527
You need the width for code, but you do
not want it for prose.

12
00:00:32,703 --> 00:00:36,527
Well, Jellypod AI brought us a proper
little fix today.

13
00:00:36,653 --> 00:00:42,847
Claude Code release 2.1.282 dropped, and
they added this incredible setting called

14
00:00:43,047 --> 00:00:45,167
maxProseWidth.

15
00:00:45,367 --> 00:00:47,787
Yeah, this is such a slick layout upgrade!

16
00:00:48,487 --> 00:00:52,867
What it does, under the hood, is it caps
the width of Claude's prose in wide

17
00:00:52,907 --> 00:00:55,947
terminals while tables and code blocks
keep the full width.

18
00:00:56,000 --> 00:01:00,480
Wait, so if I set maxProseWidth to, say,
80 in my settings file,

19
00:01:00,496 --> 00:01:02,240
what actually happens to the rendering
engine?

20
00:01:02,250 --> 00:01:06,250
So, the CLI's layout engine splits the
rendering stream by content type.

21
00:01:06,354 --> 00:01:10,170
Paragraphs of natural language get wrapped
at 80 characters,

22
00:01:10,214 --> 00:01:14,890
centered or left aligned neatly, but the
second it hits a triple backtick code block

23
00:01:14,943 --> 00:01:20,570
or a pipe table, boom, it bursts back out
to use every single pixel of your 250

24
00:01:20,616 --> 00:01:21,370
column terminal.

25
00:01:21,715 --> 00:01:24,955
Oh, that is absolute bliss for my eyes.

26
00:01:25,195 --> 00:01:27,095
Like having your cake and eating it too,
mate!

27
00:01:27,495 --> 00:01:31,615
But look, that is not even the biggest
time saver in 2.1.282.

28
00:01:31,975 --> 00:01:34,715
They also added these self healing session
fixes.

29
00:01:34,870 --> 00:01:37,210
Oh man, the redacted thinking block error!

30
00:01:38,110 --> 00:01:39,710
That one was killing me last week.

31
00:01:40,350 --> 00:01:44,730
You'd be mid conversation, deep in a
complex refactor, and suddenly the session

32
00:01:44,750 --> 00:01:49,650
would crash with an invalid data in
redacted thinking block API error.

33
00:01:50,370 --> 00:01:52,630
Every single turn after that would just
fail instantly.

34
00:01:52,708 --> 00:01:55,028
Yeah, it was dropping dead like a stunned
mullet.

35
00:01:55,248 --> 00:01:56,628
But now?

36
00:01:56,668 --> 00:02:01,748
Instead of throwing a terminal killing
panic, the CLI catches that bad payload,

37
00:02:01,798 --> 00:02:05,588
quietly drops the corrupted thinking
blocks from the conversation state,

38
00:02:05,628 --> 00:02:08,308
and retries the API call once
automatically.

39
00:02:08,513 --> 00:02:14,053
It literally heals its own context history
in the background without making you

40
00:02:14,093 --> 00:02:16,573
restart the session or dump your
transcript.

41
00:02:17,213 --> 00:02:22,113
And speaking of broken history, they also
fixed those nasty 400 bad request errors.

42
00:02:22,333 --> 00:02:25,373
Ah, the ones from undecryptable web search
history?

43
00:02:25,375 --> 00:02:25,935
Yes!

44
00:02:26,122 --> 00:02:30,095
If you were running turns through a third
party gateway or proxy,

45
00:02:30,145 --> 00:02:34,335
earlier web search results in your session
history could end up in a format the

46
00:02:34,383 --> 00:02:37,535
Anthropic API couldn't decrypt on
subsequent turns.

47
00:02:38,015 --> 00:02:43,775
2.1.282 detects those unreadable search
entries, strips the bad payload,

48
00:02:43,815 --> 00:02:45,055
and restores the request.

49
00:02:45,310 --> 00:02:47,710
Mm, love a CLI that can clean up after
itself!

50
00:02:48,990 --> 00:02:52,290
While we are under the hood, there are a
few nice quality of life tweaks for

51
00:02:52,330 --> 00:02:53,970
checking your dev environment too, right?

52
00:02:54,083 --> 00:02:55,083
Definitely.

53
00:02:55,155 --> 00:02:59,203
Have you ever spent twenty minutes
wondering why your telemetry or local tracing

54
00:02:59,251 --> 00:03:03,363
wasn't showing up, only to realize an
environment variable in a local project

55
00:03:03,413 --> 00:03:05,603
setting was silently overriding it?

56
00:03:05,805 --> 00:03:06,325
Oh, mate.

57
00:03:08,525 --> 00:03:12,705
I, uh, I might have nearly tanked a client
config last year doing something similar.

58
00:03:13,725 --> 00:03:16,445
Silence is the worst debugging experience.

59
00:03:16,667 --> 00:03:17,147
Right!

60
00:03:17,227 --> 00:03:22,107
So now, when you start up, or when you run
slash status or claude doctor,

61
00:03:22,134 --> 00:03:26,667
it explicitly lists any telemetry off or
ignored variables that are sitting in your

62
00:03:26,711 --> 00:03:27,467
settings files.

63
00:03:27,627 --> 00:03:31,067
It tells you exactly why a setting was
ignored instead of keeping quiet.

64
00:03:31,183 --> 00:03:32,043
Transparency!

65
00:03:32,483 --> 00:03:32,983
Love that.

66
00:03:33,543 --> 00:03:34,843
And what about that Chrome flag?

67
00:03:34,923 --> 00:03:36,703
Something about managed MCP?

68
00:03:36,792 --> 00:03:40,552
Right, allowClaudeInChromeWithManagedMcp.

69
00:03:40,712 --> 00:03:44,712
It lets you run claude chrome even when
your enterprise policy has an exclusive

70
00:03:44,772 --> 00:03:47,032
managed MCP configuration active.

71
00:03:47,192 --> 00:03:50,952
It used to just block Chrome entirely and
give a vague error,

72
00:03:50,992 --> 00:03:54,392
but now it names the policy and gives you
a clean way to allow both.

73
00:03:54,417 --> 00:03:59,697
Fair dinkum, 2.1.282 is just packed with
tiny details that stop you from losing your

74
00:03:59,761 --> 00:04:01,697
mind during a long coding sprint.

75
00:04:01,868 --> 00:04:06,208
From readable text on ultrawides to
sessions that fix their own API errors,

76
00:04:06,728 --> 00:04:08,408
it's a huge quality of life update.

77
00:04:08,458 --> 00:04:13,738
Set your maxProseWidth, update your CLI,
and keep your terminal clean.

78
00:04:13,962 --> 00:04:16,858
Good chatting, mate, catch you next time!