Fix extra logging in non-root commands #1500

Copilot · 2026-01-17T08:06:08Z

Fixes extra logging in non-root commands by configuring logging centrally based on command type.

Changes Made

Root command: Uses rich logging with ProxyConsoleFormatter (unchanged)
stdio command: Uses file logging only (unchanged)
jwt command: No console logging - all logging suppressed so only the token output is visible
Other subcommands (cert, config, outdated, msgraphdb): Rich logging with ProxyConsoleFormatter but with plugin messages filtered out

Added IsRootCommand property that detects if the first argument starts with - (option) or there are no arguments, automatically working for any new subcommand without code changes.

Added IsJwtCommand property to handle the jwt command's special case where no logging should be visible.

Testing

✅ jwt create outputs only the token without extra logging
✅ outdated shows its output correctly with rich formatting (no plugin messages)
✅ cert --help and config --help work correctly
✅ Root --help displays correctly with rich formatting

Original prompt

This section details on the original issue you should resolve

<issue_title>[BUG]: extra logging in non-root commands</issue_title>
<issue_description>### Description

When running non-root commands, there's extra logging which interferes with the command's output

Expected behaviour

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1bmlxdWVfbmFtZSI6Ik1lZ2FuIEJvd2VuIiwic3ViIjoiTWVnYW4gQm93ZW4iLCJqdGkiOiJmMTZlOTllIiwic2NwIjoiQ3VzdG9tZXJzLlJlYWQiLCJhdWQiOiJodHRwczovL2FwaS5jb250b3NvLmNvbSIsIm5iZiI6MTc2ODU1OTUxMSwiZXhwIjoxNzY4NTU5NTExLCJpYXQiOjE3Njg1NTk1MTEsImlzcyI6ImRldi1wcm94eSJ9.VUKYcsSrHrG69R9nmBbrSx_QDZ93wzp3eAzaGJ6vkhs

Actual behaviour

 warn    AddPlugins: The version of schema does not match the installed Dev Proxy version, the expected schema is https://raw.githubusercontent.com/dotnet/dev-proxy/main/schemas/v2.1.0/rc.schema.json
 warn    The version of schema does not match the installed Dev Proxy version, the expected schema is https://raw.githubusercontent.com/dotnet/dev-proxy/main/schemas/v2.1.0/crudapiplugin.schema.json
 warn    The version of schema does not match the installed Dev Proxy version, the expected schema is https://raw.githubusercontent.com/dotnet/dev-proxy/main/schemas/v2.1.0/crudapiplugin.apifile.schema.json
 info    5 actions for CRUD API loaded from /Users/waldek/github/pnp/proxy-samples/samples/jwt-testing-toolkit/.devproxy/customers-api.json
 info    Data for CRUD API loaded from customers-data.json for API /Users/waldek/github/pnp/proxy-samples/samples/jwt-testing-toolkit/.devproxy/customers-api.json
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1bmlxdWVfbmFtZSI6Ik1lZ2FuIEJvd2VuIiwic3ViIjoiTWVnYW4gQm93ZW4iLCJqdGkiOiJmMTZlOTllIiwic2NwIjoiQ3VzdG9tZXJzLlJlYWQiLCJhdWQiOiJodHRwczovL2FwaS5jb250b3NvLmNvbSIsIm5iZiI6MTc2ODU1OTUxMSwiZXhwIjoxNzY4NTU5NTExLCJpYXQiOjE3Njg1NTk1MTEsImlzcyI6ImRldi1wcm94eSJ9.VUKYcsSrHrG69R9nmBbrSx_QDZ93wzp3eAzaGJ6vkhs

Steps to reproduce

devproxy jwt create --name "Megan Bowen" --issuer "dev-proxy" --audiences "https://api.contoso.com" --scopes "Customers.Read"

Dev Proxy Version

latest from main

Operating system (environment)

macOS

Shell

zsh

Configuration file

{
  "$schema": "https://raw.githubusercontent.com/dotnet/dev-proxy/main/schemas/v2.0.0/rc.schema.json",
  "plugins": [
    {
      "name": "CrudApiPlugin",
      "enabled": true,
      "pluginPath": "~appFolder/plugins/DevProxy.Plugins.dll",
      "configSection": "customersApi"
    }
  ],
  "urlsToWatch": [
    "https://api.contoso.com/*"
  ],
  "customersApi": {
    "$schema": "https://raw.githubusercontent.com/dotnet/dev-proxy/main/schemas/v2.0.0/crudapiplugin.schema.json",
    "apiFile": "customers-api.json"
  }
}

