feat(nx-mcp): make nx_project_details more token efficient by default

[MaxKless]

No description provided.

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 206a65f

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e-ci,ty...	✅ Succeeded	5m 19s	View ↗
nx-cloud record -- yarn nx sync:check	✅ Succeeded	4s	View ↗
nx-cloud record -- yarn nx run-many -t ktfmtFormat	✅ Succeeded	4m 17s	View ↗
nx run-many -t ktfmtFormat	✅ Succeeded	4m 12s	View ↗
nx-cloud record -- yarn nx format:check --verbose	✅ Succeeded	6s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-12-03 14:08:41 UTC

[graphite-app]

The logic incorrectly identifies root targets when target names overlap. If a targetGroup contains ['test', 'test-ci', 'test-ci--Test1'], the code will:

1. Mark test as a root target with ['test-ci', 'test-ci--Test1'] as atomized targets
2. Also mark test-ci as a root target with ['test-ci--Test1'] as atomized target
3. Add test-ci--Test1 to targetsToExclude twice

This causes incorrect filtering and display. Fix by enforcing the double-dash pattern:

for (const target of targets) {
  const atomizedTargets = targets.filter(
    (t) => t !== target && t.startsWith(`${target}--`)
  );
  
  if (atomizedTargets.length > 0) {
    rootTargets.add(target);
    atomizedTargetsMap.set(target, atomizedTargets);
    targetsToExclude.push(...atomizedTargets);
  }
}

Suggested change

	for (const target of targets) {
	if (targets.some((t) => t !== target && t.startsWith(target))) {
	rootTargets.add(target);
	const atomizedTargets = targets.filter(
	(t) => t.startsWith(target) && t !== target,
	);
	atomizedTargetsMap.set(target, atomizedTargets);
	targetsToExclude.push(...atomizedTargets);
	}
	for (const target of targets) {
	const atomizedTargets = targets.filter(
	(t) => t !== target && t.startsWith(`${target}--`),
	);
	if (atomizedTargets.length > 0) {
	rootTargets.add(target);
	atomizedTargetsMap.set(target, atomizedTargets);
	targetsToExclude.push(...atomizedTargets);
	}
	}

Spotted by Graphite Agent



Is this helpful? React 👍 or 👎 to let us know.

[nx-cloud]

Important

A new CI pipeline execution was requested that may update the conclusion below...

Nx Cloud is proposing a fix for your failed CI:

This change fixes the detectAtomizedTargets function to only exclude targets that actually follow the atomized naming pattern (rootTarget--*). The previous implementation incorrectly filtered out all targets in a targetGroup except the root, which caused nx:run-script targets like deploy and custom-hello (from package.json scripts) to disappear from the compressed output. With this fix, only true atomized targets are excluded while maintaining the PR's token-efficiency improvements.

We verified this fix by re-running nx-mcp-e2e:e2e-ci--src/nx-project-details-compressed-targets.test.ts.

diff --git a/libs/shared/llm-context/src/lib/project-graph.ts b/libs/shared/llm-context/src/lib/project-graph.ts
index db0802ae..dc370c7b 100644
--- a/libs/shared/llm-context/src/lib/project-graph.ts
+++ b/libs/shared/llm-context/src/lib/project-graph.ts
@@ -31,7 +31,10 @@ export function detectAtomizedTargets(targetGroups: Record<string, string[]>): {
 
     // The group name is the root target name (from metadata)
     const rootTarget = groupName;
-    const atomizedTargets = targets.filter((t) => t !== rootTarget);
+    // Only consider targets atomized if they follow the pattern: rootTarget--*
+    const atomizedTargets = targets.filter(
+      (t) => t !== rootTarget && t.startsWith(`${rootTarget}--`),
+    );
 
     if (atomizedTargets.length > 0) {
       rootTargets.add(rootTarget);

  

Or Apply changes locally with:

npx nx-cloud apply-locally Pi6Q-3USi

Apply fix locally with your editor ↗   View interactive diff ↗

_{🎓 Learn more about Self-Healing CI on nx.dev}

[cursor]

You have run out of free Bugbot PR reviews for this billing cycle. This will reset on January 28.

To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.