tab-bar-echo-area VS consult-project

Another thing you might consider (this depends on how many tabs you usually keep open, etc.) is not displaying tabs in the tab-bar at all (setq tab-bar-show nil) and displaying them in the echo-area instead. I use a combination of https://github.com/fritzgrabo/tab-bar-echo-area and https://github.com/qaiviq/echo-bar.el to give a consistent but very unobtrusive presentation of the tabs in the echo bar on the bottom right. You can see that in this image -- and my config for it is here.

A combination of these two will probably be super interesting: 1. project-tab-groups 2. tab-bar-echo-area.

Consult-project defines an endpoint for accessing different sources related to the common project workflow. Using Consult's narrowing system, the user is able to access the current project's buffers, project files and all the known projects, in case they want to change projects quickly. Consult-project provides an extension to the default Consult functionality, using the built-in package project.el, defining the functions consult-project and consult-project-other-window. Furthermore, Consult-project only depends on consult, resulting in a lean and simple to maintain functionality.