rtk-ai/rtk

rtk init -g does not respect CODEX_HOME

Open

#1400 opened on Apr 19, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (48,085 stars) (2,914 forks)batch import
bugeffort-smallgood first issueresolved-pending-close

Description

I've moved my codex files into ~/.config/codex, and set CODEX_HOME, but rtk init -g --codex still puts artifacts in ~/.codex.

Contributor guide

Tech stack
rust
Domain
cli
Issue type
bug
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.
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 Rustenvironment variable handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Search the codebase for references to 'CODEX HOME' to find where it is read, then compare with the logic that determines the default path for artifacts. The `rtk init g` command likely writes to `~/.codex` directly without checking the environment variable. Look in the main entry point or configuration module for the current path resolution.