rohitg00/agentmemory · warning

Wiring … no adapter available (skipped).

Error message

Wiring ${name}… no adapter available (skipped).

What it means

During onboarding, each agent name the user selected is mapped to a wiring adapter via resolveAdapter(name). If no adapter exists for that agent, it is recorded as failed with reason 'no adapter available' and skipped with a warning; the rest of the wiring continues. It signals that this agent integration is unsupported or not installed in this build.

Solutions

1. Check the spelling of the agent name and re-run onboarding with a supported agent id.
2. Update agentmemory to the latest version to pick up new adapters (npm update agentmemory or equivalent).
3. Check the README for the list of supported agents/adapters.
4. Wire the agent manually by editing its MCP config to point at the agentmemory MCP server.

Example fix

// before
agentmemory onboarding --agents claude,codex-cli  // 'codex-cli' has no adapter
// after
agentmemory onboarding --agents claude,codex  // supported adapter names only

const supported = ["claude", "cursor", "codex", "windsurf"];
const invalid = agents.filter((a) => !supported.includes(a));
if (invalid.length) throw new Error(`Unsupported agents: ${invalid.join(", ")}`);

function hasAdapter(name: string): boolean {
  return resolveAdapter(name) !== null && resolveAdapter(name) !== undefined;
}

When it happens

Trigger: wireSelectedAgents iterates the user-selected agent list and resolveAdapter(name) returns null/undefined for one of the names — e.g. a typo'd agent name or an agent flavor agentmemory has no adapter for.

Common situations: User picks an agent from a newer list than the installed agentmemory version supports; passing a custom agent name to non-interactive onboarding; misspelling an agent id like 'claude-code' or 'cursor'; plugin variant lacking certain adapters.

Related errors

• Could not update ~/.agentmemory/.env. Set…
• : not detected on this machine (skipping). ` : ""}
• API key is required (via constructor…
• COHERE_API_KEY is required
• Embedding dimension mismatch in

AI-assisted analysis of rohitg00/agentmemory@e04ba88819 (2026-08-30). Data as JSON: /api/errors/f442005dd66c45a7. Report an issue: GitHub.

Appendix: source

Thrown at src/cli/onboarding.ts:328

    message: "Run `agentmemory connect <agent>` for each selected agent now? [Y/n]",
    initialValue: true,
  });

  if (p.isCancel(confirmed) || confirmed === false) {
    const cmds = agents.map((a) => `  agentmemory connect ${a}`);
    p.note(["Wire later with:", ...cmds].join("\n"), "later");
    return;
  }

  const wired: string[] = [];
  const manual: { name: string; docs?: string }[] = [];
  const failed: { name: string; reason: string }[] = [];

  for (const name of agents) {
    const adapter = resolveAdapter(name);
    if (!adapter) {
      failed.push({ name, reason: "no adapter available" });
      p.log.warn(`Wiring ${name}… no adapter available (skipped).`);
      continue;
    }
    p.log.step(`Wiring ${name}...`);
    let result: ConnectResult;
    try {
      result = await runAdapter(adapter, { dryRun: false, force: false });
    } catch (err) {
      const reason = err instanceof Error ? err.message : String(err);
      failed.push({ name, reason });
      p.log.error(`${name}: ${reason}`);
      continue;
    }
    switch (result.kind) {
      case "installed":
      case "already-wired":
        wired.push(name);
        break;
      case "stub":

View on GitHub (pinned to e04ba88819)