claude-code - 💡(How to fix) Fix [Bug] Context window display mismatch: status bar denominator differs from /context output [2 comments, 3 participants]

[{"error":"Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"tools.304.custom.input_schema.properties: Property keys should match pattern '^[a-zA-Z0-9_.-]{1,64}$'"},"request_id":"req_011CaTWt4sanYFboVgeAfFxw"}\n at generate (B:/~BUN/root/src/entrypoints/cli.js:11:56508)\n at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T02:50:25.494Z"},{"error":"Error: 400 {"type":"error","error":{"type":"invalid_request_error","message":"tools.304.custom.input_schema.properties: Property keys should match pattern '^[a-zA-Z0-9_.-]{1,64}$'"},"request_id":"req_011CaTWt8xu79PS1paSNADc6"}\n at generate (B:/~BUN/root/src/entrypoints/cli.js:11:56508)\n at makeRequest (B:/~BUN/root/src/entrypoints/cli.js:50:4943)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T02:50:26.007Z"}]

TL;DR

The issue may be resolved by adjusting the input schema properties to match the required pattern '^[a-zA-Z0-9_.-]{1,64}$' to fix the invalid request error.

Guidance

• Review the input schema properties in the code to identify any keys that do not match the pattern '^[a-zA-Z0-9_.-]{1,64}$'.
• Check the cli.js file at lines 11 and 50 to understand how the generate and makeRequest functions are handling the input schema properties.
• Verify that the property keys in the input schema are not exceeding the 64 character limit.
• Consider updating the input schema to use valid property keys that conform to the required pattern.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue seems to be related to an invalid request error caused by property keys in the input schema not matching the required pattern. However, without more information about the input schema and the code, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Adjust the input schema properties to match the required pattern to fix the invalid request error, as this is the most likely cause of the issue.