openclaw - 💡(How to fix) Fix [Bug]: config.patch fails for Telegram group IDs (negative numeric keys in path) [1 participants]

1. Observe: "invalid config" error Returns "invalid config" error. Workaround: manually edit openclaw.json and restart/reload. Agents cannot self-configure group settings via the standard config.patch tool. This forces manual file editing, which is error-prone and breaks the self-service configuration flow. Every Telegram supergroup has a negative ID, so this affects all group-specific configuration.

TL;DR

Update the config patch path parser to correctly handle negative numeric keys, allowing for proper configuration of Telegram supergroups.

Guidance

• Verify that the issue is indeed caused by the parser's handling of negative numbers by attempting to configure a group with a positive ID.
• Check the parser's documentation or source code to see if there are any existing provisions for handling negative keys or if there's a known workaround.
• Consider implementing a temporary workaround by modifying the config patch tool to automatically convert negative group IDs to a compatible format, such as wrapping them in quotes or using a different delimiter.
• Test the fix by attempting to configure a Telegram supergroup using the updated parser and verifying that the configuration is applied correctly.

Example

{
  "channels": {
    "telegram": {
      "groups": {
        "-5028303500": {
          "requireMention": false
        }
      }
    }
  }
}

This example configuration should be parsed correctly by the updated parser, allowing for successful configuration of the Telegram supergroup.

Notes

The provided information suggests that the issue is specific to the config patch path parser and its handling of negative numeric keys. However, without access to the parser's source code or documentation, it's difficult to provide a more detailed solution.

Recommendation

Apply a workaround by modifying the config patch tool to handle negative group IDs correctly, as this will allow for immediate resolution of the issue and enable self-service configuration for Telegram supergroups.