Command channel autoscaling
SkillDev toolsMaintain Nypsi's automatic command-channel capacity tracking, including rolling load activity, sustained-activity windows, inactivity closure, resize cooldowns, and minimum channel count. Use when changing cmd channel activity tracking or autoscaling behavior.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Command channel autoscaling skill
What this skill tells your AI
The instructions your AI receives, as published by mxz7/nypsi in .agents/skills/cmd-channel-autoscaling/SKILL.md and read by ahel’s review.
Track scale-up load as one combined activity stream:
- Add non-bot
messageCreateevents totrackCmdChannelLoad()with amessagesource. - Add chat-input interactions to the same tracker with a
slash-commandsource. - Store both in the same load activity Redis sorted set. Do not count bot replies, components, or autocomplete toward scale-up load.
Evaluate the combined activity in src/scheduled/clusterjobs/cmd-channels.ts. Split the trailing
60 seconds into two 30-second halves. Every active channel must meet
LOAD_EVENTS_PER_HALF_WINDOW in both halves before opening another channel. Keeping two halves
requires sustained load instead of allowing one short burst to trigger scaling.
Scale-down uses the separate activity TTL key. Messages and interactions refresh that 30-minute
TTL. Only the highest-numbered active channel is a removal candidate, and never reduce below
MIN_CHANNELS.
Run make check after changes.
Signals
- GitHub stars
- 69
- Forks
- 31
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
cmd-channel-autoscaling- Source
- github.com/mxz7/nypsi