Skip to main content
Use fused-cli describe to create a hosted Unified App from a natural-language goal. The CLI resolves services and operations, drafts TypeScript, shows the proposal, and asks you to confirm before applying it. Pass --kind sdk|mcp|rest to create one of those outputs instead. To create one App with SDK, MCP, and REST delivery, use fused-cli init without a method flag.
Service discovery checks the workspace first, then searches Registry when needed. The proposal identifies the selected services, exact versions, and operations. Missing services go through the existing activation lifecycle before the app is applied.
describe requires an interactive terminal. For unattended automation, use explicit init, extend, or plan/apply commands.

​
Update an existing app

Name the app with --update:
Or name it in the goal:
The CLI does not send an inventory of every local app to the model or choose an unnamed SDK automatically. If the name is missing or several configs match, supply --update or an exact -f path. An update target must exist locally; a missing target stops the request instead of creating an app. Updates preserve existing selections, language, bucket, authentication configuration, and service-version pins. They add the requested capabilities to the same file and app family. A changed stable SemVer version advances to the next minor release, such as 1.2.3 to 1.3.0. Use --version to choose another successor; prerelease and non-SemVer versions require it. An unchanged proposal keeps its version.
describe updates to SDK, MCP, and REST configs are additive. To remove capabilities, change routing or language, or upgrade service pins, edit and plan the config explicitly. To update a Unified App, edit its .fused/unified_app/<app>.tsx source and deploy a new version with app plan and app apply.

​
Review the Unified App draft

The proposal shows the exact selected provider operations and the buildUnifiedApp TypeScript source. Review its input schema, provider calls, and output before confirming. After apply, the CLI saves the source under .fused/unified_app/ and prints the new immutable App version ID. See author a Unified App for the file format and deployment commands. Applying publishes the App; it does not run its provider calls. A later request to the deployed App starts an execution.

​
What the models receive

The CLI shows processing disclosures before the corresponding requests: No additional user API key is required. The CLI does not send local bucket or authentication configuration, provider credentials, or execution payloads for drafting. Keep credentials out of the goal itself. The source draft is validated against selected operations; the normal Fused plan/apply permission and version checks still apply.

​
Useful flags