> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-tools/legacy-tools-and-migration/terminal-legacy-stackai.md).

# Terminal (Legacy StackAI)

**Deprecated.** This is the older StackAI Terminal action. For new command execution, use [Terminal (StackAI Computer)](https://docs.stackai.com/stackai-tools/browser-and-computer/terminal-stackai-computer.md) when StackAI Computer is available.

## Replace the legacy action

Identify the command, working files, required packages, and downstream uses of standard output or generated files. Configure the current Terminal for that task, then inspect its result before reconnecting later steps.

Do not assume a sandbox identifier, installed dependency, or file path from the legacy action exists in the new execution context. Confirm that the command succeeds and the required files can be opened. Use [Canvas Share File](https://docs.stackai.com/stackai-tools/browser-and-computer/canvas-share-file.md) if the user needs access to an existing sandbox file.

Follow the checklist in [Legacy Tools and Migration](https://docs.stackai.com/stackai-tools/legacy-tools-and-migration.md) before publishing the replacement.


---

# 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://docs.stackai.com/stackai-tools/legacy-tools-and-migration/terminal-legacy-stackai.md?ask=<question>&goal=<user_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.
