Guard training skills against Nextflow agent-mode console output - #982
Merged
Merged
Conversation
Nextflow 26.04+ detects the CLAUDECODE environment variable (set by Claude Code in every shell it runs) and silently switches to a machine-readable "agent mode" console format ([PIPELINE], [PROCESS], [SUCCESS]/[FAILED] tags) instead of the classic human-facing output learners actually see. Any skill that runs `nextflow` directly and copies its output into docs was at risk of baking in a format no learner will ever encounter (already found once, in docs/en/docs/execution_config/02_resources_and_retries.md). - Document the issue and the required override (env -u CLAUDECODE NXF_AGENT_MODE=false) in shared/repo-conventions.md - Apply the override in test-example and run-tutorial's concrete nextflow invocations - Add a hard-fail check for agent-mode tags to run-tutorial/references/acceptable-differences.md - Note in docker-setup why containerized runs are unaffected today, and warn against changing that Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
✅ Deploy Preview for nextflow-training ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
Nextflow linting complete!
💡 Tip: Click filename locations to go directly to that code. View all 45 issuesView formatting changes
|
Collaborator
Author
|
@pinin4fjords Found a fun issue-- Claude started complaining that the console output had changed dramatically and we needed to update all the console output text in all the courses. I freaked out a little before realizing it was just Nextflow recognizing Claude and setting agent mode automatically. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nextflow 26.04+ detects the CLAUDECODE environment variable (set by Claude Code in every shell it runs) and silently switches to a machine-readable "agent mode" console format ([PIPELINE], [PROCESS], [SUCCESS]/[FAILED] tags) instead of the classic human-facing output learners actually see. Any skill that runs
nextflowdirectly and copies its output into docs was at risk of baking in a format no learner will ever encounter (already found once, in docs/en/docs/execution_config/02_resources_and_retries.md).