@nuxtagentic/kit

Module registration

@nuxtagentic/kit is the build-time helper shared by the local Nuxt modules. It exports registerWorkspaceModule and getWorkspaceModules; it is not itself a Nuxt module to add to the host's modules array.

externalizeSsrDependencies(names, nuxt) lets Nitro bundle shared server libraries once when both SSR and server routes import the same dependency. It resolves from the importing module, including unhoisted pnpm dependencies. Browser builds and development retain their existing bundling behavior.

A module passes its ID, runtime directory, optional catalog entry, feature, metadata, and server contribution paths to registerWorkspaceModule. Kit registers its composable and server directories and creates four generated manifests:

Use catalog for business features that users can install. It provides a label, description, icon, icon classes, optional opening URL, dependencies, and an optional defaultInstalled flag. Shared services and core features omit the catalog entry and remain active. A package can own multiple contributions. Client and server manifests expose getWorkspaceMetadata(installedIds) to select active contributions. The no-argument metadata exports contain all available entries.

Each consuming module still owns its page, layout, component, configuration, and worker registration in module.ts. Registration is scoped to the Nuxt instance and rejects duplicate IDs.

Registration opts the package's TypeScript sources into both Vite and Nitro transpilation. Nitro normally excludes node_modules; Kit narrows that default to allow @nuxtagentic sources while preserving other exclusion rules. Registered package roots are bundled into the server output, including Cloudflare Workers.

Kit does not mutate cloud.config.ts or run migrations. The host statically composes schema exports so CloudConfig's CLI can read them outside Nuxt. Feature packages declare schema exports in their cloudconfig.models metadata. See the package map and setup guide.

The portable fixture installs one module at a time without the host app:

NUXT_TEST_MODULE=agents pnpm exec nuxt typecheck packages/kit/tests/fixture

Replace agents with another module name. pnpm test:modules checks import boundaries, dependency cycles, exported sources, and fixture isolation.

Coding-agent plugin and MCP host

Every registered module participates in a shared project plugin during Nuxt prepare/dev. Kit ships nuxt-agentic-mcp and nuxt-agentic-plugin; no starter-specific setup script is required. Production builds do not write coding-agent settings.

The generated plugin follows Agent Plugins 1.0: root plugin.json, mcp.json, and skills. Codex discovers it through a project marketplace and .codex/config.toml. A .claude-plugin/plugin.json / .mcp.json adapter and local marketplace support Claude Code. Run pnpm exec nuxt-agentic-plugin --client claude once to finish installing there. Explicit project disablement and unrelated configuration are preserved. Client trust and plugin reload still belong to the client.

A feature adds mcp: { from: '@your/package/mcp' } to registerWorkspaceModule and exports mcpContribution: ProjectMcpContribution from that public entry. Its optional skills path contributes feature-owned skills. Its register(host) callback registers typed tools or granted catalog sources. managedModels explicitly replaces raw model tools with specialized authoring tools. Other models automatically retain CloudConfig-generated CRUD and access rules. Kit never imports business modules directly.

The local launcher loads config through @cloudconfig/core/project, targets the app explicitly even from a plugin cache, and composes installed contributions through CloudConfig's MCP registry. Only project_info is public before local database/sign-in setup. Private calls revalidate the selected account and organization membership; they never silently switch users. No tokens are stored in plugin assets.

Generated marketplaces, host settings and the module manifest are local state and excluded from customer exports. Nuxt prepares them again after an independent customer installation.