
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
opencodesync
Advanced tools
Sync OpenCode settings and session contexts across devices via GitHub Gist
Start coding on your laptop. Continue on your desktop. Never lose context.
Seamlessly sync your OpenCode settings, custom agents, and AI session contexts across all your devices.
You're deep in a coding session on your work machine. You've built up context with your AI assistant - it understands your architecture, your decisions, your next steps. Then you need to switch to your home computer.
Without opencodesync: Start from scratch. Re-explain everything. Lose momentum.
With opencodesync: One command. Full context restored. Keep building.
npm install -g opencodesync
opencodesync init
That's it. The wizard walks you through setup and automatically syncs your settings.
First device? → Creates a new Gist and offers to push your current config
Second device? → Finds your existing Gist and offers to pull everything down
| What | Synced |
|---|---|
Main config (opencode.json) | ✅ |
Custom agents (agent/*.md) | ✅ |
Custom commands (command/*.md) | ✅ |
Global instructions (AGENTS.md) | ✅ |
Plugin configs (*.jsonc, oh-my-opencode.json) | ✅ |
Skills directory (skills/**) | ✅ |
| Session contexts | ✅ |
Export your session before switching devices:
/context-export "Auth Implementation" --guidance "focus on OAuth decisions"
Resume on any machine:
/context-import "Auth Implementation"
Your AI picks up exactly where you left off.
Morning at the office:
opencodesync pull # Get latest from home
# ... work on features ...
/context-export "Feature Progress" # Save your context
opencodesync push # Sync to cloud
Evening at home:
opencodesync pull # Get settings + context
/context-import "Feature Progress" # Resume with full context
# ... continue seamlessly ...
| Command | What it does |
|---|---|
opencodesync init | Set up GitHub token and encryption passphrase |
opencodesync push | Upload your settings to the cloud |
opencodesync pull | Download settings from the cloud |
opencodesync status | Check what's changed since last sync |
Use --verbose on any command for detailed output.
| Command | What it does |
|---|---|
/context-export [name] | Save current session as a portable context |
/context-import [name] | Load a saved context into your session |
/context-list | See all your saved contexts |
/context-prune <name> | Delete old contexts |
Context exports are AI-generated summaries, not raw data. They capture:
They never include:
Your intellectual property stays safe.
| Error | Solution |
|---|---|
| "Not configured" | Run opencodesync init |
| "Decryption failed" | Use the same passphrase as your other devices |
| "Invalid token" | Create a new GitHub token with gist scope |
Need to start fresh? opencodesync init --force && opencodesync push --force
import { createPluginTools, addContext, getAllContexts } from "opencodesync";
const tools = createPluginTools();
const context = addContext("My Context", "Summary...");
const all = getAllContexts();
MIT
Stop context-switching. Start syncing.
FAQs
Sync OpenCode settings and session contexts across devices via GitHub Gist
We found that opencodesync demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.