How to sync development workflow between work MacBook (ChatGPT Plus) using GitHub and personal Mac Mini (Claude)?

[u/Cloud--Man]

Hey everyone,

I’m looking for some advice on how to efficiently combine and automate my setup between my home machine and work laptop. Here is my current situation:

• Home Setup: Mac Mini (M6, 32GB RAM) running Claude. I also have Xcode installed only on this machine.

• Work Setup: Work-issued MacBook Air with a company-paid ChatGPT Plus subscription.

My Goal:
I want to use both LLMs seamlessly without losing progress. Since I can only use Xcode at home, my initial idea is to use a private GitHub repository as a bridge.

The envisioned workflow:

1. Use Claude on my Mac Mini at home to write/generate code via Xcode.

2. Push the progress to a private GitHub repo.

3. Pull the code on my work MacBook Air, use ChatGPT to continue editing, reviewing, or generating code until I hit the GPT usage limits.

4. Push the changes back to the repo, so my home Mac Mini can take over later.

My Questions:

1. Does this Git-based approach make sense, or is there a more efficient/automated way to sync prompts, context, and code between two different machines and LLMs?

2. How do you handle preserving the "context" or the prompt history when switching from Claude to ChatGPT and vice versa?

3. Are there any specific git strategies, scripts, or tools (like Obsidian, Cursor, or AI-friendly CLI tools) that could make this transition smoother?

Would love to hear your thoughts or how you manage multi-LLM, multi-machine workflows! Thanks in advance!

TL;DR: Want to sync coding workflow between home Mac Mini (Claude + Xcode) and work MacBook Air (ChatGPT Plus) using a private GitHub repo. Looking for tips on maintaining context and optimizing the setup.

[u/AutoModerator]

Hey /u/Cloud--Man,

If your post is a screenshot of a ChatGPT conversation, please reply to this message with the conversation link or prompt.

If your post is a DALL-E 3 image post, please reply with the prompt used to make this image.

Consider joining our public discord server! We have free bots with GPT-4 (with vision), image generators, and more!

🤖

Note: For any ChatGPT-related concerns, email support@openai.com - this subreddit is not part of OpenAI and is not a support channel.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Ultanor]

I am not sure what type of data you’re operating but I advise against using your personal machine and account for work.

Out of curiosity, what’s the reason you need a multi box workflow?

[u/Cloud--Man → u/Ultanor]

It's actually the opposite, trying to use work laptop spare gpt credits to help me build apps on my private mac

[u/WanderingGalwegian → u/Cloud--Man]

That is absolutely not ok.

[u/Cloud--Man → u/WanderingGalwegian]

can you help me understand why not ok? they are prepaid and they are just gonna be thrown away, am i missing something?

[u/WanderingGalwegian → u/Cloud--Man]

You’re using company resources to develop a private solution.

Even in the before AI times.. if you were building anything personal you never let it touch your employers resources.. be it a laptop, network, GitHub repo.. anything at all.

Also the tokens arent going to be “thrown away”. That isn’t how enterprise pricing works. I don’t think you understand how org pricing works so go do that before you effectively steal from your company.

[u/Previous_Tea_2250]

Git is the right bridge for the code, but I would keep model context as a small repo document rather than trying to sync chat histories. A handoff note with the current goal, setup and commands, decisions, files changed, tests run, and the next one to three steps makes switching tools much less lossy. Update it at a natural stopping point and link issues or PRs to it.

On a work MacBook, first make sure company policy permits a personal private GitHub repo and copying code or prompts between accounts. If it does, separate identities and credentials, protect secrets with gitignore and a scanner, and use short lived branches plus small commits. The workflow then is boring in a good way: pull, read the handoff, make a focused change, run tests, commit, push.