@Karthikvarmamkv@jetbrains fair, worktrees are about agents not stepping on each other, not about what they can read. repo only mount is the cleaner line. the annoying bit is letting it push from inside without handing over your keys
psa if you're installing codex on windows: when it asks whether you trust C:\Users\yourname, hit no. that's your entire user folder. pizur only starts it inside the workspace folder, and honestly that's how i'd run it even without pizur
https://t.co/ZQhE25QJau
@amitmuflis@thinkingjimmy@thsottiaux oh huh, didn't know it kept the newest 15. half my old chats are pinned so that's probably why nothing ever got cleaned, thanks
@tejaskalpande nice, did the same with an old thinkpad. set HandleLidSwitch=ignore in logind.conf or it'll suspend on you, and keep sessions in tmux. i mostly drive mine from my phone through pizur now https://t.co/w0eHTqQLCN
@sidborderwala@capydotai For any switch, check where the agents run and what happens to sessions when your laptop sleeps. Pizur is the local CLI route (Claude Code/Codex/Cursor); disclosure, i work on it.
@StackDhruv Separate local orchestration from hosted sessions; test worktree isolation and what happens when a laptop sleeps. Pizur fits local machines (Claude Code/Codex/Cursor CLI); disclosure, i work on it: https://t.co/xNoPTBBnJd
@sam_ess604@thsottiaux not a real fix but excluding the repo folder from defender and turning on core.fsmonitor cut the git.exe pileup a lot for me. still wild that opening one task does that
@thinkingjimmy@thsottiaux not built in as far as i know. every week or so i run git worktree prune and delete whatever's in ~/.codex/worktrees for branches that already merged, frees up a surprising amount
@Xiao_bu_yu@thsottiaux same wish. i got tired of waiting so codex just lives on my server and i poke it from my phone through pizur, mostly approving plans and reading diffs on there https://t.co/w0eHTqQLCN
@oderajoseph user one for the generic stuff like git status, lint, the test runner. project settings only for repo specific things like weird make targets. that way a new repo is already quiet on day one
@StefonGlover_@CloudflareDev what fixed this for me was just not running it on the laptop. codex sits on an old desktop inside tmux and the laptop only ssh's in, so closing the lid kills the ssh and nothing else
@krika2810 cloud ones are great until the task needs something only your machine has. local db with real data, a gpu, a service behind a vpn. that's why my mini is still on. i drive it from my phone through pizur now, feels close enough to the cloud version https://t.co/w0eHTqQLCN
do you let your coding agent make commits on its own or always do them yourself? i keep going back and forth. letting it commit makes rollback easy but the messages are junk and i squash it all at the end anyway
@andrewmcgehee tmux. ssh from the phone drops all the time and the session just keeps going, reattach and it's like nothing happened. also caffeinate -i in a terminal if you ever want amphetamine without the app
@achourdev yeah that one bugs me too. for now i just make the worktree myself (git worktree add ../feat-x -b feat-x) and open that folder as the project, it treats it like any other repo. messier sidebar but it works
@morganlinton@seachee@claudeai same, 3-4 going and one of them is always just sitting on a question for 20 min. a Stop hook that sends a push (ntfy works fine) fixed most of it for me. lately i route them through pizur so the questions show up in one chat on my phone https://t.co/w0eHTqQLCN
@SuperfluxSF if the worktrees live inside the repo, gitignore that folder so codex stops walking it. pnpm with its shared store also helps, each worktree stops being a full node_modules copy. 77 full installs is a lot for anything to index
@ohheyyang same setup here. tmux on the mini helped a lot, a dropped ssh doesn't kill a half done run anymore. and yeah separate login per machine, the refresh logout thing got me twice before i figured out what was going on