3 ms·
Don’t get too excited, Claude code still won’t detect skills on .agents/skills.
by clutter55561 16d ago
Don’t get too excited, Claude code still won’t detect skills on .agents/skills.
- jjordan 16d agoDon't worry, it's on the roadmap for Q4 2029.
- vb-8448 16d agoThey have AGI, but they don't have $20 of token budget to add a so basic functionality.
- bel8 16d agoThey probably have an explicit instruction in their own CLAUDE.md to not implement that support.
- sscaryterry 16d agoIts the only explanation. I mean, they are not living under a rock...
- falcor84 16d agoAs evidence that they actually are living under a rock, there's still no proper way to mv a workspace and have it retain all its history and config.
- yoavsha1 16d agothis is seriously nuts. I have so many repos sitting there using old/deprecated/replaced names just because of their idiotic decision to place dir-specific config and memories in ~/.claude
- albert_e 16d agoShould we be able to manually rename those history folders to make the session history show up as --resume options in a new folder?
- nextaccountic 16d agoI suppose you can use claude to build a third party script / cli tool that moves, then edit files on ~/.claude They win either way
- KetoManx64 15d agoI get that it would be nice to have it first party, but they're all just json files that you can just do a bulk awk/sed on. I did this a week ago for about 100 conversations when migrating my convo history to a different username.
- vb-8448 16d agoI heard some of their employees sent to do some PR in podcasts: they are definitively disconnected from the reality. Maybe internally they see really unbelievable things, but my impression is that they pushed so hard on agents that they don't have the grasp of the situation.
- oofbey 16d agoIf not a system prompt telling it not to read those files unless explicitly told to.
- NiloCK 16d agoArtificial General Intransigence
- perganomoly 16d agoSeriously, it’s unbelievable. Shows a serious lack of either understanding or empathy for how people use their product.
- vb-8448 16d agoThey just care much more about their user's data.
- arendtio 14d agoClaude isn't that cheap anymore ;-)
- nomel 16d agoA post-checkout git hook can handle this unfortunate situation. mkdir -p ~/.githooks git config --global core.hooksPath ~/.githooks cat > ~/.githooks/post-checkout <<'EOF' #!/usr/bin/env bash if [ -d .agents/skills ] && [ ! -e .claude/skills ]; then mkdir -p .claude ln -s ../.agents/skills .claude/skills fi EOF chmod +x ~/.githooks/post-checkout
- ahurmazda 16d agoWon’t you have to do it recursively for all child directories?
- verdverm 16d agowe shouldn't have to do this on a per-repo basis, Ant can choose to be a reasonable member of the ecosystem or not
- nomel 16d agoSure, but I have work to do. ;)
- springtimesun 16d agoThis is where I landed when a recent(ish) change broke symlinking for rules files. I didn’t like how hacky it was a first, but now I’m glad I did it. The same hook drives specific rules the non-Claudes get per repo.
- northbridgedev 16d ago[flagged]
- Sugimot0 16d agoI honestly hate .agents it's a big XDGBDS offender. Almost every plugin / lazy platform harness tries to use that dir too so I have to do a bunch of hacks to keep my $HOME clean. Also everyone tries to use a .claude .gemini .codex etc. Annoying that all these tools just completely ignore these things, it's literally like litterers you know it'd be terrible if every tool did this, but you still do it anyway