rtk-ai/rtk

Feature request: add `tea` subcommand for Gitea CLI

Open

#1,713 opened on May 5, 2026

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

Repository metrics

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

Description

Summary

RTK currently has a gh subcommand that filters and compacts GitHub CLI output. I'd like the same treatment for tea — the official Gitea CLI — so that rtk tea <cmd> produces token-optimized output in the same way.

Motivation

I use Gitea for self-hosted repos alongside GitHub. The tea CLI produces verbose, human-formatted output (issue lists, PR details, repo info) that is similarly token-heavy to raw gh output. Having an rtk tea subcommand would extend the same 60-90% savings to Gitea workflows.

Common commands that would benefit

  • tea issue list — tabular output with full descriptions
  • tea pr list / tea pr show — PR metadata and diffs
  • tea repo info — repo statistics
  • tea release list — release listings

Tea version

tea 0.14.0  golang: 1.26.2  built with: Homebrew

Reference

The gh subcommand seems like a natural template for this. Happy to help test or contribute if there's guidance on adding a new subcommand.

Contributor guide

Research direction
Study the existing `gh` subcommand implementation in RTK to understand the pattern. Then, reproduce similar logic for the `tea` CLI by analyzing its output format and adjusting token optimization accordingly.
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70