The installation page tells users to add alsoAllow to openclaw.json but doesn't say how to open the file. openclaw config edit feels like the natural command but doesn't exist — running it throws error: too many arguments for 'config'. Expected 0 arguments but got 1.
Should either:
- Document the direct file path (
~/.openclaw/openclaw.json) so users know where to edit it, or
- Implement
openclaw config edit as a convenience command
Found during a fresh install trial on EC2.
The installation page tells users to add
alsoAllowtoopenclaw.jsonbut doesn't say how to open the file.openclaw config editfeels like the natural command but doesn't exist — running it throwserror: too many arguments for 'config'. Expected 0 arguments but got 1.Should either:
~/.openclaw/openclaw.json) so users know where to edit it, oropenclaw config editas a convenience commandFound during a fresh install trial on EC2.