The next big update will concern changing the browser engine. After the update BAS will use CEF only for the interface. As the browser for automation it will use a patched version of Chromium with some Chrome features.
Pros:
Extension support.
The browser will look as authentic as possible. Some browser apis are missing in CEF, and they had to be added manually.
Less time for browser version updates in the future. During the last update, 80% of the bugs were related specifically to CEF.
It may be possible to make automation of the system browser, but without changing the fingerprint.
There may be a fork of puppeteer with FingerprintSwitcher support.
Compatibility of BAS profiles with system browser profiles.
Cons:
A long time for the update. The optimistic estimate is 2 months. A more realistic one is 3 months. Part of the automation code will have to be rewritten.
Possible bugs when changing the engine. I will do everything to avoid this, but the amount of changes is too large for nothing to break.
Possible change or disabling of some actions. It is currently planned that old scripts will be transferred to the new version without changes, but if such are needed, a detailed instruction will be created.
Unforeseen circumstances. During development anything can happen, up to rolling back to CEF. But such a scenario is unlikely.
At the same time, during the update, new modules and interface improvements will be released.
The old version (with CEF) will only work in old BAS versions; in new versions the CEF-based browser will be unavailable.
Extension support; a far more authentic browser; less time for future version updates; possible system-browser automation and a puppeteer fork with FingerprintSwitcher; profile compatibility
Long update (~2–3 months, code rewrite); possible bugs during the engine switch; some actions may change; unforeseen circumstances (rollback to CEF unlikely)