Skip to main content

Bring an existing CLI

Intermesh evaluates a frozen CLI artifact. The agent selects exactly one source.

Local repository

Use this when the CLI lives in the current repository:
Use npm instead of pnpm when that is the package manager. The build script must exist in the selected package’s package.json. If the repository contains only one supported CLI package, the agent can omit the package options and let Intermesh discover it:

Remote Git repository

Pin the revision and select the package explicitly when discovery is ambiguous:
Never put credentials in the Git URL.

Published npm package

Existing tarball

Resolve ambiguity

When setup cannot choose one package or build action, it returns an error with structured choices and a next action. The agent must use those returned values; it must not guess.