nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sometimes it just exits / Error during MCP server shutdown

rmoriz

Using:

Rovo Dev CLI: 0.8.0
Operating System: Darwin 24.5.0 (arm64)
Git: git version 2.39.5 (Apple Git-154)

Sometimes the cli just exists without a message or error code.

the last message within the log before this happens:

The code section with the closest match has been expanded in the file for review. 
2025-06-30 23:41:55.382 | INFO | - 
2025-06-30 23:42:15.924 | WARNING | - Error during MCP server shutdown: unhandled errors in a TaskGroup (1 sub-exception)

Comments

Jovana Dunisijevic

Hi @rmoriz

Thank you for reporting this issue and including your environment details and the log snippet.

Possible causes:

There could be a misconfiguration in your MCP server setup, or a compatibility issue with your current OS version (Darwin 24.5.0, arm64).
If you are running a custom or local MCP server, ensure it is running and healthy before starting the CLI. You can check your MCP configuration in ~/.rovodev/mcp.json .

Troubleshooting steps:

Update to the latest version:
Ensure you are running the latest version of Rovo Dev CLI, as bug fixes and stability improvements are released regularly.
Check your MCP server configuration:
Run acli rovodev mcp to open your MCP config file and verify the settings.
Review the full log file:
Run acli rovodev log to open the log file (~/.rovodev/rovodev.log) and look for any additional error messages or stack traces before the shutdown warning.
Try a clean restart:
Fully close all CLI and MCP server processes, then restart your terminal and try again.
If using Docker or a containerized MCP server:
Make sure the container remains running for the duration of your CLI session.

If the issue persists, please submit your log file and details to Atlassian support using the /feedback command in the CLI, or via the support portal: Bug report - Rovo Dev in CLI. This will help the team investigate further and provide a targeted fix.

I hope this helps!

Kindest regards,

Jov

rmoriz

Thanks for your reply, however I do not use a custom MCP or any non-standard configuration. I use Rovo Dev out of the box with some tweaked settings regarding the permission of running external scripts, nothing MCP related. Is there a way to increase log verbosity? The last line in the log is the only relevant log entry.

Jovana Dunisijevic

Hey @rmoriz

Sorry about that confusion!

To answer your question about verbosity:

Currently, Rovo Dev CLI does not provide a built-in option to increase log verbosity via a command-line flag or configuration setting. But you can still view the full log file with the instructions I shared above.

However, if you need some special support with the logs or want to request enhanced logging/verbosity features, please do submit your feedback or a feature request using the /feedback command in Interactive Mode, or via the support portal!

The team def appreciates all the feedback we can get!

Kindest regards,

Jov

Welcome!

It looks like you're new here. Sign in or register to get started.