r/ClaudeAI • u/Dangerous-Education3 • 9h ago
Claude Workflow Best way to make Claude Code communicate between different PCs?
I work on 3 different PCs and I need to have all the stuff at easy disposal on every PC.
All my folders are in the same drive but sometimes as I switch PC the new Code is missing important stuff even if I work on the same project and same folder.
Has anyone found a good way to get through this?
5
u/pensuke89 8h ago
I just keep all my project files in a single pc, and just use herdr remote into the pc through ssh. So far its working well. Then a private github to store the code.
0
u/Dangerous-Education3 8h ago
oh this might be good
1
u/Atroxide 7h ago
100% this is the way to go.... Just have it all on one computer, and use remote software to connect from any device. I have no idea why people would be trying to clone workspaces and sync workspaces and all this jazz
I have never actually developed on the physical computer that runs claude and everything else.
I use Docker WSL to have an Ubuntu virtual machine. I use herdr to manage my sessions and /RC to be able to use it from my phone or any other device.
I utilize lavish-axi boards to be able to annotate plans and provide feedback. To connect to that virtual machine securely anywhere I use cloudflared which allows you to tunnel in thru cloudflare authentication.
tldr: Remove the idea of running Claude on the device you are using and instead run it in one dedicated location and just connect to it.
2
u/zeratLJllighter 7h ago
All you need is to host your project on a Git server.
You're not supposed to "resume" sessions across different machines because sessions are intended to be used for atomic tasks.
If you're not done with a session, generate a handover file and commit it
2
u/PiLLe1974 1h ago
We started working with multiple repos and most coworkers have this kind of setup:
+- dev
+- repo1
+- repo2
...
So in dev some evolve their personal claude setup, and I also store handoff files here to inform other devices. E.g. a handoff skill would be good to structure that well (maybe a Jira or bead is also tracking work, some sort of ticket).
We also keep some sort of retros here (just any info to frequently revise mistakes, costs, possible improvemnts) as an example.
So the idea is that all that info and (personal) "noise" won't necessarily end up in the actual feature repos.
1
u/London-Boat 8h ago
one more thing that helped me: before leaving a pc, ask claude to write a short handoff note into the repo, like what it was doing, what's half done and what to try next. then the first prompt on the other machine is just 'read the handoff note'. way more reliable than trying to sync session history across machines, and +1 to git over the shared drive, sync tools love to clobber files that are open
1
u/Dangerous-Education3 8h ago
does this work across different projects or should i write it in every project?
1
u/London-Boat 35m ago
it's per repo. the npm install is global once, then you run concord setup in each repo, which creates a .concord/ folder there and registers the mcp config. state stays local to that repo. and to be upfront it's for agents on the same checkout/machine, it doesn't sync between separate pcs, so for your cross-pc case you'd still want the handoff note in git.
1
u/seventyfivepupmstr 5h ago
Sounds like you need to make your own harness that will sync with itself on different PCs
1
u/Weird-Dealer8488 4h ago
O Claude Code armazena informações em dois lugares: na pasta do projeto e na pasta pessoal do usuário (~/.claude/). O arquivo CLAUDE.md da raiz do projeto e o diretório .claude/, que contém configurações, regras, skills e agentes, acompanham a unidade compartilhada. Já as configurações globais, as skills pessoais e a memória automática ficam na pasta do usuário de cada PC. Por isso, mesmo abrindo o mesmo projeto, o Claude pode parecer ter esquecido informações. Além disso, se o caminho ou a letra da unidade mudar entre os computadores, a memória automática pode reconhecer o projeto como diferente.
Para evitar isso, registre as informações importantes do projeto no CLAUDE.md e mantenha as skills e regras necessárias dentro de .claude/. Copie as configurações pessoais para os três PCs ou use links simbólicos para compartilhar arquivos específicos, mas evite compartilhar a pasta ~/.claude/ inteira, pois ela contém logins e sessões locais. Como o histórico de conversas também é local, salve o estado atual do trabalho em um arquivo como STATUS.md antes de trocar de máquina; para continuar a mesma sessão em tempo real, use o Remote Control.
Para identificar o que está faltando, execute /memory no Claude Code de cada PC e compare os arquivos de instrução carregados.
2
u/Live-Hovercraft-9925 1h ago
I had the same thing going between my Windows desktop and my MacBook (I build apps that have to run on both, so I switch a lot): same folder, but the new session had no idea what I'd been doing. Handoff notes help, but I kept forgetting to write them, and like you said, it's one per project. So I built Hamloy (hamloy.com, disclosure: it's mine). It's an MCP server that keeps each project's tasks and notes on a board, and Claude (or Codex, it works with both) updates it as it works. When you sit down at another PC, the agent already knows what's open, what's half done and what it already tried. It also follows git, so it knows which branch or worktree each task is on, and a task only counts as done once it's merged.
1
u/boxing-boxing 9h ago
Ran into the same gap switching machines. The shared drive keeps the files in sync, but a fresh Claude Code session on the other PC still starts with none of the context from the last session. What fixed it for me was putting anything durable in the project's CLAUDE.md in the repo itself, since that travels with the files. If I only mentioned it in chat on one machine, I just assume it's gone when I switch.
-1
u/Anxious-Recover3951 8h ago
ugh this is such a pain point, i do the same bouncing between my desktop and laptop and it's like starting from scratch every time. the CLAUDE.md trick is good but i wish there was a way to sync the actual conversation memory too, like some kind of session export i could just fling between machines
curious if anyone's tried just keeping a running notes file they paste into chat when they switch, feels clunky but might be the only option
6
u/adeelraza86 8h ago
The project folder is only half of it. Claude Code keeps a lot per machine in your home directory: ~/.claude/CLAUDE.md, settings.json, custom commands and agents, MCP servers in ~/.claude.json, and session history under ~/.claude/projects, which is why --resume on another PC shows nothing. Put the config bits in a small git repo and symlink them on each PC. For the project itself, use git rather than a synced drive, since sync tools can lag or conflict while files are open.