rtk-ai/rtk

Windows: add winget package support

Open

#383 opened on Mar 6, 2026

View on GitHub
 (7 comments) (14 reactions) (1 assignee)Rust (2,914 forks)batch import
area:cieffort-mediumenhancementhelp wantedplatform:windowspriority:low

Repository metrics

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

Description

Summary

RTK is not available on winget (Windows Package Manager). Windows users currently have to either use cargo install or manually download the .zip from GitHub releases.

Current installation options on Windows

  • cargo install --git https://github.com/rtk-ai/rtk — requires Rust toolchain
  • Manual download from GitHub releases (rtk-x86_64-pc-windows-msvc.zip)

Expected

winget install rtk-ai.rtk

Steps to add winget support

  1. Create a winget manifest under microsoft/winget-pkgs (see contribution guide)
  2. Automate manifest updates in the release CI workflow (.github/workflows/release.yml)

A GitHub Actions step similar to the existing Homebrew formula update could handle this automatically on each release.

Context

Reported by Benjamin on Discord (Clean Coder community) — Windows users expect package manager support and the current options add unnecessary friction.

Contributor guide

Research direction
Study the existing release workflow (.github/workflows/release.yml) and the Homebrew formula update step. Create a similar step to generate a winget manifest and submit it to the microsoft/winget pkgs repository. Ensure the manifest uses the correct package identifier (rtk ai.rtk) and references the latest release asset.
Tech stack
rust
Domain
clidevops
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.
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
GitGitHub Actionswinget
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40