[BUG] Formatting numbered list causes 500 Error for Claude Code

Resolved 💬 3 comments Opened Feb 25, 2026 by jungblud Closed Feb 25, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

I wrote some requirements in Apple Notes and copy pasted which gave a 500 Error.

input:
"Ok I've thought about the complexities; this has taken a minute to think through. Essentially there are 3
Property types a user could access:

  1. Property w/Single Unit
  2. Property w/Multi Units all on single service bills for entire property
  3. Property w/Multi Units on separate service bills per Unit

We need to take billing information from multiple utility providers and normalize the addresses on the accounts
into a consistent understanding of the Property in question. This will be important for workflow actions later.
Each Provider may differ with not only sub-address terminology but also numbering potentially. A way to display
Properties is needed as this is how the landlord/tenant/owner will want to see the information organized the
majority of the time."

result:
⎿  API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server
error"},"request_id":"req_011CYV7fstbMStBZz4G6Z25D"}

What Should Happen?

Should have taken the input without 500 Error

Error Messages/Logs

⎿  API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server
     error"},"request_id":"req_011CYV7fstbMStBZz4G6Z25D"}

Steps to Reproduce

Open Claude Code
Paste text with a number list from Apple Notes
Key 'return'

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.56

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