Run project commands from a task and review operations that require approval.
Qoder can run project commands in the execution environment selected for the task. Access permissions determines when commands run directly and when file, terminal, or network access requires approval.
Select Open terminal panel at the top of the task. If no workspace is associated yet, the terminal area prompts you to add a folder first. You can also open the task sidebar and select Add tab → Open terminal.
The terminal panel supports:
When an approval request appears, review the command and its impact. Approve the operation, reject it, or ask Qoder to try another approach.
Before approving a command, check the workspace, current directory, arguments, network destination, and affected data. Keep approval enabled for deletion, dependency installation, system changes, credentials, and production operations.
When a command fails, read its result and verify the execution environment. Determine whether the cause is the command, a dependency, the network, or credentials. Do not switch to Full access only to bypass an error.
Open the terminal
Select Open terminal panel at the top of the task. If no workspace is associated yet, the terminal area prompts you to add a folder first. You can also open the task sidebar and select Add tab → Open terminal.
The terminal panel supports:
- creating and closing terminal sessions;
- splitting the terminal with Split right or Split down;
- switching between light and dark terminal appearance;
- closing or reopening the terminal panel.
pwd (cd on Windows) when you need to verify the current directory.
How commands are handled
| Access permission | Behavior |
|---|---|
| Ask for approval | Ask before running commands, modifying files outside the workspace, or accessing the network. |
| Auto approve | Run normal operations automatically and ask only when Qoder detects potential risk. |
| Full access | Do not show approval prompts; allow file, terminal, and network access. Use only when you understand the task and environment risks. |
Review command execution
Before approving a command, check the workspace, current directory, arguments, network destination, and affected data. Keep approval enabled for deletion, dependency installation, system changes, credentials, and production operations.
When a command fails, read its result and verify the execution environment. Determine whether the cause is the command, a dependency, the network, or credentials. Do not switch to Full access only to bypass an error.
Recommended practice
- Start with Ask for approval in an unfamiliar repository.
- Keep manual approval for dependency installation, deletion, system changes, credentials, and production operations.
- Before approval, check the working directory, full command, arguments, network destination, and expected write scope.
- After execution, inspect output and verify the result with tests or file diffs.