Skip to guide

Use onemind with Qoder

Qoder supports native BETA Project-folder sync and explicit CLI Project targets. Qoder has no skills capability via onemind. Native BETA sync also maintains a stable user-wide bootstrap in ~/.qoder/AGENTS.md; Project content stays in the bound folder.

macOS app

In the app, connect Qoder from Team and bind the Project folder before Mind Sync.

  1. Sign in to OneMind BETA.app and connect Qoder from Team.
  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. Start a new Qoder session from that folder. See Mind Sync for pending, offline, and recovery states.

CLI

From the repository you open in Qoder, run:

onemind project qoder .

The CLI detects Qoder 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 a onemind-managed block, then reopen Qoder chat or start a new Qoder session. Qoder IDE and Qoder CLI recognize the repository-root AGENTS.md automatically. onemind preserves instructions outside its managed block and keeps a first-write backup at <repository>/.one-mind/AGENTS.md.backup.

Running onemind qoder [PATH] calls the same detection step as onemind project qoder, adding an inactive target. New native folder bindings are scoped to the exact Project, tool, and device; do not use the legacy shorthand to move an existing native binding.

onemind uses the Qoder native plugin commands for install, list, and uninstall. The retained Qoder 1.1.5 artifact exercised this native local-package contract; authenticated vendor-artifact CI is not claimed:

qodercli plugins install "$ROOT/onemind" --scope user
qodercli plugins list --json
qodercli plugins uninstall onemind --scope user --keep-data

The native inventory identifies the local package as onemind@local. Qoder's plugins update applies to marketplace plugins, so reinstall a newly extracted local package to update it. Only when an older Qoder CLI does not expose the native plugins commands should onemind use the compatibility fallback: copy skills/onemind to ~/.qoder/skills/onemind, then run qodercli mcp add -s user -t http onemind https://onemind.team/mcp.