Connectors
A connector is a program you declare in kusaw.yaml that the factory talks to as a client: an MCP server (a local command or a hosted URL)…
A connector is a program you declare in kusaw.yaml that the factory talks to as a client: an MCP server (a local command or a hosted URL) or a small command program. Connectors bring outside work and context into the factory. They are off until you declare one, and you can declare up to 20.
| Kind | Block | What it does | Page |
|---|---|---|---|
| Tracker | tracker | Turns tracker items into tasks and keeps their status in step with the run | Tracker connectors |
| Log store | logs | Adds recent log lines to a run and turns critical error groups into held tasks | Log store connectors |
| Document store | docs | Gives steps read-only context from specs, design notes, and runbooks | Document store connectors |
How a connector is wired
connectors:
demo-tracker:
mcp:
command: ["kusaw", "connector", "demo-files", "--dir", "items"]
intake:
tool: list_items
mode: hold # new items wait for you; queue starts them right away
agent_tools: [get_item]mcpis the transport:commandfor a local stdio server, orurl(plusheaders) for a hosted one.commandat the top level of the entry is a command connector instead of MCP.env(command connectors only) sets environment variables for the connector's own process. Each entry is{ value: "..." }or{ secret: true }; store a secret withkusaw config set --secret connectors.<name>.env.<NAME>. Secret values are redacted from what the connector returns. An MCP server usesmcp.envinstead.intakepolls a tool whilekusaw serveruns. Withmode: hold, new items wait inkusaw connector itemsuntil youkusaw connector acceptorkusaw connector ignorethem.contextwrites named context files into each attempt from tool calls.agent_toolslists the read tools agents may call during a step, through the per-attemptfactory-connectorsproxy.write_backmaps tools that change the outside system. Their calls are effects held at the run-end gate until you apply them withkusaw effects apply <run>.
Every key is in the kusaw.yaml reference.
Safety
Items and tool results are fenced as untrusted connector:<name> data before a step sees them. Secrets go in with kusaw config set --secret and reach only that connector's process or its HTTP requests; they never reach a step, an agent session, a log, or an event. A hosted connector gets an outside-service warning from kusaw validate. See What stays local and what doesn't.
Commands
kusaw connector—list,check(list mapped tools and pin their definitions),call,items,accept,ignore,changes, andsync.kusaw docs show— print the document-store context a step would get.kusaw effects— list a run's effects, and apply or reject held ones.kusaw logs fingerprints— log-store error groups, withignoreandlink.