EveryInc/compound-engineering-plugin · warning

Skipping unknown target: ${extra}

Error message

Skipping unknown target: ${extra}

What it means

During install, extra targets from --also that do not exist in the targets registry are skipped with this warning; install proceeds for the primary and valid extras. The message names the offending target string verbatim to make typos obvious.

Source

Thrown at src/commands/install.ts:189

        targetName,
        outputRoot,
        codexHome,
        piHome,
        pluginName: plugin.manifest.name,
        hasExplicitOutput,
        scope: resolvedScope,
      })
      const effectiveScope =
        targetName === "opencode" ? resolveOpenCodeWriteScope(hasExplicitOutput, resolvedScope) : resolvedScope
      await target.write(primaryOutputRoot, bundle, effectiveScope)
      console.log(`Installed ${plugin.manifest.name} to ${primaryOutputRoot}`)

      const extraTargets = parseExtraTargets(args.also)
      const allTargets = [targetName, ...extraTargets]
      for (const extra of extraTargets) {
        const handler = targets[extra]
        if (!handler) {
          console.warn(`Skipping unknown target: ${extra}`)
          continue
        }
        if (!handler.implemented) {
          console.warn(`Skipping ${extra}: not implemented yet.`)
          continue
        }
        const extraBundle = handler.convert(plugin, options)
        if (!extraBundle) {
          console.warn(`Skipping ${extra}: no output returned.`)
          continue
        }
        const extraRoot = resolveTargetOutputRoot({
          targetName: extra,
          outputRoot,
          codexHome,
          piHome,
          pluginName: plugin.manifest.name,
          hasExplicitOutput,

View on GitHub (pinned to c9c10f8c75)

Solutions

1. Correct the provider name against the supported list (see README/--to docs).
2. Remove the invalid entry from --also.
3. Check the detected-targets ✓/✗ output for real names.
4. Upgrade the CLI if the provider ships in a newer release.

Example fix

// before
bun install claude --also codexx   // typo -> 'Skipping unknown target: codexx'
// after
bun install claude --also codex

const KNOWN = new Set(Object.keys(targets));
const bad = parseExtraTargets(args.also).filter(t => !KNOWN.has(t));
if (bad.length) console.error(`Unknown targets: ${bad.join(", ")}`);

function isKnownTarget(name: string): name is TargetName {
  return name in targets;
}

When it happens

Trigger: Passing an unrecognized provider name via --also to the install command; the name fails the targets[extra] lookup.

Common situations: Typo in --also; provider renamed between CLI versions; copying a flag list from another tool's docs; shell variable expanding to an unexpected value.

Related errors

• Skipping unknown target: ${extra}
• Skipping ${tool.name}: not implemented.
• Skipping ${tool.name}: no output returned.
• Cleanup currently supports only the compound-engineering plu
• Unknown cleanup target: ${target}. Use one of: ${cleanupTarg

AI-assisted analysis of EveryInc/compound-engineering-plugin@c9c10f8c75 (2026-08-31). Data as JSON: /api/errors/3c2f268aa811049d. Report an issue: GitHub.