Shadowing Practice: How to set up Chrome DevTools for agents - Learn English Speaking with Video

Kies een oefenmodus

Elke modus opent een volledig scherm oefenruimte.

80 zinnen
Als zinnen te kort of te lang zijn, klik op Bewerken om ze aan te passen.
1
Hi, I'm Matthias from the Chrome Developer Relations team.
2
A little while ago, we introduced the Chrome DevTools MCP Server.
3
This episode is a straightforward guide on how to set up the Chrome DevTools MCP Server in Gemini CLI,
4
Cloud and Code Editors like Antigravity and VS Code.
5
We'll look at environment requirements, installing the MCP Server using command line options to tailor it to your needs
6
and how to connect it to a running Chrome instance.
7
For written install instructions for over 15 agentic coding tools, see our README at google slash devtoolsmcp.
8
If you zoned out after I said MCP for the first time and need to catch up, a real brief summary.
9
MCP is a protocol enabling coding agents to talk to external tools like Chrome DevTools.
10
To learn more, watch our intro video about the Chrome DevTools MCP Server first
11
and come back to this video here to start using it.
12
The Chrome DevTools MCP Server is a Node .js application requiring version 20 .19 or newer.
13
To understand which version you have installed on your system in a terminal type node dash dash version.
14
If in your terminal you get output like v25 .1 .0, you're all set.
15
If you get output like command not found, go to the Node .js website and follow the instructions to download and install
16
Node .js for your system.
17
If your version output prints a version number below 20 .19, you need to update
18
Node .js before you can continue.
19
Use the same method you used to install
20
Node .js originally to update it.
21
For example, if you installed
22
Node .js through the Node version manager,
23
nvm, run the command nvm use –lts to download and use the most recent long -term stable version.
24
After verifying your Node .js installation, a few words on scoping.
25
This tutorial will guide you through installing the Chrome DevTools MCP server to a specific
26
Node .js project, instead of installing it for your user.
27
This is recommended, as every MCP server comes with a token cost
28
and you only want to have MCP servers enabled in chat sessions where you actually use them.
29
Additionally, this allows for a project -specific configuration of the MCP server. And lastly,
30
this will persist which MCP servers are used in a project to your repository
31
so your peers can use the same MCP service with the same configuration you do.
32
So when following this tutorial, make sure your current working directory has a package JSON or alternatively create a new one by running npm init.
33
Finally, before you get actually started with the Chrome DevTools MCP server, your coding agent might have built -in browser tools.
34
To not confuse your model with overlapping tools, make sure to disable them before proceeding.
35
Now that your environment meets all requirements, we are going to look into installing the Chrome DevTools MCP server.
36
Let's start with Gemini CLI.
37
Gemini CLI provides a handy install command that you see here.
38
This command invokes Gemini CLI, running the MCP command with the add sub command and the name of the server and its run command as arguments.
39
Run this command to install the Chrome DevTools MCP server to use in your current project with Gemini CLI.
40
For Cloud Code, there is a similar command, just as you see here.
41
Now, the interesting thing about those project scoped commands is that they generate a standardized configuration file.
42
For Gemini CLI, it's at dot gemini slash settings json
43
and for cloud code it's at dot mcp dot json in your project root
44
you can create the same configuration file for vius code for vius code
45
it needs to be at dot vius code slash mcp dot
46
json in your project root directory the same works for other
47
vius code based editors like cursor using the dot cursor slash mcp json file.
48
So when setting up mcp servers, make sure to commit configuration to your repository for any editor that's widely used in your team.
49
When your colleagues do their next git poll, their coding agent will then auto -discover and install mcp servers from the configuration files.
50
Now that we have set up our environment and the server, we can look into tailoring it to our needs.
51
The Chrome DevTools MCP server offers a wide range of tools
52
for various debugging tasks to enable your coding agent to autonomously investigate and fix bugs and validate its own output.
53
There are tools to fill forms, emulate aspects like screen size, location, CPU and network speed,
54
and to measure performance or run lighthouse audits.
55
However, you might not need all the available tools in your project.
56
For example, while debugging a form, you might not care about testing it across various devices, so you don't need the emulation tools.
57
And if you already extensively tested performance, you might not need the performance tools.
58
So you might want to disable them to not pay token costs for their definition.
59
To enable those and other use cases, you can tailor the DevTools MCP server to your needs using configuration flags.
60
The Chrome DevTools MCP server offers over 20 flags to tune various aspects of the server.
61
To get an overview of all available tools and configuration options, see our tool reference and read me at google slash devtools mcp.
62
There are also configuration flags for the previously mentioned example.
63
You can explicitly enable or disable certain tool categories.
64
Let's look into how to apply them.
65
This is our current configuration file.
66
To apply configuration options, create a new entry in the args array.
67
For example, to disable the emulation tools, add this line, dash dash category emulation equals false.
68
Or to use the slim mode with the least token consumption and only navigation and a screenshot tool, use dash dash slip.
69
You can also use the dash dash auto -connect option to let your agent use an already running
70
Chrome instance like this.
71
To use auto -connect, you also need to enable remote debugging in your Chrome instance by going to Chrome Inspect Remote Debugging.
72
Once you have configured the Chrome DevTools MCP server to your liking, or if you're happy with the defaults, you're ready for your first steps.
73
For example, you can now ask your coding agent to run a lighthouse audit for any site.
74
But you can also ask it to debug more complex flows like go to localhost admin
75
and log in with user admin and pass admin.
76
Create a new page titled
77
Hello from DevTools MCP and save it and then live observe your agent testing the full flow.
78
Start with a simple prompt to check if your setup works.
79
If you're running into issues, check our troubleshooting hints at google .devtools .mcp or let us know in the comments below.
80
So, thanks for watching and see you next time.

