claude-to-opencode
Advanced tools
Safely preview and move Claude Code memory, instructions, rules, commands, agents, skills, and MCP config into OpenCode.
Move an existing Claude Code setup into OpenCode without rebuilding it by hand.
npx claude-to-opencode
npx claude-to-opencode --apply
The first command is a dry run. It shows the exact destinations and everything that stays manual.
It handles the current project's auto memory, global and project instructions, unconditional rules, commands, subagents, and local or remote MCP servers. Auto memory stays in its Claude directory and is referenced by OpenCode, so later updates remain visible. OpenCode reads Claude skills directly, so the command leaves those files in place. Existing destinations and secret-looking plaintext values are not copied.
Path-scoped Claude rules, hooks, permissions, and sessions stay manual because OpenCode does not give them the same semantics.
This is the search-friendly entry point for dsh-movein, which owns the implementation and safety tests.
FAQs
Keep Claude Code memory and PreToolUse or PostToolUse command guardrails when moving to OpenCode. Dry run first.
The npm package claude-to-opencode receives a total of 9 weekly downloads. As such, claude-to-opencode popularity was classified as not popular.
We found that claude-to-opencode 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.
Security News
arXiv now limits authors to two submissions a month as AI slop overwhelms moderators, delays good papers, and sparks debate over applying the limit to everyone.
Research
/Security News
A new GhostAction wave hits hundreds of GitHub repos, expanding CI/CD secret theft to cloud and AI credentials in source code and git history.
Research
/Security News
Tensorlake npm SDK version 0.5.144 was compromised in a ChainDrop / Shai-Hulud attack, delivering credential-stealing malware.