Skip to guide

Use onemind with CodeBuddy (legacy WorkBuddy compatibility)

The macOS AI Tool Integrations manager can install, update, or uninstall the shared plugin package. This does not activate a Project binding or enable uploads. Project instructions use the canonical workbuddy target; uploads require UploadEnabled on the exact user-activated Project binding.

onemind connects to CodeBuddy using the current executable names codebuddy, codebuddy-code, and cbc. The public target alias codebuddy maps to the compatibility key workbuddy. Native BETA can bind a Project folder for its registered instruction adapter; follow Mind Sync when the host is connected. CLI discovery and explicit activation remain available below. Detection alone never authorizes a write or upload. CodeBuddy has no managed skills via onemind. Native BETA sync also maintains a stable user-wide bootstrap in ~/.codebuddy/CODEBUDDY.md; Project content stays in the bound folder.

Use onemind integrations (install, update, repair, uninstall) to manage the shared plugin package from the CLI. These plugin actions are separate from binding an exact Project folder, syncing instructions, and enabling uploads.

Initialize and sign in to CodeBuddy interactively first. Passive status never launches a fresh unowned profile. If the fixed ~/.codebuddy profile is absent, explicit install returns requires_host_initialization without launching CodeBuddy or writing a receipt. If a receipt remains after that profile is deleted, update and uninstall return the same initialization error before launch and retain the receipt. Existing profiles retain the bounded 15-second inventory preflight; after verified install, passive status validates receipt-bound local snapshots instead of relaunching CodeBuddy.

macOS app

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

CLI

  1. Open the workspace in CodeBuddy.
  2. Run onemind project codebuddy . to detect the workspace. The CLI prints a message asking you to open onemind and choose the Project Mind for the detected folder.
  3. Open the onemind app, find the detected folder in Sync Setup, and bind it to the intended Project Mind.
  4. Run onemind sync.
  5. Run onemind status.
  6. Confirm that the selected <workspace>/CODEBUDDY.md or <workspace>/AGENTS.md contains a onemind-managed block.
  7. Start a new CodeBuddy session.

On the first write, onemind saves the previous file at <workspace>/.one-mind/CODEBUDDY.md.backup (or .one-mind/AGENTS.md.backup if falling back to AGENTS.md).

onemind checks current CodeBuddy and legacy WorkBuddy application/configuration locations, including candidate defaults under ~/CodeBuddy and ~/WorkBuddy. Discovery opens the CodeBuddy/WorkBuddy registry database read-only and queries only workspace/session-path metadata, never chat or message content. On non-macOS systems, sqlite3 must be available on PATH for registry discovery. A discovered candidate is informational only: synchronization and upload are limited to the exact user-activated Project binding.

For an activated workspace, an existing regular, non-symlink CODEBUDDY.md is the canonical instruction destination. When it is absent, onemind retains AGENTS.md compatibility. If both files exist, onemind writes the current WorkBuddy managed block only to CODEBUDDY.md. When AGENTS.md still contains an older managed block for that exact WorkBuddy binding, onemind removes only that block and preserves every other byte, the file mode, and all user-authored content. A symlink or non-regular file at the selected priority path stops synchronization instead of falling through to a different destination.

For an activated workspace, onemind syncs reviewed memory and, when upload is enabled for the target in Sync Setup, uploads structured onemind proposal events through the generic Project reconciler. Registry discovery reads only workspace/session-path metadata; onemind never reads WorkBuddy/CodeBuddy chat or message content or derives durable knowledge from arbitrary host file changes.