App downloaden

Alles wat je nodig hebt om vloeiend te spreken

AI UitspraakScoor elke zin
IPA OefeningBeheers elk geluid
WoordenschatBouw je woordenschat op
WoordenspelLeren terwijl je speelt
FOR YOU

Aanbevolen Video

Woordenschat en spreektips bij deze les

Deze spreekles is gebaseerd op de video “How to set up Chrome DevTools for agents”. Deze woorden komen het vaakst terug: mcp, server, Chrome, devtools, tool. Deze video bevat 80 zinnen en 1139 woorden om na te spreken. Het gesproken deel duurt 7:57. De spreker praat in een gelijkmatig tempo van ongeveer 143 woorden per minuut, prettig om te shadowen. Slechts 69% van de woorden hoort bij de 3.000 meest gebruikte Engelse woorden, dus de woordenschat is pittig.

Belangrijke woorden in deze video

15 woorden uit de video die het leren waard zijn, met uitspraak en betekenis:

WoordUitspraakBetekenis
server zelfstandig naamwoord/ˈsɝvɚ/server
install werkwoord/ɪnˈstɔl/installeren, aansluiten
dash zelfstandig naamwoord/ˈdæʃ/streepje, koppelteken
enable werkwoord/ɪˈneɪ.bəl/inschakelen, in staat stellen
output zelfstandig naamwoord/ˈaʊtpʊt/productie
disable werkwoord/dɪsˈeɪbəl/onmogelijk maken
cloud zelfstandig naamwoord/ˈklaʊ̯d/wolk
connect werkwoord/kəˈnɛkt/verbinden
token zelfstandig naamwoord/ˈtoʊkən/teken
tailor zelfstandig naamwoord/ˈteɪlɚ/kleermaker, kleermaakster
aspect zelfstandig naamwoord/ˈæspɛkt/aspect
remote bijvoeglijk naamwoord/ɹəˈməʊt̞/verwijderd, afgelegen
requirement zelfstandig naamwoord/ɹɪˈkwaɪɹmənt/vereiste, plicht
scope zelfstandig naamwoord/skəʊp/domein, bereik
instruction zelfstandig naamwoord/ɪnˈstɹʌkʃən/onderwijs

Phrasal verbs die je zult horen

WoordUitspraakBetekenis
set up werkwoord/ˌsɛt ˈʌp/bereiden, voorbereiden

Grammatica in deze video

De structuren die de spreker het meest gebruikt, met de exacte woorden uit de video:

StructuurIn de video
Present perfect have/has + voltooid deelwoord — iets uit het verleden dat nu nog telthave installed · have set · have configured
Lijdende vorm be + voltooid deelwoord — het gaat om wat er gebeurt, niet om wie het doetis recommended · are used

Uitspraak om op te letten

De spreker gebruikt 7 samentrekkingen en verkorte vormen, zoals you're, don't, I'm. Spreek ze kort uit, zoals je ze hoort.

  • De klanken “sh” en “zh”: configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, dash /ˈdæʃ/, instruction /ɪnˈstɹʌkʃən/, consumption /kənˈsʌmp.ʃən/, installation /ˌɪn.stəˈleɪ.ʃən/
  • Lange woorden — let op de klemtoon: configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, directory /dɪˈɹɛktəɹi/, investigate /ɪnˈvɛs.tə.ɡeɪt/, installation /ˌɪn.stəˈleɪ.ʃən/, navigation /nævɪˈɡeɪʃən/

Klanken die Nederlandstaligen lastig vinden:

  • Stemhebbende eindmedeklinker — /b/, /d/, /g/, /z/, /v/ niet verscherpen: node /noʊd/, cloud /ˈklaʊ̯d/, installed /ɪnˈstɔːld/, package /ˈpæk.ɪd͡ʒ/, bug /bʌɡ/
  • /æ/ — opener dan de Nederlandse “e”: dash /ˈdæʃ/, admin /ˈædˌmɪn/, aspect /ˈæspɛkt/, package /ˈpæk.ɪd͡ʒ/, navigation /nævɪˈɡeɪʃən/
  • /g/ — een harde plofklank, geen Nederlandse “g”: configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, investigate /ɪnˈvɛs.tə.ɡeɪt/, bug /bʌɡ/, navigation /nævɪˈɡeɪʃən/, colleague /ˈkɒliːɡ/

Zo oefen je met deze video

  1. Luister de hele video één keer zonder te spreken en noteer de woorden die je niet kent.
  2. Spreek zin voor zin na op normale snelheid en herhaal elke zin tot je ritme gelijk is aan dat van de spreker.
  3. Neem jezelf op en vergelijk met het origineel; let daarbij op woorden als server, install, dash.

Wat is de Shadowing-techniek?

Shadowing is een wetenschappelijk onderbouwde taalleermethode die oorspronkelijk is ontwikkeld voor professionele tolkentraining en gepopulariseerd door polyglot Dr. Alexander Arguelles. De methode is eenvoudig maar krachtig: je luistert naar native Engelse audio en herhaalt het onmiddellijk hardop — als een schaduw die de spreker volgt met slechts 1–2 seconden vertraging. In tegenstelling tot passief luisteren of grammaticadrills, dwingt shadowing je hersenen en mondspieren om echte spraakpatronen tegelijkertijd te verwerken en te reproduceren. Onderzoek toont aan dat het de uitspraaknauwkeurigheid, intonatie, ritme, verbonden spraak, luisterbegrip en spreekvaardigheid aanzienlijk verbetert — waardoor het een van de meest effectieve methoden is voor IELTS Speaking-voorbereiding en echte Engelse communicatie.

Shadowing-techniek: lees de volledige stap-voor-stap-gids →