Don't open the dashboard by default

[abh]

This is the same as #268. Don't open the web dashboard by default. I use Serena with Claude Code and opening a browser window each time I open a Claude session is super disruptive.

I'm sure it's a fine feature for some users, but having to disable it on each computer I use makes me doubt everything else about the choices done in this software (which otherwise seems great!). :-)

[MischaPanch]

The dashboard is the best way to see what Serena is doing, whether it's running at all, to which project it's connected and so on. You don't even have to disable it though the config, you can do so through the CLI.

I don't understand how adjusting one line in a yaml once per computer is too much to ask for. If we disable it by default, almost no users would likely be aware that it exists

[MischaPanch]

Also consider that Serena is used a lot outside of Claude code

[abh]

I can appreciate it might make sense in other contexts.

"best way to see what Serena is doing" seems like a very "Serena-developer" centric view of the world. I guess the gist of my request is that I like the results of what Serena is doing, but seeing the lower level operations provides very little value to me and just friction / noise.

When I run grep I don't, by default, get a trace of all IO operations done.

When I use the go language server in Visual Code I don't get a overview of everything the language server is doing.

When I use my email client I don't (by default) get a window with all the connections and protocol interactions it's doing with the IMAP server.

[MischaPanch]

I understand where you're coming from, but we have heard the exact opposite opinion as well: many users were grateful about the dashboard, saying it increased transparency about what's happening. Serena is running on your computer, with access to your code - transparency is important in such a context.

So if we disable it by default, very few users will be aware of it (few read the full readme). If it's enabled by default and not desired, a user just need to do a quick search on how to disable it and do that once. Unless you switch to a new computer all the time, I have a hard time seeing how the latter is a real problem

[opcode81]

When I use my email client I don't (by default) get a window with all the connections and protocol interactions it's doing with the IMAP server.

@abh, what you seem to be completely ignoring is the nature of the application. While your email client has a UI in which it can, at any time, point out problems and present a window with error information, Serena, as an MCP server, otherwise would have no UI to do this. Notably, MCP servers are very different from IMAP servers, as they don't serve a single, well-defined purpose in which only very few types of errors can occur which could be presented by the host application in a standardised, meaningful way. IMAP servers are also not run by the email client (and therefore indirectly by you); they are operated by another entity, which takes care of any errors. MCP servers, however, are run as background processes of other applications (such as Claude Code), and without a UI of our own, a user would be at the mercy of the host application to find out what went wrong in case of errors (or would need to read more documentation to find out where to look for further information, which few users do). Therefore, a way to present immediate feedback is very important.
It's not all sunshine and rainbows for all users. While you may not have had any problems, it is important for users to have a feedback channel - especially when things go wrong.

Users have numerous options to turn it off though - some of which don't even involve editing the config file; you can just add a command line parameter to your launch command.

Presenting feedback by default is what we will continue to do. So this is the end of the discussion.

[salmandeniz]

To disable the default opening of the web dashboard, update your .serena/serena_config.yml file by setting web_dashboard_open_on_launch: false.

[ishipachev]

I think a good compromise here would be to add a note into window how to prevent it from starting every time, basically repeating the same comment above and mentioning the typical config file path.

[opcode81]

@ishipachev the Dashboard already contains a link to our configuration guide as well as a button that allows you to directly edit the configuration and change the setting ("Edit Global Serena Config"). Isn't that sufficient?

[FabianWesner]

I am trying Serena the first time and before I see any benefit, I am already annoyed by this dashboard that pops into my face when I open my Claudes. So the first thing I am doing, is to check how to disable it.

It's just a bad first impression.

The same information, as command, would be cool and consistent to Claude Code's Dev-UX.

arguing why the dashboard is useful (for sure it is!) is completely ignoring the reality of a claude code user who will open a new session every few minutes. no one can convince me that every single time you open claude, start typing, getting interrupted by a browser opening is a useful workflow.

if at all it should open once and immediately tell me "click here if you dont want this to open by default"

[MischaPanch]

I mean, it pretty much does. It has a button "edit config" where you can disable the dashboard. We have many important config settings, there's no good reason to single out this one. Yes, Claude code users might want to disable this (unless they use Serena in http mode), it's just one config setting away

[imqqmi]

When I use this with opencode, as soon the mcp starts I lose focus of opencode just when I'm about to write something. Is it possible to open the webpage without it popping to the front? I'm ok for it to open, just not lose focus on my prompt. I've learned that I can at least use Windows+cursor key down to get rid of it so I don't need to grab the mouse but it's still annoying.