rtk-ai/rtk

bug: "rtk init -g --agent cursor" errors due to expecting $HOME/.claude

Geschlossen

#1.465 geöffnet am 22.04.2026

Auf GitHub ansehenContributor Guide
 (4 Kommentare) (13 Reaktionen) (0 zugewiesene Personen)Rust (2.914 Forks)batch import
P1-criticalbugeffort-smallgood first issue

Repository-Metriken

Stars
 (48.085 Sterne)
PR-Merge-Metriken
 (Durchschn. Merge 11T 1h) (45 gemergte PRs in 30 T)

Beschreibung

Using the latest version, v0.37.2, on WSL2 (ubuntu), I receive the following error during initial setup:

$ rtk init -g --agent cursor
rtk: Failed to write RTK.md: /home/liam/.claude/RTK.md: Failed to create temp file in /home/liam/.claude: No such file or directory (os error 2) at path "/home/liam/.claude/.tmpznCCwz"

I suspect that --agent cursor still tries to setup Claude and Copilot, but because I don't use either on this device, it errors out. I would expect:

  1. --agent cursor to only install for Cursor.
  2. If claude was used, but the directory didn't exist, create it first, and/or skip over it if the primary agent target isn't claude.

I am able to get around this by manually creating that directory, and re-running, but this still initializes files and pollutes my home directory unnecessarily, which should be avoided.

Contributor Guide

Research-Richtung
Examine the init command logic in the rtk source code, likely in src/commands/init.rs or similar. The issue is that when agent cursor is used, the code attempts to write to $HOME/.claude/ regardless. The fix should ensure the target directory exists (create if missing) and/or skip agent specific paths not relevant to the selected agent. Check if there are existing functions for directory creation and how other agents (e.g., Claude, Copilot) handle directory presence. Also review the error handling to avoid failing entirely when a directory doesn't exist.
Tech Stack
rust
Domain
cli
Issue Type
Fehler
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
3
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
1-3 Stunden
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
Frisch
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
Klar
Voraussetzungen
Basic RustUnderstanding of CLI toolsFile system permissions
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
65