Plugins, skills & MCP

uuldana-cli does not run plugins

uuldana-cli does not run plugins, skills, MCP servers, hooks, or custom commands. Each provider does, from its own configuration. uuldana-cli leaves all of that alone.

What continues

• Every native extension keeps working in its own provider. uuldana-cli starts the provider’s real executable with its normal arguments and environment. Plugins, skills, MCP servers, instruction files such as CLAUDE.md or AGENTS.md, hooks, and slash commands load as they do when you start the provider yourself. Adapters do not pass flags that disable extension discovery unless you asked for that.
• Accounts keep their own setup. A second account selected with an env entry such as CLAUDE_CONFIG_DIR has its own plugins and settings directory.
• Project files continue. When work moves to another provider, the next agent starts in the same directory, with the same files, the same git state, and the project instruction files that it supports.

What does not move

Only the visible conversation is carried, as the first prompt of the next provider. Reasoning the provider did not display, its memory, approvals, running tool calls, and other internal state are not carried, and the prompt says so.

What uuldana-cli does not promise

Providers do not share a plugin format. A Claude Code plugin does nothing in Codex, a Codex skill does nothing in Gemini CLI, and an MCP server configured for one provider is not configured for another unless you configured it there too. uuldana-cli does not translate, copy, or synchronize extensions between providers.

Two practical consequences:

1. If you rely on an extension, put the providers that support it first in providers, or install the equivalent in each provider you list.
2. Project instruction files are the portable part. Providers that read the same file name, for example AGENTS.md, see the same instructions after a handoff. Providers that read a different file do not, and the handoff prompt is the only context they get.

Transport mode can change behavior

The terminal interface of a provider is the one that loads your full setup. Whether a provider’s ACP mode loads the same configuration, MCP servers, skills, and instruction files is not established, so every agent runs in its native terminal.

Checking what a provider offers

uuldana providers shows which agents were found and what was learned about them. Each adapter declares its capabilities (native terminal, initial prompt, resume by id, continue the latest, permission controls) as supported, unsupported, or unknown, with the evidence behind it. Unknown never counts as supported.