chore(code): add per-user option to ph code usage reset

[adboio]

Problem

reset_posthog_code_usage only work for ALL users, need the ability to do this per-user

Changes

adds --user-id argument to the command

usage:

reset-posthog-code-usage --dry-run --user-id <the-user-id>

How did you test this code?

tested against local stack

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Publish to changelog?

no

Docs update

no

🤖 Agent context

[adboio]

• chore(code): add per-user option to ph code usage reset #60301 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
services/llm-gateway/src/llm_gateway/cli/reset_posthog_code_usage.py:26-28
If an operator passes a `user_id` containing Redis glob characters (`*`, `?`, `[`), the exact-key and wildcard patterns generated by `_patterns_for` will silently expand beyond the intended user. For example `--user-id "1*"` would produce the match pattern `...posthog_code:1*`, which matches every user whose ID starts with `1`. A lightweight guard with an early error prevents this accidental over-deletion.

```suggestion
def _patterns_for(user_id: str | None) -> tuple[str, ...]:
    if user_id is None:
        return tuple(f"ratelimit:cost:user:{scope}:{POSTHOG_CODE_PRODUCT}:*" for scope in SCOPES)
    if any(c in user_id for c in ("*", "?", "[")):
        raise ValueError(f"user_id contains Redis glob characters: {user_id!r}")
```

_{Reviews (1): Last reviewed commit: "chore(code): add per-user option to ph c..." | Re-trigger Greptile}

[greptile-apps]

If an operator passes a user_id containing Redis glob characters (*, ?, [), the exact-key and wildcard patterns generated by _patterns_for will silently expand beyond the intended user. For example --user-id "1*" would produce the match pattern ...posthog_code:1*, which matches every user whose ID starts with 1. A lightweight guard with an early error prevents this accidental over-deletion.

Suggested change

	def _patterns_for(user_id: str | None) -> tuple[str, ...]:
	if user_id is None:
	return tuple(f"ratelimit:cost:user:{scope}:{POSTHOG_CODE_PRODUCT}:*" for scope in SCOPES)
	def _patterns_for(user_id: str | None) -> tuple[str, ...]:
	if user_id is None:
	return tuple(f"ratelimit:cost:user:{scope}:{POSTHOG_CODE_PRODUCT}:*" for scope in SCOPES)
	if any(c in user_id for c in ("*", "?", "[")):
	raise ValueError(f"user_id contains Redis glob characters: {user_id!r}")

Prompt To Fix With AI

This is a comment left during a code review.
Path: services/llm-gateway/src/llm_gateway/cli/reset_posthog_code_usage.py
Line: 26-28

Comment:
If an operator passes a `user_id` containing Redis glob characters (`*`, `?`, `[`), the exact-key and wildcard patterns generated by `_patterns_for` will silently expand beyond the intended user. For example `--user-id "1*"` would produce the match pattern `...posthog_code:1*`, which matches every user whose ID starts with `1`. A lightweight guard with an early error prevents this accidental over-deletion.

```suggestion
def _patterns_for(user_id: str | None) -> tuple[str, ...]:
    if user_id is None:
        return tuple(f"ratelimit:cost:user:{scope}:{POSTHOG_CODE_PRODUCT}:*" for scope in SCOPES)
    if any(c in user_id for c in ("*", "?", "[")):
        raise ValueError(f"user_id contains Redis glob characters: {user_id!r}")
```

How can I resolve this? If you propose a fix, please make it concise.

[charlesvien]

L G T M 🍻

[adboio]

Merge activity

• May 27, 6:42 PM UTC: @adboio merged this pull request with Graphite.

[deployment-status-posthog]

Deploy status

Environment	Status	Deployed At	Workflow
dev	✅ Deployed	2026-05-27 19:13 UTC	Run
prod-us	✅ Deployed	2026-05-27 19:40 UTC	Run
prod-eu	✅ Deployed	2026-05-27 19:42 UTC	Run