Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

rate-limit-guard: detect an account switch and tell the model the new account's limits

Abierto
  • ¿Algo no está bien?
#6,445 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
shell
Área
developer-experience, tooling

Línea de trabajo

Start from the rate-limit-guard plugin and how it records usage for a session (the prompt.submit hook context described in the issue). Read current Claude Code docs for auth/status/usage signals and which hook fires after a switch; also read docs/conventions/hook-precision for the stay-quiet test. Done means a switch notice with the new account's limits on the next turn, no old windows after the switch, and no notice when the account is unchanged.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

needs-human needs-triage

Problem

When the operator rotates to another Claude account mid-session, the model keeps acting on the
previous account's usage limits. rate-limit-guard's notices still report the old account's
windows, and nothing tells the model the account changed, so it throttles fan-out, defers work
"until the reset", or suggests handoffs that the new account does not need.

Observed 2026-10-05 in a session on feat/upstream-docs-cache (PR #6348): after the operator
switched accounts, the prompt.submit hook context still said "rate-limit-guard: 7-day window at
or above 90%, resets at 2026-10-07 03:00 UTC", and the session planned around that reset until the
operator corrected it by hand.

Ask

  1. Detect an account switch: the signed-in account identity (or organization) differs from the one
    the guard last recorded for this session or machine.
  2. On a switch, invalidate the cached usage snapshot and re-read the limits for the new account.
  3. Inject one notice into the session on the next turn, for example: "Account switched to
    ; current limits: 5-hour window N%, 7-day window N%, resets at ...; earlier limit
    notices in this session no longer apply."
  4. Stop emitting the previous account's numbers once the switch is seen.

Open questions

  • Which signal identifies the account reliably and locally (the auth state Claude Code exposes to
    hooks or mods, a status payload, the usage endpoint's response)? Needs a check against current
    Claude Code docs before design.
  • Which hook or mod event fires early enough after a switch (UserPromptSubmit, a status-line tick,
    SessionStart on resume)?
  • Should context-guard take the same notice, so the model can tell a context-size warning from a
    usage warning?

Acceptance

  • After an account switch, the next model turn carries a notice naming the switch and the new
    account's current limits.
  • No notice after the switch reports the old account's windows.
  • A stay-quiet test: no switch notice when the account is unchanged
    (docs/conventions/hook-precision).
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
8 h 24 min
PR fusionados (30 d)
947

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.