Skip to content

[Bug]: When -mcp-stdio is used, control the output #3275

@JerryNixon

Description

@JerryNixon

What?

This is set as a bug because any developer using DAB would think this is a bug regardless of the details.

Standard output causes MCP clients to misread even information as a warning.

Note

This is important because we want to seamlessly snap into the AI workflow, not look like we are failing.

Why?

The MCP client should be able to start DAB without looking like we have errored.

How?

When -mcp-stdio, default --LogLevel flag to none but allow it to override if set explicitly.

Important

We must ensure that loglevel:none in the command-line ACTUALLY emits ZERO CHARACTERS!

Image

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions