rtk-ai/rtk

Add commands - PM2 & Redis-cli

Open

#1,859 opened on May 12, 2026

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Rust (2,914 forks)batch import
area:clienhancementhelp wantedpriority:medium

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

Hi,

Feature Request: Add support for pm2 and redis-cli

Commands

  • pm2 logs, pm2 list, pm2 status, pm2 env, pm2 restart, pm2 reload
  • redis-cli get, redis-cli del, and other redis-cli subcommands

Why

Both commands appear frequently in Node.js/backend Claude Code sessions and produce verbose output that pollutes the context window.

From rtk discover on my setup (88 sessions, last 30 days):

Command Count
pm2 logs 57
pm2 list 36
pm2 restart 34
pm2 reload 23
pm2 status 6
pm2 env 5
redis-cli 31
redis-cli get 11

Expected compression

pm2 logs — output is very repetitive (timestamps, repeated log lines, process names). Truncation + deduplication should yield 70-80% savings.

pm2 list / status — tabular output with fixed-width padding. Structure compression similar to ps aux (already handled by RTK at 91.8%).

redis-cli — responses are short for single-key queries but can be large for KEYS *, HGETALL, or LRANGE. Truncation + type-aware formatting would help.

Happy to test

I can run benchmarks on real output if you need before/after token counts.

Contributor guide

Research direction
Study the existing command compression implementations (e.g., ps aux) in the RTK codebase. Then implement similar pattern detection, truncation, and deduplication for pm2 logs, pm2 list/status, and redis cli output. Use the existing infrastructure for structured output compression.
Tech stack
rust
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustCLI basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70