Skip to content

v0.4.3

Choose a tag to compare

View all tags
@MBarc MBarc released this 17 Oct 14:05
· 136 commits to master since this release
v0.4.3
9e79f8c

MCP servers follow your task between providers

Each provider CLI keeps its own list of MCP servers, so a tool you set up in Claude Code vanished when Nectra routed a turn to Codex. Now:

  • Automatic for Claude and Codex. When Nectra launches either one, it adds the local (stdio) servers from your user configs that only the other CLIs have. No config file is changed, and env values are passed in the environment, never on the command line. Example: Codex can use a Roblox Studio server you added to Claude.
  • nectra mcp shows which CLI has each server and which ones Nectra shares.
  • nectra mcp --sync adds the servers to each installed CLI's own config, Gemini included. Gemini 0.64 reads extra settings files only when an administrator owns them, so it can't be handed servers at launch.

Not shared:

  • HTTP servers, because each CLI needs its own sign-in.
  • Servers limited to certain tools.
  • Servers tied to a working directory.
  • Gemini servers whose env values Nectra can't reproduce exactly.

A server name a CLI already has is never replaced.

Fixes

  • On Windows, Nectra can launch npm-installed Gemini CLI 0.64 again. Gemini moved its entry point, and Nectra now reads it from the package instead of a fixed path.

Known issue

  • Gemini 0.64 ignores the settings file Nectra uses to install its terminal-view hooks, so Gemini turns in terminal view may not be captured. Stream view (--provider-view stream) isn't affected.
Assets 6
Loading