Skip to guide

Use onemind with OpenCode

OpenCode works with both the onemind macOS app and CLI. onemind writes one server-composed package to AGENTS.md in the explicitly bound Project directory. Native BETA sync also maintains a stable user-wide bootstrap in ~/.config/opencode/AGENTS.md; Project content stays in the bound folder.

macOS app

  1. Sign in to OneMind BETA.app and connect OpenCode from Team where the host supports verified Connect.
  2. Open Mind, choose the intended Project, and bind its exact folder on this Mac.
  3. Open the approved Mind, choose Sync, check the tool/device, and choose Sync now. Wait for confirmed delivery.
  4. The native app writes and verifies a remote MCP entry in ~/.config/opencode/opencode.json and reports the connection as connected. Start a fresh OpenCode task from that folder. See Mind Sync for pending, offline, and recovery states.

The native app manages its own connection and folder binding; CLI repository detection is a separate terminal workflow.

CLI

Run:

onemind project opencode .

The CLI detects OpenCode and prints a message asking you to open onemind and choose the Project Mind for the detected folder. Open the onemind app, find the detected folder in Sync Setup, and bind it to the intended Project Mind. Then run:

onemind sync
onemind status

Confirm that <repository>/AGENTS.md contains the composed onemind-managed block. On the first write, onemind saves the previous file at <repository>/.one-mind/AGENTS.md.backup. Start a new OpenCode session from that repository.

An explicit onemind integrations install opencode prepares the signed onemind skill at ~/.config/opencode/skills/onemind. This step installs the skill package but does not verify that an OpenCode plugin or MCP connection was installed; the package is shown as package prepared.