Back to Signal Feed
CodeTracked since May 19, 2026

Fix relative @ include resolution in claude/cli parsers

A bug fix makes both the claude and cli parsers resolve relative `@` include paths against the directory of the source file, so includes work when the prompt file is outside the current working directory.

claude parsercli parserrelative @ includesource file directory

What Happened

  • A bug fix makes both the claude and cli parsers resolve relative `@` include paths against the directory of the source file, so includes work when the prompt file is outside the current working directory.
  • A bug fix makes both the claude and cli parsers resolve relative `@` include paths against the directory of the source file, so includes work when the prompt file is outside the current working directory.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented source-file-relative resolution for relative @-includes in both parsers and added corresponding tests, directly fixing include lookup failures caused by relying on the process cwd and keeping explicit exceptions (absolute paths or unknown source_dir) untouched.

Why Track This

Why It Matters

Developers using CodeCompanion prompt files outside their current working directory can now load referenced local files with `@` includes without missing-context failures, which reduces broken prompt behavior during multi-location workflows; watch whether any custom include workflows implicitly depend on cwd-based resolution and track cases where source_dir is not discoverable, as those will continue using the previous fallback behavior.

Impact

Developers using CodeCompanion prompt files outside their current working directory can now load referenced local files with `@` includes without missing-context failures, which reduces broken prompt behavior during multi-location workflows; watch whether any custom include workflows implicitly depend on cwd-based resolution and track cases where source_dir is not discoverable, as those will continue using the previous fallback behavior.

What To Watch Next

  • Watch whether claude parser becomes a repeated pattern.
  • Track follow-up changes around AI IDE.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: unknown_source_dir_fallback_paths, relative_include_behavior_change_regression.
Open Topic TimelineOpen Technical EventOpen Original Sourceunknown_source_dir_fallback_paths / relative_include_behavior_change_regression / custom_cwd_based_workflows

Supporting Evidence