rtk-ai/rtk

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

Fermée

#1 465 ouverte le 22 avr. 2026

Voir sur GitHubGuide contributeur
 (4 commentaires) (13 réactions) (0 personne assignée)Rust (2 914 forks)batch import
P1-criticalbugeffort-smallgood first issue

Métriques du dépôt

Stars
 (48 085 étoiles)
Métriques de merge PR
 (Merge moyen 11j 1h) (45 PRs mergées en 30 j)

Description

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.

Guide contributeur

Direction de recherche
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.
Stack technique
rust
Domaine
cli
Type d'issue
Bug
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-3 heures
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
Récente
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
Claire
Prérequis
Basic RustUnderstanding of CLI toolsFile system permissions
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
65