Your terminal workflow
The commands, the sequence, the way you drive a task from the shell, remembered so OpenCode fits how you already work instead of the other way around.
Persistent memory for OpenCode
OpenCode is fast and terminal-native, but it forgets between runs. Atlaso adds automatic recall and capture through a single npm plugin, so your conventions and decisions are already there in every session, without ever leaving the terminal.
How it works
One command installs Atlaso and wires OpenCode for you: capture hooks, an MCP server, a memory skill, and rules, dropped straight into your OpenCode config. Recall and capture are fully automatic from the first prompt; there's no manual config to edit.
What it installs: Hooks, Skill, Rules.
01
Run one command
Paste the Atlaso install command in your terminal and pick OpenCode when it asks which tools should share your memory. It drops the plugin straight into your OpenCode config: no manual JSON editing, no npm step.
02
Authorize this device
Your first prompt opens the browser to connect this device to your Atlaso account. About a minute, no API keys.
03
Just work
Recall and capture run automatically in every session from then on, the same fully automatic behavior as Claude Code, in the terminal.
What it remembers
Questions
As a local plugin. The Atlaso install command drops a single bundled plugin file into your OpenCode config directory and OpenCode loads it automatically. There's no npm install, and you don't touch the config by hand.
Still have a question?
Write to usOther tools
What OpenCode captures in the terminal is there in your IDE.
Atlaso keeps one memory, not one per app. Connect OpenCode and it draws from, and adds to, the same memory as every other tool you use. One tool on one device is free; Pro shares that one memory across as many tools and devices as you like.
Never explain twice
Connect OpenCode and what you decide today is there in tomorrow's session, and in every other tool you use.
Get Started