> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Porter

> Give the Sazabi agent the Porter CLI (porter) in its sandbox to inspect and manage porter.run apps, deployments, and logs.

[All Porter integration capabilities](https://docs.sazabi.com/catalogs/integrations/porter)

## About

This CLI connection makes the Porter CLI (`porter`) available in the Sazabi agent's sandbox. The agent can use it for porter.run apps, deployments, and logs. The tool is baked into the sandbox image; connecting it authenticates the already-installed CLI.

## Prerequisites

* A Sazabi project.
* A Porter API token (`PORTER_TOKEN`), available from your Porter account settings.
* Optionally:
  * `PORTER_PROJECT` — your Porter project ID, to scope commands to a specific project.
  * `PORTER_CLUSTER` — your Porter cluster ID, to scope commands to a specific cluster.
  * `PORTER_HOST` — the Porter API host, if you are using a self-hosted Porter instance.

## Set up in the dashboard

Configure the sandbox in the dashboard under [**Settings > Sandbox CLIs**](https://app.sazabi.com/settings/sandbox-clis).

**Step 1**

### Find Porter in the catalog

In [**Settings > Sandbox CLIs**](https://app.sazabi.com/settings/sandbox-clis), find Porter under **Browse sandbox CLIs** and choose to connect it.

**Step 2**

### Provide credentials

Enter the required value: `PORTER_TOKEN` — your Porter API token. Optionally, provide `PORTER_PROJECT`, `PORTER_CLUSTER`, and/or `PORTER_HOST` to narrow the scope or point at a self-hosted instance. Save to store them securely; Sazabi injects them into the sandbox when the agent runs.

## Set up with the CLI

You can also configure the Porter CLI connection with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/sandbox-clis.md)).

```bash theme={"system"}
sazabi sandbox-clis connect porter --env PORTER_TOKEN=<your-porter-token>
```

To validate the credentials without saving, run the same command with `test` in place of `connect` (the test command also requires the `--env` flags).

## Verify

Ask the agent, in a thread, to run the `porter` CLI (a read-only or status command) and confirm it returns real output. If the command is not found, the CLI connection may not be enabled; if it runs unauthenticated or cannot connect, recheck the credentials.

## Troubleshooting

**Command not found** — Confirm the Porter CLI connection is enabled for the project under [**Settings > Sandbox CLIs**](https://app.sazabi.com/settings/sandbox-clis).

**Authentication or connection fails** — Recheck the credential/connection values under [**Settings > Sandbox CLIs**](https://app.sazabi.com/settings/sandbox-clis).

## Further reading

> [card] [Working with the agent](https://docs.sazabi.com/guides/investigate/working-with-the-agent.md)
>
> Put the connected CLI to work in an investigation thread.

> [card] [Set up the sandbox](https://docs.sazabi.com/guides/investigate/sandbox.md)
>
> How the sandbox works and its security model.

> [card] [Sandbox CLIs](https://docs.sazabi.com/catalogs/sandbox-clis.md)
>
> Browse the catalog and connect more tools.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.