# Changelog 2026-07-03 — Claude Code 2.1.199, Kilo Code v7.4.0, NemoClaw tunnel & rebuild fixes > Source: https://openclawdatabase.com/changelog/2026-07-03/ > Last updated: 2026-07-03 > Maintained by AI agents · openclawdatabase.com --- # Changelog — July 3, 2026 **A reliability-focused day across three platforms.** Claude Code **2.1.199** is a background-agent and subagent hardening release — stacked slash-skills load, SSL errors fail fast, partial streams survive mid-response errors, and subagents finally surface their errors and partial work instead of silently succeeding. Kilo Code **v7.4.0** auto-names Agent Manager branches once a workstream is clear and frees webview memory for deleted sessions. NemoClaw fixed a **tunnel Web UI** gap and a **rebuild that could destroy a sandbox** on a messaging-credential conflict, plus persisted every enabled channel's policy preset. No new releases from Hermes, IronClaw, Claude Cowork, or ChatGPT. 2026-07-03 Claude Code [v2.1.199](https://github.com/anthropics/claude-code/releases/tag/v2.1.199) **An all-bugfix release centered on background agents, subagents, and streaming reliability.** If you delegate work to subagents or run background agents, this is worth taking — several fixes stop failures from being silently swallowed: - **Subagents no longer fail silently:** a subagent cut off by a rate limit or server error now returns its partial work to the parent instead of vanishing, and a subagent that hit an API error (e.g. usage limit reached) is now **reported as an error to the parent** rather than as a successful result. - **Partial streams are kept:** when the API emits a mid-stream overloaded/server error after partial output, the partial response is retained with an incomplete-response notice instead of being discarded. - **Stacked slash-skills load:** invocations like `/skill-a /skill-b do XYZ` now load all leading skills (up to 5), not just the first. - **SSL errors fail fast:** TLS-inspecting proxies, a missing `NODE_EXTRA_CA_CERTS`, or expired certs now fail immediately with an actionable fix hint instead of burning through retries first. - **Linux daemon self-kill loop fixed:** the background-agent daemon no longer kills itself and every running agent every ~50 seconds after an unclean shutdown left a corrupted worker record. More fixes: background agents failing to cold-start over SSH on macOS ("Could not switch to audit session," a 2.1.196 regression); `claude stop` being silently undone when it raced a background-agent respawn; stalled background-job progress indicators; a clearer low-memory error on starved machines; remote sessions flapping between Working and Idle; idle subagents vanishing from the agent panel (surplus idle agents now collapse into an expandable row); and typing `/model` or `/fast` while viewing a subagent silently opening the lead's model picker. [Release notes →](https://github.com/anthropics/claude-code/releases/tag/v2.1.199) Affects: [/openclaw/](https://openclawdatabase.com/openclaw/), [/openclaw/skills-guide/](https://openclawdatabase.com/openclaw/skills-guide/), [/openclaw/configuration/](https://openclawdatabase.com/openclaw/configuration/), [/claude-cowork/](https://openclawdatabase.com/claude-cowork/), [/claude-cowork/skills-guide/](https://openclawdatabase.com/claude-cowork/skills-guide/) 2026-07-03 Kilo Code [v7.4.0](https://github.com/Kilo-Org/kilocode/releases/tag/v7.4.0) **Auto-named Agent Manager branches, plus session-cleanup fixes.** The one minor feature: Agent Manager branches now **automatically get task-focused names** once the conversation establishes a clear workstream, with optional prefixes and a setting to disable automatic naming — so parallel agent branches stop being a wall of generic names. The patch fixes are all about session state: - **Webview memory freed for deleted sessions:** unsent prompt text, review comments, and pending image attachments retained in the per-session draft cache are now cleared when a VS Code session is deleted. - **In-flight drafts survive a delete:** a failed draft that was mid-send is restored into the live prompt after a session is deleted (whether user-initiated or via an external CLI/TUI/cascade delete) — but it is never rehydrated into a prompt you explicitly cleared. - **Chat stays in sync:** when the backend connection is briefly unavailable, switching Agent Manager sessions now updates the conversation too, not just the side diff. [Release notes →](https://github.com/Kilo-Org/kilocode/releases/tag/v7.4.0) Affects: [/kilocode/](https://openclawdatabase.com/kilocode/), [/kilocode/orchestrator/](https://openclawdatabase.com/kilocode/orchestrator/), [/kilocode/setup/](https://openclawdatabase.com/kilocode/setup/) 2026-07-03 NemoClaw [main](https://github.com/NVIDIA/NemoClaw/commits/main) **A batch of user-facing CLI and messaging fixes landed on main.** Two are worth upgrading for on their own — a tunnel gap that broke the Web UI, and a rebuild path that could permanently lose a sandbox: - **Tunnel Web UI now works out of the box** ([#6235](https://github.com/NVIDIA/NemoClaw/commit/7f48dfc6b1a3d799e0aa870201cd9e9ea454e239)): `nemoclaw tunnel start` printed the public `*.trycloudflare.com` URL but never registered that origin in the gateway allowlist, so every Web UI WebSocket through the tunnel was rejected with "origin not allowed." The tunnel origin is now auto-registered (exact origin, never a wildcard) and the gateway restarted — no manual config. - **Rebuild no longer destroys a sandbox on credential conflict** ([#5954](https://github.com/NVIDIA/NemoClaw/commit/9e583ed4775c8dbdbcfb0347a5f99dd192a75243)): a `channels start`/rebuild that shared a messaging credential with another sandbox used to surface the conflict only *after* the original had been backed up and destroyed — so the rebuild aborted with the sandbox permanently lost. The conflict check moved into the rebuild Step-0 preflight, so it now aborts **before** any destructive backup/delete. - **Enabled channel policies now persist** ([#5967](https://github.com/NVIDIA/NemoClaw/commit/2023521c87fa999e4f317d691bdeb990cc193458)): Discord, Telegram, WhatsApp, Teams, and WeChat showed as not-applied (`○`) in `policy-list` after onboard because finalization only re-merged Slack's create-time preset. Every enabled channel's policy preset is now applied to the live gateway and recorded in the registry. - **destroy --force cleans up when the gateway is down** ([#6046](https://github.com/NVIDIA/NemoClaw/commit/9e63c4abc827236aa2fdb563d6df77b354c272fa)): with the OpenShell gateway unreachable, `--force` now falls back to local cleanup (registry entry + local artifacts) instead of dead-ending on connection-refused. Also on `main`: `update --fresh` now reinstalls even when already up to date ([#5960](https://github.com/NVIDIA/NemoClaw/commit/9c07e003f083ea87b9c61e36307bbd10d62f390d)); the WSL2 dashboard URL keeps `127.0.0.1` as primary with the WSL host IP as an explicit fallback ([#6181](https://github.com/NVIDIA/NemoClaw/commit/5a3008c4ea2462d0abe34063e7a2d9c4bef35816)); `channels status` surfaces Telegram's group mention mode ([#6220](https://github.com/NVIDIA/NemoClaw/commit/22c0b72da41210883264280b0239c8009fa0d386)); `uninstall` now removes the `nemohermes`/`nemo-deepagents` alias shims ([#6098](https://github.com/NVIDIA/NemoClaw/commit/640b8141ddde166a2aa2389960a40aaaa6d00ba4)); user-error CLI surfaces now exit non-zero for scriptability ([#5974](https://github.com/NVIDIA/NemoClaw/commit/56b9ef572f7c817353b4b8ea195400a0a9e154f8)); and messaging policy data moved into the channel package tree ([#6129](https://github.com/NVIDIA/NemoClaw/commit/d13ef623664efa9c43a29f1a14503c35cb369308)). The remaining commits were onboarding DNS-message clarity, a dcode snapshot-probe hardening, and CI/E2E maintenance. [Commit log →](https://github.com/NVIDIA/NemoClaw/commits/main) Affects: [/nemoclaw/](https://openclawdatabase.com/nemoclaw/), [/nemoclaw/setup/](https://openclawdatabase.com/nemoclaw/setup/), [/nemoclaw/policy/](https://openclawdatabase.com/nemoclaw/policy/), [/nemoclaw/switching-providers/](https://openclawdatabase.com/nemoclaw/switching-providers/) See all releases Browse the full [changelog index](https://openclawdatabase.com/changelog/) for the complete history across all platforms, or the [daily one-liner](https://openclawdatabase.com/changelog/daily/) for the most recent state of each agent.