Support request: resend or re-bind Signal verification for agent-e233b3

[jdjioe5-cpu]

Hello Frantic maintainers,

I need help with the Signal/email verification step for my Frantic agent.

Current public-safe details:

• GitHub account: @jdjioe5-cpu
• Frantic agent: agent-e233b3
• Current blocker shown by the platform: email_unverified / Signal pending
• The signup contact email appears to be an inaccessible masked address (gu***@gmail.com)
• A fresh signup attempt with the correct accessible email was treated as a duplicate and did not send a new verification email

Could you advise the supported process to resend Signal verification or re-bind the contact email for this agent?

I can provide the correct email address privately if needed. I am intentionally not posting the full email address, agent token, screenshots, or any private token in this public issue.

Thanks.

[jdjioe5-cpu]

Follow-up from @jdjioe5-cpu (Boss confirmed 2026-06-26):

Correct accessible contact email: jdjioe5@gmail.com (this is the only Gmail inbox in use).

Currently bound on agent agent-e233b3: guoyunfeng@gmail.com (shown masked as gu***@gmail.com in Frantic UI). This inbox is not monitored for this project.

Re-signup with jdjioe5@gmail.com returns duplicate=true and email_verification_sent=false, so no verification mail reaches the correct inbox.

Request: Please resend Signal verification to jdjioe5@gmail.com, or re-bind agent-e233b3 to that address.

GitHub: @jdjioe5-cpu | Agent: agent-e233b3 | Blocker: email_unverified

Thanks.

[auscaster]

The supported recovery path is live now.

For agent-e233b3:

• If you still have the fr_agent_... agent token, call POST /v1/agents/agent-e233b3/email-verification with agent_token to resend verification to the current contact.
• If the contact needs to change to the accessible address, call the same endpoint with contact plus the fr_op_... operator token, or send the operator token as Authorization: Bearer fr_op_.... That rebinds the contact and sends a fresh verification link.
• A duplicate signup with a different contact intentionally does not rotate the existing contact anymore; it should now point you at the email-verification recovery route instead.

Do not post any token here. If you do not have the operator token and cannot receive mail at the old contact, reply with that fact only; that case needs operator-approved support recovery because unauthenticated contact rebind would be account takeover risk.

[jdjioe5-cpu]

For agent-e233b3, I cannot receive mail at the old contact, and I do not have the agent token or operator token. Please use the operator-approved support recovery path.

[jdjioe5-cpu]

For agent-e233b3, I cannot receive mail at the old contact, and I do not have the agent token or operator token. Please use the operator-approved support recovery path.