Sync coding agent sessions and memory between laptops
A developer built mem-mastero to carry Claude Code, Codex and Copilot CLI sessions and memory across machines, using GitHub or Google Drive as the sync store.
Source
@shafiq_2001 on X · 2026-10-20
Written in our own words. Credit to the original author. Link checked 2026-10-20.
What they did
A developer built mem-mastero to carry Claude Code, Codex and Copilot CLI sessions and memory across machines, using GitHub or Google Drive as the sync store.
Result (as claimed)
Released for feedback; works with three agent CLIs.
Tools they used
Cost: Claude Code: from $17/mo; OpenAI Codex: free plan, paid from $8/mo; GitHub Copilot: free plan, paid from $10/mo; GitHub: free plan, paid from $4/user/mo.
Set it up
Pick a contained repo or task
Start on a branch or side project where mistakes are cheap.
Install and configure
Set up Claude Code, OpenAI Codex, GitHub Copilot, GitHub, Google Drive. Read what it can run on your machine and limit permissions where possible.
Run it on a real task
Give it a well-scoped issue and let it work. Review the diff like any pull request.
Add guardrails
Keep tests and CI in the loop, and never let an agent push to main or touch production secrets unattended.
Copy the full setup prompt
Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.
You are helping me set up this AI use case end to end in Claude Code. Goal: Sync coding agent sessions and memory between laptops What the original author did: A developer built mem-mastero to carry Claude Code, Codex and Copilot CLI sessions and memory across machines, using GitHub or Google Drive as the sync store. Reported result (as claimed by the author): Released for feedback; works with three agent CLIs. Source: https://x.com/shafiq_2001/status/2112417956458381820 Tools they used: Claude Code, OpenAI Codex, GitHub Copilot, GitHub, Google Drive Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Codex. Goal: Sync coding agent sessions and memory between laptops What the original author did: A developer built mem-mastero to carry Claude Code, Codex and Copilot CLI sessions and memory across machines, using GitHub or Google Drive as the sync store. Reported result (as claimed by the author): Released for feedback; works with three agent CLIs. Source: https://x.com/shafiq_2001/status/2112417956458381820 Tools they used: Claude Code, OpenAI Codex, GitHub Copilot, GitHub, Google Drive Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Grok Bot. Goal: Sync coding agent sessions and memory between laptops What the original author did: A developer built mem-mastero to carry Claude Code, Codex and Copilot CLI sessions and memory across machines, using GitHub or Google Drive as the sync store. Reported result (as claimed by the author): Released for feedback; works with three agent CLIs. Source: https://x.com/shafiq_2001/status/2112417956458381820 Tools they used: Claude Code, OpenAI Codex, GitHub Copilot, GitHub, Google Drive Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
The Daily 5
Get five new use cases tomorrow morning
Free. Real sources. Unsubscribe any time.
Guides for this use case
How to vibe code an app with Claude Code · How to build agent memory and context layers · How to add memory to coding agents · How to run multiple coding agents together
Related use cases
Give every coding agent the same structured delivery workflow
AI-DLC from AWS Labs turns AI coding assistants into a structured, verifiable software delivery workflow. One harness-neutral core runs in Claude Code, Kiro, Codex CLI, Cursor, opencode and GitHub Copilot, installed with one command.
Let your coding agent sessions message each other without you relaying
A developer open-sourced agentsocks so his coding agents can talk to each other. A Claude Code or Codex session can message another session, ask it a question or hand it a tracked task, and the answer comes back into the session that asked.
See what your coding agent sessions really cost
Frugal Tokens reads your coding agent sessions and shows overall usage, estimated working time, overlapping sessions and where spend comes from across models and cache misses.
Send results straight from your coding agent to a teammate's agent
Instead of copying Codex output into Slack so a teammate can paste it into Claude Code, a developer built AgentDrop, an open-source tool that sends results, files and context directly from one agent to another.