> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/1.2/reference/step-definitions/run-command-line.md).
# Run command line
The **Run command line** step can be used to run arbitrary commands. These will be executed with "cmd.exe" (on Windows) or "bash" (on Linux), so no prefix is needed on the command lines themselves.
Note that the command specified should not ask for user input, as that would hang the process. There is presently no user interaction allowed with the started command (it will run hidden).
Optional settings can be specified to configure the working directory (it will default to the location of the content item specified), the success codes (defaulting to "0 3010"), and a timeout (in minutes) before the started process is automatically terminated (causing the step to fail).
The output from the command will automatically be captured into the DeployR log.
{% hint style="info" %}
Note: Most commands could also be executed using a **Run PowerShell script** step.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.2pintsoftware.com/deployr/1.2/reference/step-definitions/run-command-line.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
