### Problem (one or two sentences) Zoo Code has not yet updated its user agent to own dedicated. ### Context (who is affected and when) This could be disrespectful to the original and will increase debugging difficulty in the future. ### Desired behavior (conceptual, not technical) Refer to itself as Zoo Code in activity logs rather than Roo Code. ### Constraints / preferences (optional) _No response_ ### Request checklist - [x] I've searched existing Issues and Discussions for duplicates - [x] This describes a specific problem with clear context and impact ### Zoo Code Task Links (optional) _No response_ ### Acceptance criteria (optional) _No response_ ### Proposed approach (optional) https://github.com/Zoo-Code-Org/Zoo-Code/blob/72456803f025dcff9b4e7b0c488c5346cfa9343e/src/api/providers/constants.ts#L4 https://github.com/yfdyh000/Zoo-Code/commit/7b1dc0b5a0928bc3f9a9dc7cb1cf07b009ff4159 ### Trade-offs / risks (optional) Meanwhile, I suspect that updating the identifier may break the existing authorization for some users and endpoints, so are UI/docs changes needed?
Activity
proyectoauraorg commentedon May 24, 2026
Looking into this — updating the user-agent string in
src/api/providers/constants.tsto identify as Zoo Code. PR incoming shortly. 🦓edelauna commentedon May 24, 2026
I should've commented sooner, I claimed this under #219