> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sidecardata.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Runs and approvals
> Follow Agent Console runs, approve gated tools, and review artifacts
The **Console** lists runs across every agent and job. A job page also shows its recent runs.
Click a run to review its origin, current status, turn timeline, transcript, approvals, and artifacts.
## Run statuses
| Status | Meaning |
| --------------------- | --------------------------------------------------------------- |
| **Queued** | Sidecar accepted the run and is preparing it. |
| **Running** | The agent is working. |
| **Awaiting input** | The agent needs a reply before it can continue. |
| **Awaiting approval** | A gateable tool is waiting for an Account Admin. |
| **Blocked** | The run cannot continue without resolving a blocking condition. |
| **Succeeded** | The run completed successfully. |
| **Partial** | The run completed with an incomplete result or delivery. |
| **Failed** | The run stopped with an error. |
| **Cancelled** | An Account Admin stopped the run. |
## Start and cancel runs
An active manual or scheduled job has **Run now**. Starting it opens the run detail page.
Sidecar serializes runs for the same job and target. If the same job is already running, use the existing run instead. Different jobs can run at the same time.
Use **Cancel run** to stop an active run. Cancelling closes its pending approvals.
## Transcript
Expand a turn to see the agent messages and tool activity for that stage of the run. Older transcripts may become unavailable while run metadata and artifacts remain.
## Approvals
Tool permissions determine whether gateable web and MCP tools pause. Core repository tools do not pause.
When a run reaches **Awaiting approval**:
1. Open the approval card.
2. Review the tool, MCP server if applicable, and summarized inputs.
3. Click **Approve**, or click **Reject with note** and explain what the agent should do instead.
Only an Account Admin in the same workspace can decide. A decision is recorded with the approver and time.
Slack approval controls use the same authorization. If Slack asks you to link your identity, complete the one-time link before deciding. Linking does not grant the Account Admin role or approve the action.
## Artifacts
A completed run can produce:
* A pull or merge request
* A pushed branch or compare link
* A Markdown response in Agent Console
* A source-control review for Custodian
Open artifacts from the run detail page. Agents do not merge their own changes.
