Repository navigation
Description
Affected area: Core runtime; Harness adapter; Schemas or configuration; Consumer integration; Documentation or examples
Tracks the GTC DC P0 work for NemoClaw. It replaces #547, whose shared P0 specification still applies to OpenClaw and Hermes; #578 and #579 extend it. Deferred work is in #566. To change the scope, edit this description and add a change-log line.
Problem or opportunity
NemoClaw v1 ships OpenClaw and Hermes for GTC DC (2026-11-30), and users migrate from NemoClaw classic only if they keep what they have there. Each harness must run as the stock harness does inside OpenShell; the Fabric adapters don't offer all of that yet.
Priorities
Agreed in the NemoClaw and Fabric reviews on 2026-10-30 and 2026-11-02, with Deep Agents Code deferred on 2026-11-06:
- Two P0 harnesses: OpenClaw and Hermes. The others wait until after GTC DC ([Enhancement]: Epic: deferred until after GTC DC: interface contract items and other harnesses #566).
- The bar is the stock harness. A feature that fails for a reason other than the sandbox's policy is a bug. Fabric offers each harness's own interfaces directly rather than normalized ones.
- Dates: Fabric 0.7 on 2026-11-19; GTC DC on 2026-11-30. NemoClaw tests Fabric
mainas work lands. - Platforms: Linux,
linux/amd64andlinux/arm64. Fabric tells NemoClaw when it moves a harness pin or a path an adapter relies on.
| Sub-issue | Priority | Harness | Scope | Work |
|---|---|---|---|---|
| #578 | P0 | OpenClaw, Hermes | Cold resume across restarts | Core's runtime.keep_state (#572) and Hermes's home in it (#576); OpenClaw adopts it; each continues the previous conversation |
| #541 | P0 | OpenClaw | Browser dashboard and chat | A setting on the managed runtime's Gateway, plus its per-start token file |
| #540 | P0 | Hermes | API server; browser dashboard and chat | Runtime-bound Hermes API server and dashboard children |
| #579 | P0 | OpenClaw, Hermes | Terminal UI | Offer each harness's own terminal UI on the runtime's configuration and state |
| #580 | P0 | OpenClaw, Hermes | Skills on mounted volumes | Per-skill mounts, read-only or read-write, and agent-written skills that persist |
| #618 | P0 | Hermes | Native configuration controls for conversation-aware middleware | Expose background model-call and tool-search controls; qualify memory controls against supported Hermes |
| #487, #298 | To decide | All | Restart safety | Retry a lost start without a second runtime (#487); report an exited harness as failed so a refresh starts it again (#298) |
Deep Agents Code (dcode) scope is deferred until after GTC DC in #566: #546, cold resume and retained state, mounted skills, and harness qualification. This is deprioritized work, not completed work. LangChain Deep Agents is a separate harness and is unaffected.
Shared Fabric defects #583 (busy-stop cleanup and replacement) and #584 (invocation response loss) remain in this epic. Their historical dcode evidence remains valid; deferring that harness does not defer the shared fixes.
OpenClaw shutdown defect #626 is also tracked here: Fabric force-kills the Gateway before ownership release. With retained state, ordinary Docker sandbox replacement then fails for up to five minutes. The shutdown fix is independent of the retained-state PR; validation with retained state is required for #578.
Status
NemoClaw's reference implementation (cv/NeMo-Fabric) is proposed as stacked pull requests: #568 to #570 (fixes), #573 (OpenClaw), #574 (Hermes), #572 and #576 (kept state). These can be reviewed or just referenced in the implementation.
To test a change against NemoClaw, update NemoClaw v1's Fabric pin and run its tests on a GPU host, such as a DGX Spark.
Acceptance criteria
- Every sub-issue above marked P0 is closed.
- NemoClaw's tests show OpenClaw's and Hermes's interfaces working and their state and conversations surviving a sandbox replacement.
- NemoClaw
v1pins a Fabric commit onmainthat contains this work.
Change log
-
2026-11-12: added [Bug]: Fabric force-kills OpenClaw before shutdown finishes, blocking replacement with retained state #626 for OpenClaw shutdown completing too late for Fabric's stop allowance, and the resulting Docker replacement failures with retained state.
-
2026-11-09: added [Enhancement]: Hermes and OpenClaw native configuration controls for conversation-aware middleware #618 as GTC DC P0 for Hermes native configuration controls needed by the decision-model guard workflow. OpenShell middleware bindings are tracked separately in [GTC DC] Support OpenShell network middleware bindings in v1 sandbox policies NemoClaw#14338.
-
2026-11-06: agreed to defer Deep Agents Code until after GTC DC; moved its adapter and qualification scope to [Enhancement]: Epic: deferred until after GTC DC: interface contract items and other harnesses #566, narrowed [Enhancement]: P0 adapters: cold resume and usable agent-installed plugins across restarts #578/[Enhancement]: P0 adapters: skills on mounted volumes #580 to OpenClaw and Hermes, and retained shared Fabric lifecycle and transport work.
-
2026-11-02: opened from [Enhancement]: Epic: serve harnesses' native interfaces through one adapter contract #547, narrowed to three harnesses; cold resume, terminal UIs and skills on mounted volumes added.
-
2026-11-02: trimmed to scope and status; cold resume's requirements moved to [Enhancement]: P0 adapters: cold resume and usable agent-installed plugins across restarts #578, and the specification stays on [Enhancement]: Epic: serve harnesses' native interfaces through one adapter contract #547.
-
2026-11-02: cold resume ([Enhancement]: P0 adapters: cold resume and usable agent-installed plugins across restarts #578) is P0, like the rest of this epic.
Duplicate check
- I searched the existing issues and did not find a duplicate.
Activity
cv commentedon Nov 2, 2026
How the pull requests from the
cv/NeMo-Fabricfork map to this epic. NemoClaw'sv1builds on fork commita3b57155; NVIDIA/NemoClaw#14054 moves it toddf59e87, which merges all nine branches below.runtime.keep_statein core; #576 Hermes keeps its home in the agent's state folderDecisions open in review threads, for the Fabric team:
stopsignals the child directly, so OpenClaw's Gateway and an ACP agent's tool and MCP processes can outlive it (fix: stop agents where group signals are denied #568). Options: walk the process tree, or report incomplete cleanup.keep_state, a service holds the state folder until it's released, and one runtime at a time can connect to it (feat: keep an agent's state in one folder across its runtimes #572).dcode_commandandstartup_timeout_secondsfrom [Enhancement]: Deep Agents Code adapter: new adapter with terminal UI #546.Notes for #580, from the adapters on these branches:
SKILL.md, so one mount per skill works and a mounted directory of skills is rejected.skills.external_dirs, so a directory of skills works; skills the agent writes go to its home, which feat: keep Hermes's home in the agent's state folder #576 keeps.skillsyet.[-][Enhancement]: Epic: GTC DC P0 for NemoClaw: OpenClaw, Hermes and Deep Agents Code as stock harnesses[/-][+][Enhancement]: Epic: GTC DC P0 for NemoClaw: OpenClaw and Hermes as stock harnesses[/+]jyaunches commentedon Nov 6, 2026
Following the agreement to defer Deep Agents Code (
dcode) until after GTC DC (2026-11-30), the scope has been updated:gtc-dc-blockerlabel. The issue remains open.LangChain Deep Agents is a separate harness and is unaffected. Deferral establishes no new delivery date; #566 calls for reprioritization after GTC DC.