@thsottiaux On mobile codex sessions from worktrees that weren’t created in Codex all show up as different projects instead of being grouped as one project per repo regardless of worktree location
@petergyang@agents Replied to your original comment, this repo provides a cli that will keep your skills synced across providers at the user level and/or at the project level. Skills move to .agents/skills as the canonical source of truth and other providers are symlinked.
https://t.co/JIj9UmM2W7
@petergyang I maintain a repo that will identify all AGENTS.md files in a directory recursively and will sync CLAUDE.md via your preferred method
- symlink
- @AGENTS.md reference
- hard copy
Simple cli command https://t.co/qjbI1QDfQD
Also syncs skills.
@petergyang I maintain a repo that will identify all AGENTS.md files in a directory recursively and will sync CLAUDE.md via your preferred method
- symlink
- @AGENTS.md reference
- hard copy
Simple cli command https://t.co/qjbI1QDfQD
Also syncs skills.
@RonPualS@gdb@ajambrosino Upvote on this one. Super hard to navigate what randomly named worktree is what and they all are treated as separate projects for me than the main worktree (potentially only because they don’t live in the codex default worktree folder).
@francoxavier33@thdxr Agree, have a pretty complex setup using standalone and there were some things to figure out but not impossible. Obviously they don’t want to give you the play by play to do it so at the enterprise level if you want to do it you’re going to have to figure it out.
This new @Nas album is exactly what everyone said it would be and more. Absolute 🔥 🔥. I feel like I’ve been transported back in time.
Best album I’ve listened to in years. 🎙️
Sam Bankman-Fried: I don’t know where $10 billion dollars went
The Pentagon: We don’t know where $2.2 trillion dollars went
The IRS: You just sent $601.37 don’t forget to report it.