Harness Handbook

Field status · verified 2026-08-15

Know the rc.6 boundaries before they become incidents.

This is a community-maintained snapshot of high-signal reports, not an official release-health claim. Each item separates observed evidence from inference and links to the primary discussion.

Published
0.1.0-rc.6
Tracked
6 boundaries
Rule
Verify before workaround

Operator view

Start with the failure surface.

Linux · installHigh friction

Published CLI may lack the Linux x64 PTY prebuild.

node-pty falls back to node-gyp rebuild. A deprecation warning is not the failure; capture the first compiler error.

First evidence
prebuilds/linux-x64 does not exist
Next action
Install the native build toolchain or wait for a corrected package; do not treat local compilation as the release fix.
Primary report ↗
Session · tool runtimeData continuity

A scheduler crash can leave a permanently invalid provider transcript.

A recorded assistant tool call without its matching result can make every later turn fail with HTTP 400. A full restart was tested and did not repair a turn already closed with turn/end(error).

First evidence
insufficient tool messages following tool_calls message
Next action
Preserve and back up the session. Avoid hot-loading plugins during an active turn; do not edit persisted event sequences manually.
Primary report and validation ↗
Linux · sandboxSecurity report

Do not run the bwrap profile as privileged root.

A public report shows a root process retaining enough mount authority to remount a read-only bind as writable. The report is source-consistent but has not been independently reproduced by this handbook.

First evidence
Host writes persist after a sandboxed remount.
Next action
Treat root + bwrap as unsafe pending an upstream fix. Run unprivileged and prefer a capability-resistant isolation boundary such as Landlock or a disposable VM.
Security report ↗
Remote Web · browserEnvironment

Plain HTTP can remove required browser crypto APIs.

A remote Web page may render while workspace and provider data stay empty because the origin is not a secure context.

First evidence
crypto.randomUUID is not a function
Next action
Use localhost or HTTPS. Do not work around the symptom by weakening browser security.
Open the incident note →
Windows · workspacePath boundary

Folder selection failures are not one bug.

Native picker worker exits, legacy junction EPERM, and CJK UTF-16 truncation have distinct evidence and fixes. Switching blindly between pickers can hide the real boundary.

First evidence
Record the picker implementation, exact path class, and complete worker error.
Next action
Use a plain disposable path while preserving the failing path and logs for upstream diagnosis.
Junction report ↗
MCP · configurationUX gap

The client exists; the general-purpose settings form does not.

Configure one @deepseek-ai/dsh-mcp-client row per server through an overlay or profile patch. Discovered tools use mcp__server__tool names.

First evidence
Resolved config plus connection, discovery, and registration logs.
Next action
Trial with --patch, then merge into a profile patch. Resolve secrets from environment variables.
Open the MCP guide ↗

Interpretation rule

Observed is not the same as inferred.

Observed means a report includes an exact error, event sequence, or reproducible command. Source-consistent means the reported mechanism matches the inspected implementation. Verified means a workaround was actually tested against the described failure.

This page avoids “fixed” labels until a published build and the original failure path have both been retested.

Need a route, not a list?

Find the first broken boundary.

Open the failure routerStar the handbook