rtk-ai/rtk

Add support for docker compose (build, up, exec, ps, restart)

Open

#1727 aperta il 5 mag 2026

Vedi su GitHub
 (2 commenti) (0 reazioni) (0 assegnatari)Rust (2914 fork)batch import
area:clienhancementhelp wantedpriority:medium

Metriche repository

Star
 (48.085 star)
Metriche merge PR
 (Merge medio 11g 1h) (45 PR mergiate in 30 g)

Descrizione

Problem

rtk discover flagged docker-compose as my single largest unhandled command surface — across 30 days I had:

  • docker compose ... — 724 invocations
  • docker-compose build — 222
  • docker-compose up — 194
  • docker-compose exec — 185
  • docker-compose ps — 101

Total: ~1,426 invocations not benefiting from RTK. docker exec is already handled (rtk docker), but the compose family isn't.

Proposal

A rtk compose <subcommand> (or auto-detection of docker compose ... / docker-compose ...) that compresses the same way rtk docker does:

  • build — collapse layer-cached steps, surface only actual build steps + warnings/errors
  • up / up -d — drop ASCII spinners and "Container ... Started" noise; one line per service
  • ps — same compact table style as rtk docker ps
  • exec — passthrough (no compression needed, but routes through hook)
  • restartok <service> style, like rtk git push

Why it matters

For projects on docker-compose, every up/build/ps cycle dumps hundreds of tokens of progress UI into Claude's context. Estimated savings on my usage alone: ~80% on build/up output.

Guida contributor