Thanks for the report.  This and 'Selected context only' are the only 2 checkboxes there that are temporary settings.  Do others think it's appropriate to make both persistent?

1. The whole idea of settings is to persist something. 
2. Things should behave consistently in the same way, or you have to give a hint that this is a special case. 

+1 to Martin's comment. If someone is taking the time to open up Settings, they probably want that change to be permanent...

Some news here? I noticed this bug today to and it is very annoying!!

I share Martin's concern, but I would resolve it towards visually indicating that the setting is not persisted.

but all the other console filtering options via the drop down menu are persisted? 

It wouldn't be quite so annoying if that drop down was reverted to the lovely older network panel filtering UI and violations were added as a specific type

Come on, it's obvious all settings should be persisted.  If there is no time to fix the bug I understand, but what's right and consistent from a usability perspective is not in doubt.

please add this, the new "The SSL certificate used to load xxxx in M66..." warning message is being triggered by the bug with favicons being downloaded for every hashchange. my console is mostly full of repeated warnings
 
https://bugs.chromium.org/p/chromium/issues/detail?id=721635

It's really annoying having to open settings to check "User messages only" every time I open the devtools window because of the thousands of Chrome warnings that we don't even have a way of fixing, like the "font fallback due to slow network" that is triggered regardless of my network speed.

If it's in the settings, should be permanent (consistent with the others).
If it's not permanent, should be outside the settings panel (with fast access, even better).

My preference: persist

This is incredibly annoying, I find myself disabling this feature COUNTLESS times in my day. At this point it's become a time suck and is making me consider moving to Firefox...

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/66a0229065510c32eacf89277f718f8972b13a95

commit 66a0229065510c32eacf89277f718f8972b13a95
Author: Erik Luo <luoe@chromium.org>
Date: Mon Dec 11 23:26:05 2017

DevTools: persist console text filter and sidebar state

Console will remember
- User text typed in the input filter
- Whether the sidebar was open, consistent with Sources and the drawer
- Which top level sidebar filter was selected

Bug:  787620 ,  734088 
Change-Id: Iab109fbf1f459b0c64974c7414dcf3fd24739f11
Reviewed-on: https://chromium-review.googlesource.com/810090
Commit-Queue: Erik Luo <luoe@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523247}
[modify] https://crrev.com/66a0229065510c32eacf89277f718f8972b13a95/third_party/WebKit/LayoutTests/http/tests/devtools/console-sidebar/console-filter-sidebar-expected.txt
[modify] https://crrev.com/66a0229065510c32eacf89277f718f8972b13a95/third_party/WebKit/LayoutTests/http/tests/devtools/console-sidebar/console-filter-sidebar.js
[modify] https://crrev.com/66a0229065510c32eacf89277f718f8972b13a95/third_party/WebKit/LayoutTests/http/tests/devtools/console/console-filter-level-test.js
[modify] https://crrev.com/66a0229065510c32eacf89277f718f8972b13a95/third_party/WebKit/LayoutTests/http/tests/devtools/console/console-filter-test.js
[modify] https://crrev.com/66a0229065510c32eacf89277f718f8972b13a95/third_party/WebKit/Source/devtools/front_end/console/ConsoleSidebar.js
[modify] https://crrev.com/66a0229065510c32eacf89277f718f8972b13a95/third_party/WebKit/Source/devtools/front_end/console/ConsoleView.js

The checkbox has moved to the Console sidebar: https://developers.google.com/web/updates/2017/11/devtools-release-notes#console-sidebar

There you can choose to filter the logs to only user messages (messages emitted via the window.console.* methods)

As of the above commit (in Chrome 65), devtools will persist your sidebar state. So while this feature changed quite a bit, the original request is now satisfied.

awesome