gtc wizard

Overview

The gtc wizard command creates new Greentic bundles from wizard answers. It scaffolds the complete bundle structure including configuration files, provider setups, and app templates.

Usage

gtc wizard [OPTIONS]

Options

Option	Description
`--answers <FILE \| URL>`	Path or URL to wizard answers file (JSON or YAML). Supports local paths and remote `http://` / `https://` URLs.
`--dry-run`	Preview generated files without writing
`--output <DIR>`	Output directory (default: current directory)
`--template <NAME>`	Use a specific template
`-v, --verbose`	Enable verbose output

Wizard Answers File

JSON Format

{
  "project": {
    "name": "my-digital-worker",
    "version": "1.0.0",
    "description": "Customer support digital worker"
  },
  "providers": {
    "messaging": ["telegram", "slack"],
    "events": ["webhook", "timer"]
  },
  "apps": [
    {
      "name": "support-bot",
      "template": "customer-service"
    }
  ],
  "tenants": [
    {
      "id": "demo",
      "name": "Demo Tenant",
      "teams": [
        {
          "id": "default",
          "channels": ["telegram", "slack"]
        }
      ]
    }
  ]
}

YAML Format

project:
  name: my-digital-worker
  version: "1.0.0"
  description: Customer support digital worker

providers:
  messaging:
    - telegram
    - slack
  events:
    - webhook
    - timer

apps:
  - name: support-bot
    template: customer-service

tenants:
  - id: demo
    name: Demo Tenant
    teams:
      - id: default
        channels:
          - telegram
          - slack

Generated Structure

Running the wizard generates:

my-digital-worker/
├── greentic.demo.yaml          # Main configuration
├── providers/
│   ├── messaging/
│   │   ├── messaging-telegram.gtpack
│   │   └── messaging-slack.gtpack
│   └── events/
│       ├── events-webhook.gtpack
│       └── events-timer.gtpack
├── apps/
│   └── support-bot/
│       ├── app.yaml
│       └── flows/
│           └── on_message.ygtc
├── tenants/
│   └── demo/
│       ├── tenant.gmap
│       └── teams/
│           └── default/
│               └── team.gmap
└── seeds.yaml

Examples

Basic Usage

# Interactive mode
gtc wizard

# With answers file
gtc wizard --answers wizard-answers.yaml

Preview Mode

# See what would be generated
gtc wizard --answers wizard-answers.yaml --dry-run

Remote Answers File

The --answers flag accepts http:// and https:// URLs, making it straightforward to store shared answer documents in a central location and reference them from CI/CD pipelines.

# Fetch answers from a remote URL
gtc wizard --answers https://config.example.com/teams/support/wizard-answers.yaml

# Combine with dry-run to preview before generating
gtc wizard --answers https://config.example.com/teams/support/wizard-answers.yaml --dry-run

Custom Output Directory

gtc wizard --answers wizard-answers.yaml --output ./my-project

Using Templates

# List available templates
gtc wizard --list-templates

# Use specific template
gtc wizard --template customer-service --answers answers.yaml

Available Templates

Template	Description
`minimal`	Bare bones bundle with one provider
`customer-service`	FAQ bot with escalation
`helpdesk`	IT support with ticket integration
`multi-channel`	Multiple messaging channels

Workflow

Create answers file

Define your project configuration in JSON or YAML.

Run wizard

gtc wizard --answers wizard-answers.yaml

Review generated files

Check the generated bundle structure.
Configure providers
Terminal window
```
gtc setup ./my-digital-worker
```
Start runtime
Terminal window
```
gtc start ./my-digital-worker
```

Customizing Generated Flows

The wizard generates basic flow templates. Customize them after generation:

name: on_message
version: "1.0"
description: Handle incoming messages

nodes:
  # Add your custom nodes here
  - id: analyze
    type: llm
    config:
      model: "gpt-4"
      prompt: "Analyze: {{message}}"
    next: respond

  - id: respond
    type: reply
    config:
      message: "{{analysis_result}}"

triggers:
  - type: message
    target: analyze

Troubleshooting

Invalid Answers File

Error: Failed to parse answers file

Ensure your JSON/YAML is valid. Use a linter to check syntax.

Missing Required Fields

Error: Missing required field: project.name

Check that all required fields are present in your answers file.

Template Not Found

Error: Template 'unknown' not found

Use gtc wizard --list-templates to see available templates.

Next Steps

gtc setup - Configure providers
gtc start - Run the runtime
Quick Start - Complete workflow