You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I share settings.json across multiple devices, but this command turned my symlink into a regular file.
I consider this a serious issue.
Another problem is that settings.json shouldn't contain absolute paths, and the patch content also includes absolute paths, making it impossible to share across multiple machines. I refactored them to relative paths.
As for why rtk.md is injected into CLAUDE.md, another issue already asked about it, so I won't ask here.
I’m taking this issue. I’ll fix settings.json patching so symlinked settings files are preserved (no symlink replacement), with tests, in a focused PR against develop.
Activity
TechWizard9999 commentedon Mar 18, 2026
I’m taking this issue. I’ll fix settings.json patching so symlinked settings files are preserved (no symlink replacement), with tests, in a focused PR against develop.
TechWizard9999 commentedon Mar 18, 2026
I’ve submitted a PR to address this issue: #675
Changes include:
settings.jsonduring patch writes (no symlink replacement)Validation run:
cargo fmt --all --checkrtk cargo clippy --all-targetsrtk cargo testPlease review when you get a chance.
pszymkowiak commentedon Mar 20, 2026
🔍 Automated Triage
bughighSummary
rtk init --global destroys settings.json symlinks by overwriting with a regular file; two PRs (#675, #2088) already in progress with fixes.
📁 Relevant files
src/init.rsTriaged automatically by wshm · This is an automated analysis, not a human review.
fix(init): preserve settings.json symlink during atomic write
fix(init): preserve settings.json symlink during atomic write
fix(init): preserve settings.json symlink during atomic write
chore: sync fork with upstream rtk-ai/rtk v0.43.0 (#22)