Claude Code v1.0.124 introduced an undocumented breaking change in session resume behavior:
- v1.0.123 and earlier: Creates a NEW session ID when using
--resume - v1.0.124 and later: Reuses the SAME session ID when using
--resume
This change breaks systems that rely on the previous behavior of creating new session IDs on resume.
# Prerequisites
export ANTHROPIC_API_KEY="your-api-key"
# Build and run tests
docker compose build
docker compose run --rm claude-test ./test.sh 1.0.123
docker compose run --rm claude-test ./test.sh 1.0.124{
"behavior": "creates_new_id",
"session_ids": {
"initial": "66658f92-2cd1-48a5-a904-9acbbf0197cb",
"resumed": "dc038920-1cb0-4d21-b417-98fcb753b54c",
"identical": false
}
}{
"behavior": "reuses_same_id",
"session_ids": {
"initial": "b41d4917-26d4-4dcd-84bf-dc429457ed39",
"resumed": "b41d4917-26d4-4dcd-84bf-dc429457ed39",
"identical": true
}
}This undocumented change can break applications that:
- Track sessions by Claude session ID
- Assume new session IDs indicate new conversation branches
- Store conversation events keyed by session ID
README.md- This documentationtest.sh- Test script that demonstrates the behaviorDockerfile- Ubuntu container with Claude installationdocker-compose.yaml- Docker compose configuration