Conversation
- When called from a detected AI agent (via env vars like CLAUDECODE), skip the interactive prompt and auto-configure the detected agent plus any outdated agents - Report non-configured agents with a suggested command - When --agents is explicitly passed, ignore detection entirely - Strip AI agent env vars from e2e test environment to prevent leaks - Fix gemini e2e test assertions to use AGENTS.md (the actual rules file) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
View your CI Pipeline Execution ↗ for commit 0c63d68
☁️ Nx Cloud last updated this comment at |
![nx-cloud[bot]](https://avatars.githubusercontent.com/in/80458?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
…re-ai-agents Unify the automatic configuration logic so --no-interactive (without explicit --agents) behaves the same as AI agent auto-detection: update outdated agents and report non-configured ones. The detected agent is now also configured regardless of the --no-interactive flag. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…re-ai-agents Unify the automatic configuration logic so --no-interactive (without explicit --agents) behaves the same as AI agent auto-detection: update outdated agents and report non-configured ones. The detected agent is now also configured regardless of the --no-interactive flag. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> [Self-Healing CI Rerun]
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
…re-ai-agents Unify the automatic configuration logic so --no-interactive (without explicit --agents) behaves the same as AI agent auto-detection: update outdated agents and report non-configured ones. The detected agent is now also configured regardless of the --no-interactive flag. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> [Self-Healing CI Rerun]
There was a problem hiding this comment.
Nx Cloud has identified a possible root cause for your failed CI:
Our test failures are unrelated to this PR's changes to AI agent auto-detection. The failing tests (e2e-react, e2e-storybook) are in domains completely separate from the touched projects (e2e-nx, e2e-utils, nx), and exhibit pre-existing flakiness (0.25%-2.87%). The errors stem from environment issues: corrupted @microsoft/api-extractor dependency installation and corepack configuration problems in temporary test projects.
No code changes were suggested for this issue.
Trigger a rerun:
🎓 Learn more about Self-Healing CI on nx.dev
1 participant
Current Behavior
When
configure-ai-agentsis invoked from within an AI agent (e.g. Claude Code), it either shows an interactive multi-select prompt (which the agent can't interact with) or requires--agentsand--no-interactiveflags to work correctly. This makes the experience awkward when AI agents call the command as part of workspace setup.Expected Behavior
When an AI agent is detected (via environment variables like
CLAUDECODE), the command now:nx configure-ai-agents --agents ...commandWhen
--agentsis explicitly passed, detection is ignored entirely (existing behavior preserved).--checkmode also works with detection — it checks the detected agent plus all other configured agents.Additionally:
CLAUDECODE,CLAUDE_CODE,OPENCODE,GEMINI_CLI, etc.) from e2e subprocess environments to prevent the test runner's environment from leaking into testsAGENTS.md(notGEMINI.md) for gemini assertions, matching what the gemini generator actually creates for fresh installations