Additional Info

No response</issue_description>

<agent_instructions>Configure logging so that the rich logging is used only with the root command. All other subcommands should only log their output, just like the stdio subcommand does</agent_instructions>

Comments on the Issue (you are @copilot in this section)

Fixes [BUG]: extra logging in non-root commands #1499

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: waldekmastykarz <11164679+waldekmastykarz@users.noreply.github.com>

waldekmastykarz

@copilot is this the best way to implement this? The stdio command has something similar implemented too. Is there a way to configure it centrally and avoid duplication? Only the root command should have the extended logging. All other commands should only print console.writelines. All other logs should be invisible

DevProxy/Commands/DevProxyCommand.cs

Co-authored-by: waldekmastykarz <11164679+waldekmastykarz@users.noreply.github.com>

Copilot · 2026-01-17T10:40:59Z

@copilot is this the best way to implement this? The stdio command has something similar implemented too. Is there a way to configure it centrally and avoid duplication? Only the root command should h...

Refactored in ccf902b. The logging is now configured centrally in ILoggingBuilderExtensions.ConfigureDevProxyLogging with a single check: !DevProxyCommand.IsRootCommand. Only the root command gets rich logging; all subcommands get minimal logging with plugin messages filtered out. No duplication needed.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

aka.ms
- Triggering command: /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy jwt create --name Megan Bowen --issuer dev-proxy --audiences REDACTED --scopes Customers.Read (dns block)
- Triggering command: /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy outdated (dns block)
- Triggering command: /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy cert --help (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

waldekmastykarz

@copilot ok, it must be done differently, because now we're surpressing all output which isn't great. jwt and stdio shouldn't log anything to console. Other commands should

Co-authored-by: waldekmastykarz <11164679+waldekmastykarz@users.noreply.github.com>

Copilot · 2026-01-18T13:11:57Z

@copilot ok, it must be done differently, because now we're surpressing all output which isn't great. jwt and stdio shouldn't log anything to console. Other commands should

Fixed in eb12d79. Updated the logging configuration:

stdio and jwt commands: No console logging
Root command: Rich logging with ProxyConsoleFormatter
Other subcommands (cert, config, outdated, msgraphdb): Simple console logging with plugin messages filtered out

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

aka.ms
- Triggering command: /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy jwt create --name Megan Bowen --issuer dev-proxy --audiences REDACTED --scopes Customers.Read (dns block)
- Triggering command: /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy outdated (dns block)
- Triggering command: /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy cert --help (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

waldekmastykarz · 2026-01-18T13:41:51Z

@copilot is this the best way to solve it?

Copilot · 2026-01-18T13:43:06Z

@copilot is this the best way to solve it?

The current approach is a reasonable solution given the constraint that logging must be configured early in app startup, before System.CommandLine parses commands.

An alternative would be to configure all subcommands to have no console logging by default (like stdio), and let commands that need logging output use Console.WriteLine directly. This would simplify the logic to just two cases: root command (rich logging) vs all subcommands (no logging).

Would you prefer that simpler approach? It would mean commands like cert, config, outdated would output via Console.WriteLine instead of the logger.

waldekmastykarz · 2026-01-18T17:38:01Z

@copilot let's stick with the current approach. We can always change it in the future

DevProxy/Extensions/ILoggingBuilderExtensions.cs

Copilot

Pull request overview

This PR fixes extra logging in non-root commands by configuring logging centrally based on command type. The issue was that plugin messages and other diagnostic logs were appearing in the output of utility commands like jwt create, interfering with their intended output.

Changes:

Added IsJwtCommand property to detect when the JWT command is being run and suppress all console logging
Added IsRootCommand property to detect when the root proxy command is being invoked (vs. subcommands)
Refactored logging configuration to use rich logging for root command, no logging for JWT command, and simple console logging with filtered plugin messages for other subcommands

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
DevProxy/Commands/DevProxyCommand.cs	Added `IsJwtCommand` and `IsRootCommand` static properties to detect which command is being executed based on command-line arguments
DevProxy/Extensions/ILoggingBuilderExtensions.cs	Refactored logging configuration to use conditional logic based on command type, with different logging strategies for stdio, jwt, root, and other subcommands

DevProxy/Extensions/ILoggingBuilderExtensions.cs

DevProxy/Commands/DevProxyCommand.cs

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

…nd adding console formatter

…/github.com/dotnet/dev-proxy into copilot/fix-extra-logging-non-root-commands

garrytrinder · 2026-01-19T10:01:13Z

devproxy outdated command is returning plugin messages.

waldekmastykarz · 2026-01-19T10:06:38Z

devproxy outdated command is returning plugin messages.

@copilot include outdated in the list of commands that should use simplified logging

Co-authored-by: waldekmastykarz <11164679+waldekmastykarz@users.noreply.github.com>

Copilot · 2026-01-19T10:09:48Z

devproxy outdated command is returning plugin messages.

<img alt="image" width="882" height="52" src="https://private-user-images.githubusercontent.com/11563347/537506900-16675d95-6637-471b...

Fixed in 8ecf3a4. The subcommands branch was incorrectly using the same rich logging as the root command. Now it properly uses ClearProviders() + AddSimpleConsole() with plugin messages filtered to LogLevel.None.

devproxy outdated now only shows its own output:

info: DevProxy.Commands.OutdatedCommand[0] You are using the latest version of Dev Proxy.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

aka.ms
- Triggering command: /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy outdated (dns block)
- Triggering command: /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy jwt create --name Test User (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

waldekmastykarz · 2026-01-19T10:32:55Z

@copilot revert the last change. For the outdated command, keep the existing logging formatting, only suppress messages from plugins.

Co-authored-by: waldekmastykarz <11164679+waldekmastykarz@users.noreply.github.com>

Copilot · 2026-01-19T10:35:35Z

@copilot revert the last change. For the outdated command, keep the existing logging formatting, only suppress messages from plugins.

Fixed in c7c1793. Reverted to use rich logging with ProxyConsoleFormatter for subcommands like outdated. Only plugin messages are now filtered out (DevProxy.Plugins.* → LogLevel.None).

devproxy outdated now shows:

 info    You are using the latest version of Dev Proxy.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

aka.ms
- Triggering command: /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy outdated (dns block)
- Triggering command: /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy /home/REDACTED/work/dev-proxy/dev-proxy/DevProxy/bin/Debug/net10.0/devproxy jwt create --name Test User (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Configure Actions setup steps to set up my environment, which run before the firewall is enabled
Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Done

Initial plan

6e5edfe

Copilot AI assigned Copilot and waldekmastykarz Jan 17, 2026

Copilot started work on behalf of waldekmastykarz January 17, 2026 08:06 View session

Fix extra logging in non-root commands by filtering plugin messages

8525028

Co-authored-by: waldekmastykarz <11164679+waldekmastykarz@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Fix extra logging in non-root commands~~ Fix extra logging in non-root commands Jan 17, 2026

Copilot AI requested a review from waldekmastykarz January 17, 2026 08:18

Copilot finished work on behalf of waldekmastykarz January 17, 2026 08:18

waldekmastykarz added the pr-bugfix Fixes a bug label Jan 17, 2026

waldekmastykarz requested changes Jan 17, 2026

View reviewed changes

DevProxy/Commands/DevProxyCommand.cs Outdated Show resolved Hide resolved

Copilot started work on behalf of waldekmastykarz January 17, 2026 10:37 View session

Refactor: Use IsRootCommand instead of listing subcommand names

ccf902b

Co-authored-by: waldekmastykarz <11164679+waldekmastykarz@users.noreply.github.com>

Copilot finished work on behalf of waldekmastykarz January 17, 2026 10:44

Copilot AI requested a review from waldekmastykarz January 17, 2026 10:44

waldekmastykarz previously requested changes Jan 18, 2026

View reviewed changes

Copilot started work on behalf of waldekmastykarz January 18, 2026 13:08 View session

Handle jwt command separately: no console logging, other subcommands log

eb12d79

Co-authored-by: waldekmastykarz <11164679+waldekmastykarz@users.noreply.github.com>

Copilot AI requested a review from waldekmastykarz January 18, 2026 13:15

Copilot finished work on behalf of waldekmastykarz January 18, 2026 13:15

Copilot started work on behalf of waldekmastykarz January 18, 2026 13:42 View session

Copilot finished work on behalf of waldekmastykarz January 18, 2026 13:43

Copilot started work on behalf of waldekmastykarz January 18, 2026 17:38 View session

Copilot finished work on behalf of waldekmastykarz January 18, 2026 17:39

waldekmastykarz marked this pull request as ready for review January 18, 2026 17:42

waldekmastykarz requested a review from a team as a code owner January 18, 2026 17:42

Copilot AI review requested due to automatic review settings January 18, 2026 17:42

Copilot started reviewing on behalf of waldekmastykarz January 18, 2026 17:42 View session

waldekmastykarz reviewed Jan 18, 2026

View reviewed changes

DevProxy/Extensions/ILoggingBuilderExtensions.cs Show resolved Hide resolved

waldekmastykarz marked this pull request as draft January 18, 2026 17:44

Copilot AI reviewed Jan 18, 2026

View reviewed changes

DevProxy/Extensions/ILoggingBuilderExtensions.cs Outdated Show resolved Hide resolved

DevProxy/Commands/DevProxyCommand.cs Outdated Show resolved Hide resolved

DevProxy/Commands/DevProxyCommand.cs Show resolved Hide resolved

Copilot started work on behalf of waldekmastykarz January 18, 2026 17:45 View session

Copilot AI requested a review from waldekmastykarz January 18, 2026 17:46

Copilot finished work on behalf of waldekmastykarz January 18, 2026 17:46

waldekmastykarz and others added 3 commits January 18, 2026 18:46

Apply suggestion from @Copilot

516df64

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Enhance logging for non-root subcommands by adjusting filter levels a…

098c076

…nd adding console formatter

Merge branch 'copilot/fix-extra-logging-non-root-commands' of https:/…

d5502fe

…/github.com/dotnet/dev-proxy into copilot/fix-extra-logging-non-root-commands

waldekmastykarz marked this pull request as ready for review January 18, 2026 17:50

Copilot started work on behalf of waldekmastykarz January 19, 2026 10:07 View session

Fix subcommands to use simple logging with plugin messages filtered out

8ecf3a4

Co-authored-by: waldekmastykarz <11164679+waldekmastykarz@users.noreply.github.com>

Copilot finished work on behalf of waldekmastykarz January 19, 2026 10:10

Copilot started work on behalf of waldekmastykarz January 19, 2026 10:33 View session

Keep rich logging for subcommands, only suppress plugin messages

c7c1793

Co-authored-by: waldekmastykarz <11164679+waldekmastykarz@users.noreply.github.com>

Copilot finished work on behalf of waldekmastykarz January 19, 2026 10:36

waldekmastykarz and others added 3 commits January 19, 2026 11:24

Merge branch 'main' into copilot/fix-extra-logging-non-root-commands

796039d

Merge branch 'main' into copilot/fix-extra-logging-non-root-commands

2080355

Merge branch 'main' into copilot/fix-extra-logging-non-root-commands

9d85912

garrytrinder approved these changes Jan 19, 2026

View reviewed changes

waldekmastykarz merged commit fd55193 into main Jan 19, 2026
4 checks passed

waldekmastykarz deleted the copilot/fix-extra-logging-non-root-commands branch January 19, 2026 14:03

Fix extra logging in non-root commands #1500

Fix extra logging in non-root commands #1500

Uh oh!

Conversation

Copilot AI commented Jan 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes Made

Testing

Expected behaviour

Actual behaviour

Steps to reproduce

Dev Proxy Version

Operating system (environment)

Shell

Configuration file

Additional Info

Comments on the Issue (you are @copilot in this section)

Uh oh!

waldekmastykarz left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Copilot AI commented Jan 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

waldekmastykarz left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Jan 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

waldekmastykarz commented Jan 18, 2026

Uh oh!

Copilot AI commented Jan 18, 2026

Uh oh!

waldekmastykarz commented Jan 18, 2026

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

garrytrinder commented Jan 19, 2026

Uh oh!

waldekmastykarz commented Jan 19, 2026

Uh oh!

Copilot AI commented Jan 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

waldekmastykarz commented Jan 19, 2026

Uh oh!

Copilot AI commented Jan 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

I tried to connect to the following addresses, but was blocked by firewall rules:

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented Jan 17, 2026 •

edited

Loading

Copilot AI commented Jan 17, 2026 •

edited

Loading

Copilot AI commented Jan 18, 2026 •

edited

Loading

Copilot AI commented Jan 19, 2026 •

edited

Loading

Copilot AI commented Jan 19, 2026 •

edited

Loading