VectorStep integration

This page is the authoritative reference for how the Gateway plugs into VectorStep: the executor config on VectorStep’s side, using it from a pipeline step, and how it compares to the OpenClaw executor.

1. Configure VectorStep

In ~/.vectorstep/config/vectorstep.yaml:

executors:
  gateway:
    url: ws://gateway:18780/rpc          # gateway WebSocket endpoint — the compose service name
    token: ${VECTORSTEP_GATEWAY_TOKEN}        # invoke token, wired in automatically by the installer —
                                               # NOT the admin token; see Gateway authentication
    rest_url: http://gateway:18780      # used by the VectorStep Agents UI

2. Use in pipeline YAML

steps:
  - name: triage
    executor: gateway
    executor_config:
      agent: sre-triage                      # must match an agent in your agents/ directory
      model: anthropic/claude-sonnet-4-6     # optional model override
      thinking_level: low                    # optional — Anthropic and OpenAI models
    confidence_threshold: 0.70
    on_low_confidence: escalate
    timeout_seconds: 300
    prompt_template: |
      Alert: {{summary}}
      Service: {{labels.service}}

      Investigate and return JSON...

Steps within the same VectorStep pipeline can freely mix executor: openclaw and executor: gateway.

Differences from the OpenClaw executor

	OpenClaw executor	Gateway executor
Auth	Ed25519 device signature	Bearer token
Session isolation	Server-side (no file clearing)	Server-side
Model routing	OpenClaw agent config	Gateway providers: config
MCP tools	OpenClaw MCP servers	Gateway mcp_servers: config
Thinking parameter	thinking	thinkingLevel
OTel trace propagation	Not supported	Supported — joins VectorStep’s trace

Gateway MCP (agent authoring)

VectorStep-Gateway-MCP is a separate, standalone MCP server (own repo, own process) that exposes this gateway’s agent-management and introspection surface to an MCP client (Claude Code/Desktop), so an agent’s agent.yaml/soul.md can be authored conversationally instead of by hand-editing files on the host running the gateway. It talks to this gateway only over the REST endpoints — no shared code — and holds the admin token (agent writes need the admin scope; the invoke token VectorStep holds can’t do this), never returning it or any other config.yaml secret from any tool.

For the full tool inventory, install steps, and client configuration, see MCP servers.