Skip to main content

Connector Integration

MonoSurf is a CLI binary. connector.json defines how CLI binaries are invoked. They connect naturally.

The Pattern

Intent Field

connector.json v2.1 adds intent to StepDefinition:
  • intent: "read" — safe, AI can execute freely within grant
  • intent: "write" — mutates state, cjson runner prompts for confirmation
This field was added to the connector.json schema specifically for the MonoSurf use case, but applies to any tool that has read and write operations.

Pipeline Example

A connector.json can define a full discover → dive → engage pipeline:
Machine executes steps 1-2 automatically. Step 3 pauses for human approval. This is the same separation pattern as NIIA’s read-only observe surface and OTP-gated control surface over Kernel CLI.

Same Pattern, Every Tool

connector.json doesn’t know or care that MonoSurf uses Chrome CDP internally. It sees a CLI binary with arguments and output. The same connector.json format works for: One format. Any tool. The transport is the tool’s problem, not the orchestrator’s.

Running via cjson

The cjson runner:
  1. Loads connector.json
  2. Resolves {variables} from CLI arguments
  3. Executes binary with args
  4. Matches output against rules
  5. Suggests next actions
  6. Gates write operations with approval prompts