Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#6,445 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
shell
Ambito
developer-experience, tooling

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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).
Lingua principale
Shell
Stelle
22
Fork
2
Merge medio
8h 25m
PR unite (30g)
944

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di melodic-software/claude-code-plugins

Tutte le issue di melodic-software/claude-code-plugins

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.