1
00:00:00,000 --> 00:00:01,277
Welcome to the show, everyone!

2
00:00:01,317 --> 00:00:05,036
I'm Lachlan Reed, coming to you from my
backyard shed, and I'm joined by James

3
00:00:05,082 --> 00:00:05,758
Turner.

4
00:00:05,785 --> 00:00:09,517
We've got a massive tech hook for you
today, and thanks to Jellypod to help make

5
00:00:09,565 --> 00:00:11,519
this daily show a reality.

6
00:00:11,546 --> 00:00:15,840
If you've been running Claude Code for
agentic workflows, you know the absolute gut

7
00:00:15,893 --> 00:00:19,836
punch of hitting API rate limits right in
the middle of a complex deploy.

8
00:00:19,964 --> 00:00:23,197
Well, Anthropic just threw us a massive
lifeline.

9
00:00:24,000 --> 00:00:25,598
Oh, they absolutely did.

10
00:00:26,050 --> 00:00:29,361
We are talking about true multi-model
resilience now.

11
00:00:29,501 --> 00:00:34,479
You can now configure up to three fallback
models in strict order using the new

12
00:00:34,639 --> 00:00:40,561
`fallbackModel` setting in your config
file, or just append the `--fallback-model`

13
00:00:40,641 --> 00:00:41,760
flag on the fly.

14
00:00:41,973 --> 00:00:48,477
If Claude 3.5 Sonnet starts throwing 429
rate-limit errors or peak-traffic

15
00:00:48,525 --> 00:00:53,030
overloads, your agentic terminal loop will
immediately fall back to your secondary

16
00:00:53,137 --> 00:00:55,906
or tertiary choice without crashing the
run.

17
00:00:56,000 --> 00:00:57,519
That is fair dinkum brilliant.

18
00:00:58,481 --> 00:01:03,048
No more babysitting a script only for it
to fall over at 2:00 AM because of API

19
00:01:03,099 --> 00:01:03,849
congestion.

20
00:01:03,989 --> 00:01:09,131
You could literally set Sonnet as primary,
fallback to Haiku for speed,

21
00:01:09,151 --> 00:01:11,450
and then maybe keep an older model as a
safety net.

22
00:01:11,610 --> 00:01:12,650
It's beautiful.

23
00:01:12,850 --> 00:01:16,887
But wait, James, if we're falling back to
models that have deep reasoning

24
00:01:16,949 --> 00:01:20,649
capabilities, isn't that going to run up
the bill with thinking tokens?

25
00:01:20,689 --> 00:01:23,961
[questioning tone] It definitely can,
which brings us to the second major

26
00:01:24,007 --> 00:01:26,927
configuration change: thinking toggles.

27
00:01:27,087 --> 00:01:31,330
For workflows where you do not need deep
chain-of-thought processing,

28
00:01:31,350 --> 00:01:36,124
you can completely disable thinking by
setting `MAX_THINKING_TOKENS=0` in your

29
00:01:36,164 --> 00:01:40,083
environment, or simply run `--thinking
disabled`.

30
00:01:41,000 --> 00:01:42,199
Disable it entirely?

31
00:01:43,384 --> 00:01:45,963
That makes a lot of sense for simple,
structured tasks.

32
00:01:46,027 --> 00:01:51,327
Like, if I'm just regex-parsing some logs,
I don't need Claude spending five seconds

33
00:01:51,367 --> 00:01:55,167
and thousands of tokens pondering the
meaning of life before it writes the script.

34
00:01:55,380 --> 00:01:58,208
It's a huge latency and cost saver.

35
00:01:59,000 --> 00:01:59,717
Exactly.

36
00:02:00,485 --> 00:02:04,517
Save the heavy thinking for complex logic,
and bypass it for routine file

37
00:02:04,570 --> 00:02:05,475
manipulations.

38
00:02:05,655 --> 00:02:10,518
And speaking of file manipulations, the
latest security prompt updates are a massive

39
00:02:10,582 --> 00:02:10,918
deal.

40
00:02:11,009 --> 00:02:14,749
Claude Code now has explicit guardrails
around critical system files.

41
00:02:14,962 --> 00:02:20,509
It prompts for explicit user permission
before touching things like your SSH keys,

42
00:02:20,589 --> 00:02:23,624
shell profiles, or global env files.

43
00:02:24,000 --> 00:02:28,715
No worries about an agent accidentally
nuking your `.bashrc` or sending your private

44
00:02:28,779 --> 00:02:30,474
keys off to a remote server then.

45
00:02:31,208 --> 00:02:34,033
That's a massive relief for local
execution.

46
00:02:34,143 --> 00:02:38,793
And while we're on local workflows, have
you seen the new `/btw` command?

47
00:02:38,953 --> 00:02:42,716
It copies the last command output directly
to your system clipboard.

48
00:02:43,000 --> 00:02:44,920
Oh, the clipboard copy!

49
00:02:45,308 --> 00:02:49,796
It's such a simple quality-of-life
addition, but not having to drag-select text in a

50
00:02:49,863 --> 00:02:52,354
messy terminal window is a game-changer.

51
00:02:52,454 --> 00:02:57,073
You just type `/btw` and paste it right
into your documentation or Slack.

52
00:02:58,000 --> 00:03:00,519
It's the little things that keep us sane,
mate.

53
00:03:00,607 --> 00:03:04,956
Keep those fallbacks configured and your
system files locked down.

54
00:03:05,116 --> 00:03:07,672
That's all for today's quick tech
breakdown.

55
00:03:07,779 --> 00:03:09,034
Catch you next time!

56
00:03:10,000 --> 00:03:10,398
See ya!