rtk-ai/rtk
Ver no GitHubFeature: Add filter for `docker compose logs` (high-volume, currently proxied raw)
Open
#578 aberto em 13 de mar. de 2026
area:clieffort-mediumenhancementhelp wantedpriority:high
Métricas do repositório
- Stars
- (48.085 stars)
- Métricas de merge de PR
- (Mesclagem média 11d 1h) (45 fundiu PRs em 30d)
Description
Summary
docker compose logs is currently intercepted via rtk proxy but has no output filter, resulting in 0% token savings. This is a high-volume command that would benefit significantly from filtering.
Usage data
From rtk discover on my machine (last 30 days):
docker compose logs: 606 runs, estimated ~200K+ tokens saveabledocker-compose logs(legacy syntax): 40 additional runs
Expected behavior
rtk docker compose logs should filter output similarly to rtk docker logs, which currently achieves ~78-83% savings.
Suggested filter behaviors
- Tail truncation: When
--tail=Nis specified, only return the last N lines (already done fordocker logs) - Timestamp normalization: Collapse repeated timestamps into a single header
- Service prefix deduplication: When multiple services log the same line (e.g., health checks), collapse with a count
- ANSI stripping: Remove color codes that bloat token count
- Known noise patterns: Filter out common low-signal lines (e.g.,
health: starting, repeated keepalive pings)
Related
rtk fallback: grep -rn...also hits 0% savings on some patterns — the grep parser appears to fall back silently on certain flag combinations (-rnwith path args). Worth investigating alongside this.
Environment
- RTK version: $(rtk --version 2>/dev/null)
- Shell: zsh / macOS Darwin 25.2.0