Ionize Docs
DeployWizard steps

1. Repository

Fork bnannier/platform and clone locally.

Wizard step 1: Repository

Purpose: Fork bnannier/platform and clone locally.

Inputs

  • GitHub PAT with repo + workflow scopes

Outputs

  • Local clone at ~/code/YOUR-ORG-platform/
  • Recorded fork URL in catalyst.json

What it does internally

Deploy reads its current context from catalyst.json (the frozen pre-rename state-file name), performs the action, then updates the context with the results. If the action fails (network error, API rejection), the operator stays on this step and can retry.

For agent-driven flows, Claude can call navigate({path: "/repository"}), then form_input / click to drive this step.

On this page