My Claude Code setup lived on three machines and none of them agreed

May 16, 2026 · 6:15 PM UTC ·6 min read · 0 reactions · 0 comments · 35 views

#web development #tooling #synchronization #opensource #supabase #Branko Stancevic #ClaudeSync #Supabase #Netlify #React #Postgres #Edge Functions #GitHub

TL;DR · WeSearch summary

Branko Stancevic created ClaudeSync to solve inconsistencies in his Claude Code setup across multiple machines. The tool enables manual, controlled synchronization of configurations, skills, and plugins without automatic file watching. It uses a Node agent, Supabase for backend services, and a React dashboard for user interaction.

Key facts

▪ClaudeSync was built to synchronize Claude Code configurations across multiple devices reliably.
▪The system avoids automatic syncing to prevent conflicts and partial updates during file edits.
▪It uses Supabase Realtime for communication, allowing agents behind firewalls to receive sync commands securely.
▪The dashboard provides a visual diff of changes before users choose what to sync.
▪Absolute file paths in configuration files posed a challenge and required special handling to ensure cross-machine compatibility.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/landb/my-claude-code-setup-lived-on-three-machines-and-none-of-them-agreed-17ok
Publication time	Sat, 16 May 2026 18:15:31 +0000
Retrieval time	2026-05-16T18:40:19.021Z
Last seen	2026-05-16T18:40:19.021Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	KM3rjdRmS9G2
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 429391) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Branko Stancevic Posted on May 16 My Claude Code setup lived on three machines and none of them agreed #claude #supabase #opensource #webdev Branko, you built another tool? Yes. Yes I did. And before you roll your eyes — hear me out, because this one scratched an itch that was driving me genuinely crazy. I run Claude Code on three machines. My laptop. My desktop. My work box. And every single one of them had its own little personality. A CLAUDE.md from two weeks ago on one.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments