#ClawHub admin ask: handle rename

8 messages · Page 1 of 1 (latest)

lethal pasture
#

Hey, quick admin ask — can someone rename my ClawHub handle from apps-debug to qorisai?

Backstory: I published qoris-memory under apps-debug before renaming the underlying GitHub account to qorisai.
ClawHub picked up the new display name ("Qoris AI") and avatar on re-login, but the handle slug is still stuck on the old one. Same GitHub account (ID 248860180), same user — just a rename.

I'd rather not delete + republish since that'd wipe download stats and the 90-day slug reservation would block me from reusing qoris-memory for 3 months. Opened issues #1675 and #1676 for the underlying feature gaps but I'm hoping an admin can just flip the handle column manually for my account in the meantime.

crude plumeBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

fleet shuttleBOT
#

That sounds like a legit manual-rename case, and yeah, deleting + republishing would be a bad trade if it nukes stats and triggers the slug hold.

I can’t flip the ClawHub handle myself from here, but opening issues #1675 and #1676 was the right move. This likely needs a maintainer/admin-side database change or a proper rename flow on the backend.

My recommendation:

  • keep the existing package as-is for now
  • do not delete + republish
  • let the issue/thread be the source of truth for the manual fix request

If an admin picks this up, the requested change is:

  • account: GitHub ID 248860180
  • old handle: apps-debug
  • new handle: qorisai

If this gets resolved here, please mark the solution so it’s indexed on Answer Overflow.

lethal pasture
#

@harsh flower @ruby orchid

fleet shuttleBOT
#

Yep, this is firmly an admin-side fix, so waiting here makes sense.

I wouldn’t touch the package in the meantime. If they can do a manual handle swap, that’s the cleanest outcome.

ruby orchid
#

Thanks for tagging - will escalate, however this likely won’t be possible

fleet shuttleBOT
#

Yeah, that tracks. If the handle slug is baked into ownership or package URLs, a manual flip can be nastier than it looks.

In that case, the issues are probably the right long-term path, and I’d leave the existing publish alone until the escalation comes back.

lethal pasture