rtk-ai/rtk
Vedi su GitHubFeature Request: Support OpenClaw CLI commands for token optimization
Open
#1244 aperta il 12 apr 2026
area:clieffort-mediumenhancementhelp wantedpriority:low
Metriche repository
- Star
- (48.085 star)
- Metriche merge PR
- (Merge medio 11g 1h) (45 PR mergiate in 30 g)
Descrizione
Summary
RTK is great for standard dev commands, but it doesn't rewrite OpenClaw CLI commands, which are heavily used in OpenClaw-based AI agent sessions (10-20+ calls per session).
Frequently used OpenClaw commands that need RTK coverage
# Most frequent - sent every response via Telegram/Discord
openclaw message send --channel telegram --target <ID> --message ...
openclaw message send --channel discord --message ...
# Status/debug
openclaw status
openclaw gateway status
openclaw plugins list
# Model management
openclaw models status
# Cron
openclaw cron list
# Wiki
openclaw wiki search <query>
openclaw wiki ingest <file>
Suggested token savings
openclaw message sendoutput: strip plugin loading logs ([plugins] ...,[lcm] ...) - saves ~100-200 tokens per callopenclaw statusoutput: compact format with key metrics onlyopenclaw plugins list: table → compact listopenclaw cron list: table → compact list
Current behavior
rtk rewrite returns exit code 1 (no match) for all openclaw commands:
$ rtk rewrite "openclaw message send --channel telegram --target 6572517363 --message test"
# no output, exit 1
Environment
- rtk: 0.35.0
- Platform: Linux (Ubuntu 24.04)
- Use case: OpenClaw AI assistant sessions via Telegram
- OpenClaw repo: https://github.com/openclaw/openclaw
Impact estimate
In a typical OpenClaw session, openclaw message send is called 10-20 times. Each call outputs ~150 tokens of plugin loading logs that are injected into LLM context. Adding RTK support could save 1,500-3,000 tokens per session just from message sends alone.
Thank you for the great tool! 🦞