Packaging

Ageniti can turn one app definition into distributable artifacts for CLI, MCP, manifests, and skill documentation.

What Gets Built

The bundle target writes:

ageniti.manifest.json
ageniti.actions.json
ageniti.mcp.json
cli.mjs
mcp-stdio.mjs
GUIDE.md
package.json
README.md
ageniti.bundle.json

These files describe the app, expose runnable launchers, and package the app for installation or review.

Required App Module

Launcher targets need a Node-safe module that exports your Ageniti app.

src/ageniti/app.js

Avoid importing React components, browser-only APIs, route files, or mobile runtime code from this entry.

Build

task-app build bundle --app-module ./src/ageniti/app.js --app-export app --out-dir ./dist/ageniti

If your project has an ageniti.config.json, build commands can read defaults from it.

Package

task-app package --app-module ./src/ageniti/app.js --app-export app --out-dir ./dist/ageniti

This builds the bundle and runs npm pack inside the generated output directory.

Publish

task-app publish --app-module ./src/ageniti/app.js --app-export app --out-dir ./dist/ageniti

publish defaults to a dry run. Use --live only when you intentionally want a real npm publish.

task-app publish --live --access public --tag latest --app-module ./src/ageniti/app.js --app-export app --out-dir ./dist/ageniti

MCP Descriptor

ageniti.mcp.json includes command metadata and snippets for common MCP host configuration. The generated stdio command points at:

node ./mcp-stdio.mjs

Skill Documentation

GUIDE.md is generated from app and action metadata. It gives agents, coding assistants, and automation systems a compact usage guide for the capabilities exposed by the app.

Release Review

Before publishing a new bundle:

• inspect ageniti.manifest.json
• inspect ageniti.actions.json
• inspect ageniti.mcp.json
• run the generated cli.mjs
• run the generated mcp-stdio.mjs with an MCP host
• compare old and new manifests with task-app diff