Skip to content

fix: remove existing_app_id from 409 response + clarify recovery instructions#51

Merged
i8ramin merged 1 commit into
dupe-com:mainfrom
lpezet:fix/409-email-already-registered-response
Jun 1, 2026
Merged

fix: remove existing_app_id from 409 response + clarify recovery instructions#51
i8ramin merged 1 commit into
dupe-com:mainfrom
lpezet:fix/409-email-already-registered-response

Conversation

@lpezet

@lpezet lpezet commented May 21, 2026

Copy link
Copy Markdown
Contributor

Closes #50

Summary

  • Remove existing_app_id from the EMAIL_ALREADY_REGISTERED 409 response body — leaking it allows unauthenticated app_id enumeration by probing with arbitrary emails
  • Update recovery message to accurately describe the human-mediated flow: call POST /v1/auth/recover → receive BOTCHA code by email → visit https://botcha.ai → click "Account" → enter code → retrieve app_id and share with the agent

Test plan

  • POST /v1/apps with a duplicate email returns 409 with no existing_app_id field
  • recovery message in the 409 body matches the updated wording
  • All existing tests pass (bun run test:run — 1219 tests)

🤖 Generated with Claude Code

…ructions — closes dupe-com#50

Removes existing_app_id from the EMAIL_ALREADY_REGISTERED 409 response
to prevent unauthenticated app_id enumeration via email probing. Updates
the recovery message to describe the correct human-mediated flow: trigger
a BOTCHA code email, then visit botcha.ai/Account to retrieve the app_id.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@i8ramin i8ramin merged commit a1060b0 into dupe-com:main Jun 1, 2026
1 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: remove existing_app_id from 409 EMAIL_ALREADY_REGISTERED response + clarify recovery instructions

2 participants