inconvo CLI

Install Inconvo-flavored assistant-ui components into any project.

Usage

Add the assistant-ui tool components to the current working directory:

npx inconvo@latest add assistant-ui-tool-components

Options:

• --cwd <path> – run the installer against a different project directory
• --path <relative> – override the root folder used for file output (defaults to src)
• --overwrite – replace any files that already exist without prompting
• --yes – answer "yes" to interactive prompts
• --skip-install – copy files only and skip dependency installation

By default the installer writes everything under src/, including the tool components and their supporting src/lib/inconvo/types.ts. It also installs external dependencies such as react-vega, vega, vega-embed, vega-lite, and @tanstack/react-table unless you opt out with --skip-install.

After the files are copied, the CLI attempts to update src/components/assistant-ui/thread.tsx by importing InconvoTools and rendering it inside ThreadPrimitive.Root. If the file is missing or has been customized heavily, you'll see a warning and can complete the insertion manually.

Development

npm install
npm run build

The component templates live under templates/assistant-ui/tools. Update those files whenever the upstream components change and cut a new CLI release.

Releasing

1. In the npm package settings for inconvo, connect this repository as a Trusted Publisher (OIDC) so GitHub Actions can publish without storing an npm token.
2. Follow conventional commit syntax (feat:, fix:, chore:…) when merging into main. Semantic Release reads those messages to determine the next version.
3. Every push to main (or a manual workflow_dispatch) runs .github/workflows/release.yml, which installs dependencies, builds, and executes npx semantic-release. When it finds a release-worthy change it will:
   • publish the package to npm with provenance,
   • update the GitHub release notes.
4. Verify with npx inconvo@latest --help after the workflow reports success.