Running Claude Code on your own server: three problems to solve

What you have to handle yourself

Environment: install dependencies, pin the egress IP, keep the machine online.

Session: the process has to survive SSH disconnecting, and the next connection has to resume the conversation rather than start blank.

Sync: remote edits need to reach your local editor, local edits need to reach the server, and simultaneous edits on both sides need a way to converge.

Safety: .env files, keys, and credentials must not get swept up into the sync.

The hard part is conflicts, not transfer

Moving files is easy. The hard part is what happens when both sides changed the same file. Silent overwriting is the worst possible answer — you find out weeks later that an edit vanished.

BestCodex shows a side-by-side comparison and lets you decide instead of choosing for you. Secret files are excluded by default so credentials don't get pushed to the remote.

The BestCodex path

Download the launcher (macOS 13+ on Apple silicon or Intel, or Windows 10/11 64-bit), sign in inside the app, and switch to the Claude tab.

The first run explains itself before connecting. After that workspaces are unlimited and terminals are persistent — close the window, come back, and the session is still there.