harness-multitool

Open questions

Questions the specification has not settled yet, and what each needs to be settled. A settled one stays in the table, struck through, with its answer.

IdQuestionNeeds
Q-1The name. Settled: harness-multitool (ADR 0008).—
Q-2The license (MIT, Apache-2.0, or both).the owner
Q-3Configuration format and location (TOML in the project and in the user's config directory?).design
Q-4Do the chosen providers accept direct requests from a browser (CORS), and with which headers?a check per provider
Q-5Which ratatui backend renders to the DOM well enough for the demo?a spike
Q-6Out-of-process plugins in any language: when, and for which interfaces?after M2
Q-7A sandbox for third-party plugins (WebAssembly components)?after M4
Q-8Is "no harness runs in the browser" true? Check before saying it publicly.research
Q-9Trigger configuration: the match syntax (label globs, payload field conditions), how a payload maps onto a journal entry or a skill's input (templates?), and per-trigger rate limits.design
Q-10How a skill run started by a callback reports back to the caller: the callback's result URL, a reply callback, or a message to the user's channel?design
Q-11How a run is identified across flow events. Settled by the owner: a pass is an instance of the reference chart, identified by the client's own unique pipeline id (a correlation_id or any id its product logic guarantees) sent with every flowstate_update; several instances render collapsed by default, the user opens any, a collapsed instance pulses for one second on an update (ADR 0012).—
Q-12How events of an existing process map onto a chart's nodes without changing the process: a mapping table in the binding, labels, payload fields?design
Q-13Run history: retention, size limits, and which windows watch a chart (a named session, every session of the project, the one that created it).design
Q-14How the debug router receives the agent's decisions. Settled by the owner: the debug router is a router in the client app, built by one OpenAPI-style contract — approve, step back only where possible, product routes; env-gated and authorized (CON-25, CON-27). The harness's own router is its daemon, the single callback entry point.—
Q-15Keeping step-debug code out of production. Settled by the owner: strictly behind the env gate MULTITOOL_DEBUG_MODE=1, with authorization (CON-25).—
Q-16What a waiting step does when no decision comes. Settled by the owner: it waits for approve, no timeouts, nothing on its own even if the agent is gone; a health check was rejected as over-engineering (CON-29).—
Q-17Where reliability metrics come from and how they reach the agent. Settled by the owner: from anywhere, by any transport, accumulated; the agent gets a message only when a Condition (IF-15, any logic, always a bool) turns true (ADR 0014).—
Q-18The interface for writing a project's response policies. Settled by the owner: the client describes the policies, the agent writes them as Markdown files in the project, and each condition links the paths of its policy files (ADR 0014).—
Q-19What an agent may do on its own and how humans are paged. Settled by the owner: described per project in its policies; not unified at the harness level (ADR 0014).—
Q-20A days-long watch versus short sessions. Settled by the owner: monitoring sessions stay open 24/7 (ADR 0014).—
Q-21Does a condition that stays true resend? Settled by the owner: a condition is idempotent — one message per event; repeats go to the harness's trigger log, and the message tells the agent to check that log for nearby triggers (INV-14).—
Q-22What identifies "the same event". Settled by the owner: the incoming event uuid, a required part of the communication contract; a record whose uuid is already recorded is the same event (INV-14).—
Q-23A burst of different events on one condition. Settled by the owner: one message per batch; firing rules live in the callback plugin, written by the user so as not to spam the agent (INV-14).—
Q-24The hot-reload mechanism for plugins that are crates. Settled by the owner: rebuild, then swap the binary in the same terminal at a safe point (exec on Unix; a child in the same console on Windows), handing the in-memory view over through a hand-off file (ADR 0015).—
Q-25Plan mode switching and what it allows. Settled by the owner: the user switches it on or asks the agent to plan and the agent enters it; leaving takes the user's approval; only harness tools, read operations and web search are available (ADR 0016).—
Q-26Plan mode: a plan file of its own? Settled by the owner: documentation in files is mandatory — the journal, maps and flowcharts are mirrored into the docs tree and kept consistent; a plan is mirrored there too (ADR 0017, CON-43).—
Q-27How the documentation mirror is kept. Settled by the owner: the agent writes the files; a PostToolUse hook on every write to the journal, a map or a chart tells it which file to update (ADR 0017).—
Q-28A docs-mirror check that cannot break anything. Settled by the owner: a built-in hook plugin on typed memory-write events, linked by doc id, one advisory reminder at Stop, the same checker as multitool docs check and in CI; structure only, not prose (CON-45, ADR 0017).—
Q-29Ask about the docs tree at the first start? Settled by the owner: at the first start in a project without docs/ and .harness/ the harness asks once whether to initialize it (project-init creates both); no mirroring until then (ADR 0017).—
Q-30Which parts of .harness/ are committed. Settled by the owner: for now all of it, step-debug runs included; no .gitignore lines; revisited if something comes up in use (ADR 0017).—
Q-31How the trigger actions relate to callback types. Settled by the owner: they are the harness types — message removed (it is notification), journal only writes to the journal, skill kept as a concept (may be dropped), flow renamed flowstate_update (ADR 0009).—
Q-32Generated documentation (ADR 0018): the PDF engine — printed from the HTML, or a typesetting engine. (Settled by the owner: only the docs files are the source, not the journal; built on demand by multitool doc; CI is the project's DevOps choice.)the owner
Q-33May the Claude Code delegate ship in the default build (ADR 0020)? Settled by the owner, 2026-11-19: yes. Anthropic's published terms do not prevent an end user signing in to the unmodified Claude Code binary with their own subscription, even inside a product, and the harness meets their conditions (delegates).—
Q-34The delegate's default mode: oneshot or session, by time to first event and reliability.a measurement
Q-35The delegate in long sessions: who compacts and whether the log stays in step, memory when idle, a dropped pipe, limits.a two-hour run

This page's source