WEBVTT

00:00:00.140 --> 00:00:04.119
So, you can build custom agents.
That's not all you can tweak

00:00:04.199 --> 00:00:06.959
about these agents
and chat sessions though.

00:00:07.519 --> 00:00:11.159
There also are prompt files,
chat instructions,

00:00:11.239 --> 00:00:15.179
MCP servers, toolsets,
and chat settings at the point of time

00:00:15.199 --> 00:00:18.840
I'm recording this. And as always,
chances are high

00:00:18.879 --> 00:00:22.499
time. Now,
I'll get back to some of the more

00:00:22.500 --> 00:00:26.319
But for now,
it's worth pointing out the chat settings

00:00:26.379 --> 00:00:30.000
up the regular settings,
which I showed you before, but focused on

00:00:30.059 --> 00:00:33.119
the, well, AI chat related settings.

00:00:33.200 --> 00:00:36.979
You could have searched manually for chat
in your VS

00:00:37.040 --> 00:00:40.939
Code settings, but that's, of course,
a quicker way of getting to the exact

00:00:41.020 --> 00:00:44.979
settings that allow you to change the
behavior of this chat mode and of these

00:00:45.119 --> 00:00:48.720
agents. Also worth noting
is this button here,

00:00:48.799 --> 00:00:52.360
which opens this full screen chat mode
here,

00:00:52.420 --> 00:00:56.299
which simply is the same as
if I would have manually dragged this

00:00:56.419 --> 00:00:58.879
all the way over here
and then closed my editor.

00:00:58.879 --> 00:01:02.859
But that's a quick way of doing it. So
if you need more space for your chat

00:01:02.959 --> 00:01:06.759
and the other sessions so
that you can quickly jump around, that is

00:01:06.840 --> 00:01:10.599
how you can do it. Now,
when it comes to these sessions,

00:01:10.720 --> 00:01:13.979
through your sessions
if you've got many of them,

00:01:15.860 --> 00:01:19.819
And inside of a chat session,
you can also regenerate a

00:01:19.879 --> 00:01:21.999
response if you're not happy with it.

00:01:22.040 --> 00:01:25.979
So you can retry it so
that the agent has another chance of doing

00:01:26.019 --> 00:01:29.779
its job, no matter if it was an agent
that wrote code or answered a

00:01:29.839 --> 00:01:33.199
question. Or you can restore to the last

00:01:33.400 --> 00:01:36.319
checkpoint,
and that's worth taking a closer

00:01:36.360 --> 00:01:38.459
look.