تدريب Shadowing: How to set up Chrome DevTools for agents - تعلم التحدث بالإنجليزية عبر الفيديو

اختر وضع التدريب

كل وضع يفتح غرفة تدريب بملء الشاشة.

80 جمل
إذا كانت الجمل قصيرة أو طويلة جدًا، انقر على Edit لتعديلها.
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.

تنزيل التطبيق

كل ما تحتاجه للتحدث بطلاقة

تقييم النطق بالذكاء الاصطناعيتقييم كل جملة
تدريب IPAأتقن كل صوت
المفرداتابنِ رصيدك من الكلمات
لعبة المفرداتتعلّم أثناء اللعب
FOR YOU

فيديو موصى به

المفردات وملاحظات التحدث لهذا الدرس

هذا الدرس في المحادثة مبني على الفيديو “How to set up Chrome DevTools for agents”. أكثر الكلمات تكرارًا في الفيديو: mcp, server, Chrome, devtools, tool. يحتوي هذا الفيديو على 80 جملة و1139 كلمة للتدرب على الترديد. مدة الكلام 7:57. يتكلم المتحدث بسرعة ثابتة، نحو 143 كلمة في الدقيقة، وهي سرعة مريحة للترديد. 69% فقط من الكلمات ضمن أكثر 3,000 كلمة شيوعًا في الإنجليزية، فالمفردات صعبة نسبيًا.

أهم المفردات في هذا الفيديو

15 كلمة من الفيديو تستحق التعلّم، مع النطق والمعنى:

الكلمةالنطقالمعنى
server اسم/ˈsɝvɚ/خَادُوم m or خَادِم, مُلَقِّم
install فعل/ɪnˈstɔl/رَكَّبَ
dash اسم/ˈdæʃ/شَحْطَة, شَرْطَة
output اسم/ˈaʊtpʊt/مُخرَج
cloud اسم/ˈklaʊ̯d/سَحَاب, غَيْم
connect فعل/kəˈnɛkt/رَبَطَ
token اسم/ˈtoʊkən/رَمْز
tailor اسم/ˈteɪlɚ/خَيَّاط, خَيَّاطَة
remote صفة/ɹəˈməʊt̞/بَعِيد
requirement اسم/ɹɪˈkwaɪɹmənt/مَطْلَب, طَلَب
scope اسم/skəʊp/حَيِّز
instruction اسم/ɪnˈstɹʌkʃən/تَعْلِيم
lighthouse اسم/ˈlaɪthaʊs/مَنَارَة, مَنَار
stable اسم/ˈsteɪ.bəl/حَظِيرَة, اِسْطَبْل
package اسم/ˈpæk.ɪd͡ʒ/صُرَّة, طَرْد

القواعد في هذا الفيديو

أكثر التراكيب التي يستخدمها المتحدث، مع العبارات نفسها من الفيديو:

التركيبفي الفيديو
المضارع التام have/has + اسم المفعول — حدث ماضٍ ما زال له أثر الآنhave installed · have set · have configured
المبني للمجهول be + اسم المفعول — التركيز على ما يحدث لا على من يفعلهis recommended · are used

نطق يحتاج إلى انتباه

يستخدم المتحدث 7 من الصيغ المختصرة، مثل you're, don't, I'm. انطقها بصيغتها القصيرة كما تسمعها.

  • أصوات “sh” و“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/
  • الكلمات الطويلة — انتبه لموضع النبر: 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/

أصوات يجدها متحدثو العربية صعبة:

  • /p/ — ليس /b/: انطقه مع نفخة هواء: output /ˈaʊtpʊt/, aspect /ˈæspɛkt/, scope /skəʊp/, package /ˈpæk.ɪd͡ʒ/, consumption /kənˈsʌmp.ʃən/
  • /v/ — ليس /f/: مع اهتزاز الأوتار الصوتية: server /ˈsɝvɚ/, discover /dɪˈskʌvə/, investigate /ɪnˈvɛs.tə.ɡeɪt/, overview /ˈoʊ.vɚˌvjuː/, observe /əbˈzɜːv/
  • تتابع الصوامت — لا تضف حركة بينها: install /ɪnˈstɔl/, cloud /ˈklaʊ̯d/, connect /kəˈnɛkt/, aspect /ˈæspɛkt/, installed /ɪnˈstɔːld/

كيف تتدرب بهذا الفيديو

  1. استمع إلى الفيديو كاملًا مرة واحدة دون أن تتكلم، ودوّن الكلمات التي لا تعرفها.
  2. ردّد جملة جملة بالسرعة العادية، وكرّر كل جملة حتى يتطابق إيقاعك مع المتحدث.
  3. سجّل صوتك وقارنه بالأصل، مع الانتباه إلى كلمات مثل server, install, dash.

ما هي تقنية التظليل الصوتي؟

التظليل الصوتي (Shadowing) تقنية تعلم لغة مدعومة علمياً، طُورت أصلاً لتدريب المترجمين الفوريين المحترفين. الطريقة بسيطة لكنها قوية: تستمع لصوت إنجليزي أصلي وتكرره فوراً بصوت عالٍ — كظل يتبع المتحدث بتأخير 1-2 ثانية. تُظهر الأبحاث تحسناً كبيراً في دقة النطق والتنغيم والإيقاع وربط الأصوات والاستماع والطلاقة.

تقنية الشادوينغ: اقرأ الدليل الكامل خطوة بخطوة →