Skip to content

feat: --slim mode for maximum token savings#958

Merged
OrKoN merged 2 commits intomainfrom
orkon/minimal
Feb 23, 2026
Merged

feat: --slim mode for maximum token savings#958
OrKoN merged 2 commits intomainfrom
orkon/minimal

Conversation

@OrKoN
Copy link
Collaborator

@OrKoN OrKoN commented Feb 13, 2026

  • navigate
  • run js
  • take screenshot

That's it. Basic functionality for a low (~368) token price.

@OrKoN OrKoN requested a review from natorion February 13, 2026 18:00
@OrKoN
Copy link
Collaborator Author

OrKoN commented Feb 13, 2026

@natorion wdyt?

@OrKoN OrKoN force-pushed the orkon/minimal branch 2 times, most recently from 28b545d to 3396207 Compare February 13, 2026 18:26
@OrKoN OrKoN marked this pull request as ready for review February 16, 2026 08:23
@OrKoN OrKoN marked this pull request as draft February 16, 2026 08:24
@natorion
Copy link
Contributor

A few thoughts:

  • I like the concept
  • Should it be called "lean" instead of "minimal"?
  • Is error reporting of evaluate_script sufficient for any common AI agent to act on the errors? Or will this just produce a frustrating experience?

@OrKoN
Copy link
Collaborator Author

OrKoN commented Feb 16, 2026

I like --lean!

@OrKoN OrKoN changed the title feat: --minimal mode with maximum token savings feat: --slim mode for maximum token savings Feb 20, 2026
@OrKoN
Copy link
Collaborator Author

OrKoN commented Feb 20, 2026

@natorion updated to slim with the reference generation (slim mode consumes 359 tokens).

@natorion
Copy link
Contributor

One more thing: Should we mention different tool categories and modes in the general Chrome DevTools Skill?

@OrKoN
Copy link
Collaborator Author

OrKoN commented Feb 20, 2026

One more thing: Should we mention different tool categories and modes in the general Chrome DevTools Skill?

let me think about it a bit

@OrKoN
Copy link
Collaborator Author

OrKoN commented Feb 20, 2026

One more thing: Should we mention different tool categories and modes in the general Chrome DevTools Skill?

let me think about it a bit

so I think we do not need a skill since the mode is low complexity (most complexity lies in code generation and interpreting screenshots for which generic skills can be used). I also worry that combining two modes in one skill would leave to confusion. Any better ideas?

@OrKoN OrKoN requested a review from matthiasrohmer February 20, 2026 14:14
@natorion
Copy link
Contributor

One more thing: Should we mention different tool categories and modes in the general Chrome DevTools Skill?

let me think about it a bit

so I think we do not need a skill since the mode is low complexity (most complexity lies in code generation and interpreting screenshots for which generic skills can be used). I also worry that combining two modes in one skill would leave to confusion. Any better ideas?

I was mostly thinking to say: In case you don't find tools mentioned in the skills, make sure that there are tooling categories that are not default or something. This way the agent can start fixing the mcp configs.

@OrKoN
Copy link
Collaborator Author

OrKoN commented Feb 23, 2026

Updated the skill to exclude --slim.

@OrKoN OrKoN marked this pull request as ready for review February 23, 2026 11:49
@OrKoN OrKoN added this pull request to the merge queue Feb 23, 2026
Merged via the queue into main with commit c402b43 Feb 23, 2026
30 of 33 checks passed
@OrKoN OrKoN deleted the orkon/minimal branch February 23, 2026 14:47
github-merge-queue bot pushed a commit that referenced this pull request Feb 25, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.18.0](chrome-devtools-mcp-v0.17.3...chrome-devtools-mcp-v0.18.0)
(2026-02-24)


### 🎉 Features

