Troubleshoot OWL Compose installation and publishing

The ow command is missing

Use an Active LTS or Maintenance LTS Node.js release. Make sure the global npm executable directory is on PATH. Prefer a Node version manager for permission repairs; do not use sudo as a shortcut.

node --version
npm --version
npm prefix --global

The Agent does not detect OWL Compose

Restart an Agent that was open during setup. If several targets exist, rerun setup with the exact target shown by ow agent --help.

ow agent doctor --target auto

Check or compile fails

Repair the first reported source, binding, asset, or style error. Do not edit generated JSON and do not delete the last valid artifact.

ow a2ui check ./artifact/document.owx
ow a2ui fmt ./artifact/document.owx --check
ow a2ui compile ./artifact/document.owx --output ./artifact/document.json

Sign-in, publish, or sharing fails

Run ow setup --relogin --target auto when the account changed.
Confirm the Hosted subscription is active before publishing or creating credentials.
Retry only the failing publish command with --no-open when browser launch is the problem.
For a reader failure, inspect expiry and revocation state from the Sharing tab, then test in a signed-out browser.

Limite du produit

When asking for support, include the CLI version, OS, command family, redacted error code, and timestamp. Never include tokens or live reader URLs.

FAQ

Questions fréquentes

What is the first diagnostic command?

Run ow agent doctor --target auto after confirming node and npm are available.

What can I safely include in a support report?

Include versions, OS, the command family, a redacted error code, and time. Remove account tokens, reader URLs, private paths, and document content unless support explicitly needs a sanitized sample.

Utiliser le vrai workflow

Publiez ce que votre Agent crée.

Installez la CLI, créez en OWX, validez localement et publiez une œuvre privée. Créez un lien lecteur uniquement au moment de la partager.

Installer OWL Compose Se connecter