Setup Manifest

Configure OpenClaw to route through Manifest -- either the cloud service or a local dev server.

Cloud users don't need the plugin. This skill adds Manifest as a direct model provider in the OpenClaw config.

Workflow

1. Determine parameters

• Port (required for dev/local, optional for cloud): The port where the Manifest backend is running. In cloud mode without a port, defaults to https://app.manifest.build.
• Mode (optional, default dev): dev, local, or cloud
  • dev -- Local development, connects to a backend you started manually
  • local -- Configures the plugin for embedded server with SQLite (plugin must be installed separately via openclaw plugins install manifest)
  • cloud -- Connects to app.manifest.build (or localhost if port is provided)
• Key (optional): A mnfst_* API key. Required for cloud mode.

If the user doesn't specify a mode, default to dev. If dev/local and no port, ask them.

2. Run the setup script

# Dev (port required):
bash "${CLAUDE_SKILL_DIR}/scripts/setup_manifest.sh" <PORT> --mode dev [--key <KEY>]

# Cloud (port optional):
bash "${CLAUDE_SKILL_DIR}/scripts/setup_manifest.sh" --mode cloud --key <KEY>

The script sets the provider config (models.providers.manifest), default model (manifest/auto), and restarts the gateway. Use --dry-run to preview.

3. Show status table

bash .claude/skills/manifest-status/scripts/manifest_status.sh

Output the table exactly as printed. No extra commentary.