Remote workflow

Remote workflow

light-process supports a client-server flow. You register one or more remote servers, then push/pull/run workflows against them.

Config locations

• Global: ~/.light/config.json (remotes, default, override resolution)
• Per-workflow: .light-remote file inside the workflow folder (overrides the default for that one workflow)

Bind a remote

light remote bind <url> --key <key> [--name <name>]

The first remote becomes the default. Use light remote use <name> to switch.

light remote set-key <key> [--name <name>]   # rotate API key, keep URL
light remote list                            # list configured remotes
light remote ping [--name <name>]            # health check
light remote forget <name>                   # remove a remote from local config

List, run, delete workflows on a remote

light remote ls                                            # list workflows on the default remote
light remote run <id> --input '...'                        # run with inline JSON input
light remote run <id> --input-file f.json                  # run with input from a file
light remote delete <id> [--soft] [--yes]                  # remove from the remote
light remote rm <id>                                       # alias for delete

Pull a workflow from remote into local folder

light pull <id>                          # default target ./<id>/
light pull <id> --path <dir>             # custom target
light pull <id> --path <dir> --force     # wipe target first

Server endpoint used: GET /api/workflows/:id?full=true.

Push local folder(s) to remote

light push                          # no-arg = push all workflows in current dir
light push <name>                   # push a specific workflow
light push <name> --path <dir>      # explicit path

Auto-detects POST (new) vs PUT (update). PUT prompts for confirmation unless --yes.

Server endpoint used: PUT /api/workflows/:id?persist=true (atomic update).

Manage links inline

light link <dir>                              # open in $EDITOR
light link <dir> --from <a> --to <b>          # add a link
light link <dir> --edit <id>                  # edit a single link
light link <dir> --list                       # list links
light link <dir> --remove <id>                # delete a link

REST API the client speaks to

Method	Path	Purpose
GET	/health	Health (public)
GET	/api/workflows	List summaries
GET	/api/workflows/:id	Detail (?full=true for full JSON)
POST	/api/workflows	Register (?persist=true writes file)
PUT	/api/workflows/:id	Replace (?persist=true)
DELETE	/api/workflows/:id	Remove (?persist=true deletes file)
POST	/api/workflows/:id/run	Execute with body as input

Auth: LP_API_KEY env on the server enables Bearer. Unset = all routes public. /health is always public.