Skip to content

docs(db): note user IDs are not always UUIDs - #5375

Open
kilo-code-bot[bot] wants to merge 1 commit into
mainfrom
docs/user-id-not-always-uuid
Open

docs(db): note user IDs are not always UUIDs#5375
kilo-code-bot[bot] wants to merge 1 commit into
mainfrom
docs/user-id-not-always-uuid

Conversation

@kilo-code-bot

@kilo-code-bot kilo-code-bot Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds guidance to packages/db/AGENTS.md clarifying that a user ID is not always a UUID.

We keep hitting backwards-incompatible bugs because code assumes user IDs are UUIDs. In reality a user ID is an arbitrary string: it may be a UUID or another format, and OAuth user IDs usually start with the prefix oauth/. This matches the schema, where kilocode_users.id and all user-ID references (e.g. kilo_user_id, user_id) are text() columns, not uuid().

Change

New "User IDs" section under the shared PostgreSQL data-contract notes, warning against UUID validation/parsing and uuid()-typed columns or ::uuid casts on user IDs, since those break for OAuth users.

Docs-only; no code or schema changes.


Built for Evgeny Shurakov by Kilo for Slack

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.

1 participant