Skip to main content

​
Install

One command sets up OpenCode along with any other AI tools on this machine:
Pick OpenCode when the CLI asks which tools should share your memory. Already have Atlaso? Run atlaso setup and add it.
Last step — start a fresh OpenCode session so it loads the plugin and the Atlaso MCP server.
OpenCode loads plugin files from your config directory automatically, so the Atlaso CLI installs one bundled file to ~/.config/opencode/plugin/atlaso.js. Nothing is added to your opencode.json and there’s no npm install step.There is also an @atlaso-labs/opencode package on npm. It’s a separate distribution channel and it’s behind the version the CLI ships — don’t add it as well, or OpenCode will load Atlaso twice. Use the CLI.

​
What it wires

​
Notes

  • Everything is automatic — nothing to run day-to-day.
  • Background/cloud agent runs don’t get the memory loop; memory works in your interactive sessions.

​
Removing it

That revokes OpenCode’s access and removes the plugin. By hand: delete ~/.config/opencode/plugin/atlaso.js and start a fresh session.