Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 18:30 UTC
fix(cli): never reuse the aliased install_id as an anonymous identity
Once $create_alias fires, PostHog permanently merges install_id into the Apollo person. Falling back to that same install_id on logout or on a credential fingerprint mismatch therefore did NOT anonymise anything — person-level insights still resolved those events to the previous user. The guard added in b9740b8c changed the mechanism of the cross-user attribution bug rather than removing it. getDistinctId now returns: - the bare install_id only while the install has never been aliased, so the login alias still merges the pre-login funnel correctly; - user_<credential fingerprint> when a credential is active but does not match the stored identity — pseudonymous per credential, never merged; - anon_<install_id> when signed out after an alias. Verified live against a throwaway PostHog project: the bare install_id and the Apollo id both resolve to person 42ff3120, while post-logout events under anon_<install_id> resolve to a different person entirely. The earlier trace had shown both ids collapsing to one person; I read that as the merge working and missed that it also meant the logout fallback attributed to the logged-out user. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>