docs(core): document argv in task execution hook contexts (#33322) The `argv` field was already implemented in `PreTasksExecutionContext` and `PostTasksExecutionContext` but lacked tests and documentation for plugin authors to discover and use it. ## Changes - **Added unit tests** (`packages/nx/src/daemon/server/handle-tasks-execution-hooks.spec.ts`) validating that `argv` flows correctly through hook handlers for different command patterns (direct, affected, run-many) - **Enhanced existing documentation** in `astro-docs/src/content/docs/extending-nx/task-running-lifecycle.mdoc` with a new section covering: - Context property definitions showing the `argv` field - Examples showing how to detect command types (direct execution, affected, run-many) - Example demonstrating conditional analytics based on the original command - Common command patterns reference - Best practices for defensive argv parsing ## Usage ```typescript import type { NxPlugin, PostTasksExecutionContext } from '@nx/devkit'; export const myPlugin: NxPlugin = { name: 'my-plugin', postTasksExecution: async (options, context: PostTasksExecutionContext) => { // Distinguish between nx build my-app vs nx affected -t build if (context.argv.includes('affected')) { console.log('Running in affected mode'); } } }; ``` Fixes https://linear.app/nxdev/issue/NXC-3382/add-contextargv-to-task-execution-hook-contexts

Original prompt

> Issue Title: Add context.argv to task execution hook contexts > Issue Description: Expose the original CLI arguments on the plugin worker so hooks can distinguish how execution was started (e.g., `nx build nx-api` vs `nx affected -t build`). Proposal: include the invoking argv on the hook context (e.g., `context.argv`). > Fixes https://linear.app/nxdev/issue/NXC-3382/add-contextargv-to-task-execution-hook-contexts > > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > [https://github.com/nrwl/nx](https://github.com/nrwl/nx) > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > Aha! that worked - so you can tell it to assign to copilot instead of "me and copilot" > > Comment by User d484ef82-7f7d-4a95-be09-9d82ca3905dc: > 📋 I wasn't able to determine which GitHub repository to work in. > > I think it's one of these, but can you tell me which one is right? > > Comment by User : > Created issue [NXC-3382](https://linear.app/nxdev/issue/NXC-3382/add-contextargv-to-task-execution-hook-contexts) > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > This comment thread is synced to a corresponding [thread in Slack](https://nrwl.slack.com/archives/C070BJ2JYLW/p1761928859857989?thread_ts=1761928859.857989&cid=C070BJ2JYLW). All replies are displayed in both locations. > > Comment by User : > This thread is for an agent session with githubcopilot. > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > @Linear make a ticket and assign it to copilot > > Comment by User f5ae6d50-28e9-4ee7-ad51-3da8208d5914: > Makes sense to me > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > Sure, context.argv? > > Comment by User f5ae6d50-28e9-4ee7-ad51-3da8208d5914: > We can add them as `argv`? > > Comment by User f5ae6d50-28e9-4ee7-ad51-3da8208d5914: > Yeah they would run on the plugin worker so it's not there > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > @jason we could add `originalArgv` to the contexts? > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > Eh, probably not... they run on the plugin worker > > Comment by User 4215f3ef-50bd-4f09-85a0-b489c88057b6: > Yeah, I don't think the hooks know.... I'd be curious if process.argv would just have that info though > > Comment by User 439b15a6-827b-4258-971a-d86133ad59de: > payfit does > > Comment by User 74901385-a023-4825-8470-fe68b1b55664: > I can’t see anything about that in the docs - so I would assume the hooks are agnostic to how the tasks were triggered? > > Comment by User 74901385-a023-4825-8470-fe68b1b55664: > so they’re asking is there’s a way to tell the difference between `nx build nx-api` or `nx affected -t build` in the task hook? > > Comment by User 74901385-a023-4825-8470-fe68b1b55664: > > I’ve been playing around with the Task Execution Hooks, specifically the postTasksExecution hook, and I think it will be really useful for me to grab some detailed metrics for our specific use cases. > > What I feel like it’s missing is a way to see what command actually started the task execution, whether it was a specific target or an affected command. As long as it was a specific target, I think the tasks are sorted in order so the last taskResult will probably be the actual target of the command but for affected it seems a bit more random what the last result will be. > > Is there a way to know exactly which command kicked off the ‘task execution’? > >

--- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey). --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: AgentEnder <6933928+AgentEnder@users.noreply.github.com> Co-authored-by: Craigory Coppola Co-authored-by: Caleb Ukle Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: Copilot