rtk-ai/rtk

Feature request: python3 command support

Open

#784 opened on Mar 23, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
effort-mediumenhancementgood first issue

Description

Use Case

Python scripts are frequently executed inline (heredocs) or directly during AI-assisted development sessions. The output from Python scripts — tracebacks, print statements, data dumps — can be verbose and consume unnecessary context tokens.

Statistics (from rtk discover)

  • ~570 python3 commands in 30 days (single user)
  • ~420 heredoc invocations (python3 << 'EOF' ... EOF)
  • ~150 direct script executions (python3 script.py)

Proposed Behavior

rtk python3 could:

  • Compress long tracebacks (show only the relevant frames)
  • Truncate large data output (e.g., list/dict dumps)
  • Deduplicate repeated log lines (same as RTK already does for other commands)

Impact

Second most frequent unhandled command category in rtk discover output.

Contributor guide

Tech stack
rustpython
Domain
clideveloper experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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
Basic RustUnderstanding of RTK command structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Review existing command implementations (e.g., how `rtk` handles compression and deduplication) in the source code, likely under `src/commands/`. Examine the current `python3` command placeholder if any. Test with sample Python output to understand the expected behavior. Check issue comments for any additional context.