# T3 Cloud recipe

URL: https://briq.cloud/cookbook/t3-cloud

> Native T3 with saved CLI connections, Briq MCP and skills in a personal sandbox.

Tags: agents

## Run it

CLI:

```bash
briq run t3-cloud --expose private
```

MCP:

```ts
briq_run({ recipe: "t3-cloud", expose: "private", wait: true })
```

REST:

```bash
curl -X POST https://api.briq.cloud/v1/briqs \
  -H "Authorization: Bearer $BRIQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "recipe": "t3-cloud",
    "expose": "private",
    "wait": true
  }'
# → { "briqs": [{ "id": "bq_…", … }], "outputs": { "T3_HOST": "…" }, … }

# ... when done, for each briq id
curl -X DELETE https://api.briq.cloud/v1/briqs/<id> \
  -H "Authorization: Bearer $BRIQ_API_KEY"
```

briq.yaml:

```yaml
stack: app
services:
  t3:
    recipe: t3-cloud
    expose: private
    # its defaults, each a field you can set:
    # image: ghcr.io/briq-cloud/t3-cloud@sha256:d322bd1371df2280d48a54e7f1ea0d96f8f60195ad8af011448269154b18a0a1
    # size: small
    # volume: { gb: 12 }
```

## Fields

Set them beside `recipe`, in briq_run or a briq.yaml service, as a GitHub Actions service.

| Name | Type | Options | Default | What it does |
| --- | --- | --- | --- | --- |
| `image` | string | — | "ghcr.io/briq-cloud/t3-cloud@sha256:d322bd1371df2280d48a54e7f1ea0d96f8f60195ad8af011448269154b18a0a1" | A published T3 Cloud image digest |
| `env` | record | { key: string \| { secret, value?, literal?, scope?, hosts?, locations? } } | {} | Added to the home's environment. API-key mode for a vendor: its team secret, { secret: "ANTHROPIC_API_KEY", scope: "team" }, which the credential gateway fills on the way to the vendor. ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, CLAUDE_CODE_OAUTH_TOKEN, OPENAI_API_KEY, CODEX_API_KEY, COPILOT_GITHUB_TOKEN, GH_TOKEN, GITHUB_TOKEN, CURSOR_API_KEY, XAI_API_KEY, MISTRAL_API_KEY, GEMINI_API_KEY, GOOGLE_API_KEY are taken only that way: any other value replaces the person's subscription. A base URL, a proxy or CA variable, PATH and HOME are refused |
| `size` | enum | pico, micro, nano, small, medium, large, xlarge | "small" | Compute size for native T3 and its CLI sessions |
| `volume` | object | { gb? } | {"gb":12} | The volume at /work, sign-ins, files and app updates: { gb } |

## Outputs

Returned by `briq_run` once the stack is healthy. Hosts resolve inside your team network; secrets are generated per run.

| Output | Value |
| --- | --- |
| `T3_HOST` | `t3.<stack>.internal` |
| `WORKDIR` | `/work` |
| `STATE` | `/work/.t3` |

## What it runs

| Briq | Image | Ports | Size | Volume |
| --- | --- | --- | --- | --- |
| t3 | `ghcr.io/briq-cloud/t3-cloud@sha256:d322bd1371df2280d48a54e7f1ea0d96f8f60195ad8af011448269154b18a0a1` | 8080, 8081 | small | 12 GB at /work |

## When to use it

* Use T3 from the official phone app or a browser.
* Keep subscription sign-ins on one central Briq.
* Give each new native thread its own Briq workspace.

## Set up T3

```text
briq_run({ recipe: "t3-cloud", stack: "t3-ana", expose: "private" })
```

The default 12 GB volume requires Pro or Team. Leave disk capacity for thread workspaces.

Retrieve the owner key using the Briq ID returned by `briq_run`:

```bash
briq exec <briq-id> -- node -p 'process.env.T3_CLOUD_OWNER_KEY'
```

Open `https://<T3-host>/_cloud/` with the private endpoint's access token.
Enter the printed owner key to open **T3 Cloud Connections**. Keep the key private.

1. Choose **Open native Briq sign-in** and approve the CLI credential in your browser.
2. Choose **Connect Codex** and complete its subscription sign-in.
3. Under **Pair your phone with central T3**, choose **Create five-minute central pairing**.
4. In the official T3 phone app, scan the QR code or enter the displayed server URL and pairing code.
5. For browser access, choose **Create a five-minute T3 pairing**. Open its link in the same browser, then **Open T3**.

Cloud sessions currently support Codex. Claude Cloud is disabled pending validation.

## Tips

* **Leave room for updates**: new T3 homes default to a 12 GB volume for app update preparation.
* **Wake before pairing**: open the private owner page first if the central Briq is asleep.
* **Pair with central T3**: each new native thread allocates a separate Briq workspace automatically.
* **Budget for workspaces**: each running workspace has its own compute cost, alongside the central Briq.
* **Manage subscriptions centrally**: CLI sign-ins stay on the central volume; thread workspaces use its connections.
* **Keep pairing codes private**: create a fresh code after five minutes.
* **Keep files in git**: the volume is never forked or backed up.
