Fetching from the wire…
01
02
03
04
05
06
07
08
Public story · 2026-07-27 · high
A skill written to wait for a forked task to finish will keep going without it, and nothing will tell you that happened.
Why now: Documented in the July 27 changelog for release v2.1.218.
Claude Code's v2.1.218 release flipped a scheduling default. Skills that declare context: fork used to block the main session until the forked task returned. Now they run in the background instead, per the changelog. A new per-skill background: false setting in frontmatter brings back the old blocking behavior if you set it.
Any skill written to assume a fork finishes before the next step runs doesn't hold anymore. The failure mode is quiet: no error, no warning. The main session just continues. A skill's logic that depends on a forked result being ready can produce wrong output, with nothing pointing back to the cause.
The same release made two other changes. Frontmatter booleans now accept yes, no, on, off, 1, and 0, case-insensitively, not just true/false. Claude Code also now rejects agent names containing a colon, since : is reserved for plugin namespacing.
Nothing in the changelog flags which existing skills fork without declaring a background preference. That's the gap to watch. Will a future release add a lint for it, or will teams discover the change by tracing bad output back to a silent default?
Each link below shares sources, entities, or timing with this story.
Shared entity: Same / Same source / Shared topic / Earlier coverage
Both cover Same; cite the same source (v2.1.218); overlapping topics (agent, background).
Shared entity: Same / Same source / Earlier coverage / Tension
Both cover Same; cite the same source (v2.1.218); earlier Same coverage from 2026-06-02.
Same source / Shared topic / Tension
Cite the same source (v2.1.218); overlapping topics (agent, background, context); pushes against this story (against).
Shared entity: Same / Same source / Earlier coverage
Both cover Same; cite the same source (v2.1.218); earlier Same coverage from 2026-07-22.
Both cover Same; cite the same source (v2.1.218); earlier Same coverage from 2026-07-22.
Both cover Same; cite the same source (v2.1.218); earlier Same coverage from 2026-07-10.
Shared entity: Same / Shared topic / Earlier coverage / Tension
Both cover Same; overlapping topics (agent, context); earlier Same coverage from 2026-05-14.
Both cover Same; overlapping topics (agent, context); earlier Same coverage from 2026-03-29.