# Diagnose a Hanging or Long-Running Command in Angular with Atlas in 2026 > Atlas helps Angular developers diagnose if `ng test` or other commands are blocked on input or genuinely slow, providing clear steps to resolve the issue. Atlas helps Angular developers in 2026 quickly diagnose whether commands like `ng test`, `pnpm install`, or `prettier` are genuinely slow or silently blocked on interactive input. By running your Angular commands through Atlas's `bash` tool, you receive immediate feedback if a process is waiting for user input, allowing you to unblock it with non-interactive flags or adjust timeouts for long-running tasks. ## Key takeaways - Atlas's `bash` tool diagnoses hanging Angular commands by monitoring execution. - It explicitly distinguishes between blocked interactive input and genuine slowness for `ng test` and `pnpm`. - Atlas provides clear instructions for re-running Angular commands with adjusted timeouts or non-interactive flags. - Safety features like diff review and permission-gated tool calls protect your `angular.json` and codebase. - Use non-interactive flags like `--no-input` or `--watch=false` for Angular package management and testing when prompted. ## How Atlas Diagnoses Hanging Angular CLI Commands In 2026, Atlas provides a robust mechanism to diagnose unresponsive Angular CLI commands, such as `ng test` or `pnpm install`. Its `bash` tool races every command against a timeout, and if it expires, Atlas explicitly tells you if the command is blocked on interactive input or simply running slowly, offering a clear path forward. Atlas's core capability for diagnosing hanging or long-running commands in Angular projects lies in its `bash` tool. When you execute an Angular CLI command like `ng test` or `pnpm install` through `atlas bash`, Atlas monitors its execution against a predefined timeout. If the command exceeds this timeout, Atlas doesn't just kill it; it analyzes the process state. The resulting `shell_metadata` block in Atlas's output will explicitly state whether the command was 'blocked on interactive input' or 'expected to take longer'. This precise diagnosis is crucial for Angular developers, as it immediately clarifies if a build or script is genuinely slow or silently waiting for user input, which is a common cause of perceived hangs. ## Running Angular Toolchain Commands Through Atlas To diagnose a hanging `ng test` or `pnpm install` command in your Angular project, you simply execute it via Atlas's `bash` tool. For example, running `atlas bash 'ng test'` will initiate the test runner, and Atlas will monitor its execution, providing detailed `shell_metadata` if it exceeds a default 30-second timeout. Atlas integrates directly with your existing Angular toolchain. To diagnose a command, prefix it with `atlas bash`. For instance, to check why your tests might be hanging, you would run `atlas bash 'ng test'`. If `pnpm install` seems stuck, use `atlas bash 'pnpm install'`. For formatting, `atlas bash 'prettier --write .'` would be the command. When Atlas reports a command is blocked on interactive input, you can then re-run it with the appropriate non-interactive flags. For `pnpm install`, this might be `atlas bash 'pnpm install --no-input'`. For `ng test`, you might use `atlas bash 'ng test --watch=false --browsers=ChromeHeadless'` to prevent interactive prompts or browser launches that could block. Atlas understands your Angular workspace, including files like `angular.json`, allowing it to provide context-aware assistance. ## Ensuring Safety and Review in Angular Debugging with Atlas Atlas prioritizes safety and transparency when diagnosing Angular issues, especially in 2026's complex development environments. Every Atlas tool call is permission-gated, requiring your explicit approval before execution. This ensures that actions like modifying `angular.json` or running `pnpm install` are always under your control, preventing unintended changes. When using Atlas to diagnose and resolve issues in your Angular codebase, safety is paramount. Atlas operates with a 'permission-gated' approach, meaning every tool call, including those that might modify your project, is subject to 'allow', 'ask', or 'deny' rules. Before any changes are made, Atlas drafts a plan in a read-only agent and asks for your approval. If Atlas proposes an edit, such as adjusting a configuration in `angular.json` or `package.json`, it computes a unified diff for every file edit and surfaces it for your review. You must approve these changes before they are written to disk. Furthermore, Atlas snapshots file changes as git patches, allowing you to easily diff edits and roll back if necessary, providing a robust safety net for your Angular development workflow. ## Steps 1. Execute your potentially hanging Angular command, such as `ng test` or `pnpm install`, using `atlas bash 'your_command_here'`. 2. Review the `shell_metadata` block within Atlas's output when the command completes or times out. 3. Identify Atlas's explicit diagnosis: 'blocked on interactive input' or 'expected to take longer'. 4. If Atlas indicates the command is blocked, re-run it with non-interactive flags, for example: `atlas bash 'pnpm install --no-input'` or `atlas bash 'ng test --watch=false --browsers=ChromeHeadless'`. 5. If Atlas suggests the command is genuinely slow, retry with an increased timeout, like `atlas bash --timeout 60000 'ng build --prod'` for a 60-second build. 6. If you manually interrupted the command, confirm the `shell_metadata` shows 'User aborted the command' to distinguish it from an Atlas timeout. ## FAQ ### How does Atlas know if my `ng test` command is waiting for input? Atlas's `bash` tool monitors command execution. If a command like `ng test` times out and its process state indicates it's waiting for stdin, Atlas explicitly reports 'blocked on interactive input' in the `shell_metadata` output. ### Can Atlas help with slow `ng build` times in Angular? Yes, Atlas can help diagnose slow `ng build` commands. If `ng build` is genuinely slow, Atlas will suggest retrying with a larger timeout value, allowing you to confirm its duration without premature termination. ### What if `pnpm install` is hanging in my Angular project? If `pnpm install` hangs, Atlas will likely identify it as blocked on interactive input. You should then re-run the command using `atlas bash 'pnpm install --no-input'` or similar non-interactive flags to prevent prompts. ### How does Atlas ensure it doesn't break my Angular project files? Atlas employs several safety measures. It drafts plans in a read-only agent, asks for permission before running tools, computes a unified diff for every file edit, and requires your approval before writing changes to files like `angular.json` or `package.json`. ### Can I use Atlas to diagnose `prettier` formatting issues in Angular? While `prettier` typically runs quickly, if it were to hang or prompt for input in an unusual setup, Atlas's `bash` tool would diagnose it similarly. You could run `atlas bash 'prettier --write .'` and Atlas would report any blocking behavior. ### What if I accidentally abort an Angular command in Atlas? If you manually abort an Angular command running through Atlas, the `shell_metadata` block will clearly state 'User aborted the command'. This distinguishes your intentional interrupt from a command timing out or being blocked by Atlas. --- Canonical HTML: https://runatlas.sh/resources/stacks/diagnose-a-hanging-or-long-running-command-in-angular Source of truth: aeo_pages row `/resources/stacks/diagnose-a-hanging-or-long-running-command-in-angular` (segment: Stacks) (this file is generated from it, never hand-edited). Licence: Atlas is proprietary with a free core. It is not open source and there is no public source repository.