Empty catch block without logging. This makes debugging difficult if config reading fails. Consider adding logging or at least a comment explaining why exceptions are silently ignored.

catch (Exception ex) {
    // Log configuration parsing error for troubleshooting
    System.Diagnostics.Debug.WriteLine($"Failed to read pyRevit config: {ex.Message}");
    return (false, "current_command");
}

Empty catch block without logging. UI operations can fail for various reasons and silent failures make troubleshooting difficult.

catch (Exception ex) {
    // Log UI operation error for troubleshooting
    System.Diagnostics.Debug.WriteLine($"Failed to close other outputs: {ex.Message}");
}

Config parsing logic is fragile and could match unintended lines. Using IndexOf to find "true" anywhere in the line could match comments or other values. Should parse the key=value format properly.

if (line.StartsWith("close_other_outputs", StringComparison.InvariantCultureIgnoreCase)) {
    var parts = line.Split(new[] { '=' }, 2);
    if (parts.Length == 2)
        close = string.Equals(parts[1].Trim().Trim('"'), "true", StringComparison.InvariantCultureIgnoreCase);
}

The configuration value parsing is unreliable. Using IndexOf to check for 'true' could match partial strings like 'untrue' or comments containing 'true'. Should parse the actual value after the '=' separator like the close_mode parsing below.

I recommend using the configuration API, which is already in the pyRevit library. It is also worth adding these settings to the command line utility :)

It is better to put the operating modes in an enum or create a class hierarchy

Thanks a lot!
Here, would you add extension methods to map enum and string from Consts file ?
I'm a beginner in C# so plz don't be implicit :)

after writing the review, I think it will be enough to create text constants with which to conduct comparisons

but you can still make an enum Enum.TryParse<TEnum>(string value, out TEnum result)

It is better to put the operating modes in an enum or create a class hierarchy

It is recommended to add configuration constants to the constants class

I think it's also worth moving these settings to this class

I think it's also worth moving these settings to this class

Didn't understand
They already are in the PyRevitConfig class

write an implementation of access to these parameters inside a class specially made for access to the pyRevit_Config.ini parameters

sample:

@property
def close_other_outputs(self):
    return self.core.get_option(
        CONSTS.CloseOtherOutputs,
        default_value=CONSTS. CloseOtherOutputsDefault,
    )

@close_other_outputs.setter
def close_other_outputs(self, state):
    self.core.set_option(
        CONSTS.CloseOtherOutputs,
        value=state

Sorry, I didn't notice that you wrote the code where it should be :D

It is recommended to add configuration constants to the constants class

I think it's also worth moving these settings to this class

It is recommended to add configuration constants to the constants class

I think it's also worth moving these settings to this class

It is recommended to add configuration constants to the constants class

I think it's also worth moving these settings to this class

@dosymep is there a better way than trimming the config value ?

As far as I remember, you don't need to trim it yourself, it should do it automatically

@dosymep With enum, I had to deal with mapping somewhere.
Feel free to redirect me, if you see a better way to do plz

I think it's good, I hope in the future I will rewrite all the code for working with settings, and there will be a more convenient option

remove only the enum suffix in name, I don't think users need to see it

Empty catch block violates exception handling standards. According to the review validation checklist, empty catch blocks should log exceptions at minimum. Consider logging the exception or using more specific exception types.

catch (Exception ex) {
    logger.Debug("Failed to close other output windows: " + ex.Message);
}

Using BeginInvoke for UI marshalling may introduce unnecessary delay. Consider whether the console closing operation needs to be asynchronous or if Invoke (synchronous) would be more appropriate for immediate feedback.

The current implementation may cause timing issues where the new console opens before others finish closing.

The string trimming logic with both quotation marks seems unusual and may indicate a configuration parsing issue. The standard pyRevit configuration pattern doesn't typically require quote trimming. Consider whether this complexity is necessary or if it masks an underlying issue.

var s = (raw ?? PyRevitConsts.ConfigsCloseOutputModeDefault).Trim();

As far as I remember, you don't need to trim it yourself, it should do it automatically

Sorry, I didn't notice that you wrote the code where it should be :D

I think it's good, I hope in the future I will rewrite all the code for working with settings, and there will be a more convenient option

remove only the enum suffix in name, I don't think users need to see it

remove trim, the pyRevit library trimmed values by default

can remove I think

I renamed methods (remove enum suffix)