Skip to content

borgmcp 6.2.0

Latest
Latest

Choose a tag to compare

View all tags
@TheodorStorm TheodorStorm released this 28 Oct 16:36
· 15 commits to main since this release
v6.2.0
adb6fa9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Package

  • npm: borgmcp@6.2.0
  • Integrity: sha512-JR6IOlNzQY+iuUaGOxD76F2ozvKa4VApylNIgSXJyJFCnnaXc9izfDmgdTwvYrCCeRRAJ4hVdm0vgjSIhwZ7Dw==
  • Published with npm Trusted Publishing.

Source

News and fixes

borgmcp 6.2.0

Borg now supports OpenCode 1 and OpenCode 2.1.2 or newer. Continue using
borg --cli opencode: Borg detects the installed executable on every launch
and selects the matching integration. Borg does not install OpenCode.

OpenCode 2

  • Uses native Code Mode and its generated tool declarations. Explicit
    mcp.servers.borg.codemode=false configuration keeps direct Borg tools.
  • Starts a private OpenCode API process and attaches the normal OpenCode
    interface after verifying the process and version. The first prompt is
    submitted once; wakeup retries reuse the durable message identity.
  • Binds coordination tools and wakeups to the selected drone and worktree.
    Launching from a worktree subdirectory works. Sending a prompt in another
    conversation in that worktree carries the launch permission policy into it.
  • Preserves ordered directory restrictions and exceptions. Launch-only
    directory grants stay within the selected paths, and Borg never
    automatically approves the outer execute tool.
  • Preserves native MCP configuration precedence and environment/file
    substitutions. The native server's API password is excluded from the Borg
    MCP child's configuration.

Persistent sessions and provider connections

Borg uses OpenCode's native sessions in a separate, persistent V2 database.
This keeps V2 database migrations away from the ordinary V1 database. Sessions
created through Borg can be resumed through Borg; --continue and --session
refer to that database. Ordinary OpenCode conversation history is not imported.

Saved provider accounts may need /connect in the OpenCode interface launched
through Borg. Provider configuration and environment credentials remain
available, and connections made in the Borg-launched interface persist for
later launches.

OpenCode 1 compatibility

OpenCode 1 retains its existing API and function plugin. Plugins are installed
per launch so the two generations can share ordinary user configuration without
loading each other's plugin API. Migration preserves user-edited plugin files.

Upgrading

Run borg update. The Node.js minimum remains 22.13.0 and the
shared contract remains pinned to borgmcp-shared 2.2.0. No server or
shared-package release is required for this client change.

Assets 2
Loading