Sign in
← AI PulseAug 13, 2026

Wire · news · Single-source brief

Claude Code Updates Include Subagent Forking and GitLab Integration

Recent updates to Claude Code include enabling subagent forking by default, new cross-session messaging capabilities, and expanded GitLab support.

By Illumora Editorial

Source · Aug 13, 2026, 11:29 PM · On Illumora · Aug 13, 2026, 11:32 PM

Media from the primary source — shown here so you can stay on Illumora.

Rewritten from one allowlisted primary — not independent enterprise reporting. Lanes →

Brief drafted by Illumora’s editorial model from the linked primary source. Ops desk reviews flagged pieces. How we write →

Read the source →Claude Code What's New + releases — Claude Code changelog - Claude Code Docs
Save

Claude Code has received several updates, including changes to subagent behavior, inter-session communication, and integration with GitLab.

Key Points

  • Subagent forking is now enabled by default, allowing a subagent_type: "fork" subagent to inherit the full conversation and prompt cache.
  • Non-teammate agent spawns in interactive sessions now run in the background by default.
  • Users can type @ in the prompt to mention another Claude session by name, which then uses SendMessage to reach that session directly.
  • SendMessage now delivers to a bare name that exactly matches one live session without requiring confirmation.
  • Interactive sessions on a single machine now maintain unique names; if a name is already in use, a variant is assigned.
  • New /config rows have been added for "Dialog expiry" and "Messages from your other sessions," managing cross-session inbound message handling.
  • Secret redaction has been implemented for various GitLab token families (e.g., glrt-, gloas-, glptt-), with full redaction for glpat- and gldt- tokens.
  • GitLab support has been added to plugin marketplaces, allowing bare gitlab.com repository URLs to clone similarly to github.com URLs.

Context

According to the Claude Code changelog, these updates enhance the functionality and security of the platform, particularly in how agents interact and how sensitive information is handled.

Why It Matters

These changes offer builders more control over agent behavior and inter-session communication, while also improving security for GitLab users, potentially streamlining development workflows.

What To Do

  • Note the default behavior change for subagent forking and background agent spawns.
  • Test the new @ mention and SendMessage functionality for direct session communication.
  • Review the new /config options for managing cross-session messages.
  • Observe the enhanced secret redaction for GitLab tokens and the expanded GitLab repository cloning support.