* `--slim` mode for maximum token savings
([#958](#958))
([c402b43](c402b43))
* add a new skill for accessibility debugging and auditing with Chrome
DevTools MCP.
([#1002](#1002))
([b0c6d04](b0c6d04))
* add experimental screencast recording tools
([#941](#941))
([33446d4](33446d4))
* add skill to debug and optimize LCP
([#993](#993))
([2cd9b95](2cd9b95))
* add storage-isolated browser contexts
([#991](#991))
([59f6477](59f6477))
* add take_memory_snapshot tool
([#1023](#1023))
([7ffdc5e](7ffdc5e))
* support any-match text arrays in wait_for
([#1011](#1011))
([496ab1b](496ab1b))
* support type_text
([#1026](#1026))
([b5d01b5](b5d01b5))


### 🛠️ Fixes

* detect X server display on Linux
([#1027](#1027))
([1746ed9](1746ed9))


### ♻️ Chores

* cleanup string and structured console formatters
([#1005](#1005))
([0d78685](0d78685))
* extract version in a seprate file
([#1032](#1032))
([0106865](0106865))
* move emulation settings to context
([#1000](#1000))
([bc3c40e](bc3c40e))
* optimize slim tool descriptions and params
([#1028](#1028))
([ca6635d](ca6635d))
* simplify JavaScript code examples, update code block language, and
refine descriptions in a11y debugging skill documentation.
([#1009](#1009))
([5cedcaa](5cedcaa))
* types for JSON output of IssueFormatter
([#1007](#1007))
([9ef4479](9ef4479))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
wolfib pushed a commit to wolfib/chrome-devtools-mcp that referenced this pull request Mar 10, 2026
- navigate
- run js
- take screenshot

That's it. Basic functionality for a low (~368) token price.
wolfib pushed a commit to wolfib/chrome-devtools-mcp that referenced this pull request Mar 10, 2026
🤖 I have created a release *beep* *boop*
---


##
[0.18.0](ChromeDevTools/chrome-devtools-mcp@chrome-devtools-mcp-v0.17.3...chrome-devtools-mcp-v0.18.0)
(2026-02-24)


### 🎉 Features

* `--slim` mode for maximum token savings
([ChromeDevTools#958](ChromeDevTools#958))
([c402b43](ChromeDevTools@c402b43))
* add a new skill for accessibility debugging and auditing with Chrome
DevTools MCP.
([ChromeDevTools#1002](ChromeDevTools#1002))
([b0c6d04](ChromeDevTools@b0c6d04))
* add experimental screencast recording tools
([ChromeDevTools#941](ChromeDevTools#941))
([33446d4](ChromeDevTools@33446d4))
* add skill to debug and optimize LCP
([ChromeDevTools#993](ChromeDevTools#993))
([2cd9b95](ChromeDevTools@2cd9b95))
* add storage-isolated browser contexts
([ChromeDevTools#991](ChromeDevTools#991))
([59f6477](ChromeDevTools@59f6477))
* add take_memory_snapshot tool
([ChromeDevTools#1023](ChromeDevTools#1023))
([7ffdc5e](ChromeDevTools@7ffdc5e))
* support any-match text arrays in wait_for
([ChromeDevTools#1011](ChromeDevTools#1011))
([496ab1b](ChromeDevTools@496ab1b))
* support type_text
([ChromeDevTools#1026](ChromeDevTools#1026))
([b5d01b5](ChromeDevTools@b5d01b5))


### 🛠️ Fixes

* detect X server display on Linux
([ChromeDevTools#1027](ChromeDevTools#1027))
([1746ed9](ChromeDevTools@1746ed9))


### ♻️ Chores

* cleanup string and structured console formatters
([ChromeDevTools#1005](ChromeDevTools#1005))
([0d78685](ChromeDevTools@0d78685))
* extract version in a seprate file
([ChromeDevTools#1032](ChromeDevTools#1032))
([0106865](ChromeDevTools@0106865))
* move emulation settings to context
([ChromeDevTools#1000](ChromeDevTools#1000))
([bc3c40e](ChromeDevTools@bc3c40e))
* optimize slim tool descriptions and params
([ChromeDevTools#1028](ChromeDevTools#1028))
([ca6635d](ChromeDevTools@ca6635d))
* simplify JavaScript code examples, update code block language, and
refine descriptions in a11y debugging skill documentation.
([ChromeDevTools#1009](ChromeDevTools#1009))
([5cedcaa](ChromeDevTools@5cedcaa))
* types for JSON output of IssueFormatter
([ChromeDevTools#1007](ChromeDevTools#1007))
([9ef4479](ChromeDevTools@9ef4479))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants