T3 Cloud

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

  • agents

Run it

briq run t3-cloud --expose private

Fields

NameTypeOptionsDefault
imagestring—"ghcr.io/briq-cloud/t3-cloud@sha256:d322bd1371df2280d48a54e7f1ea0d96f8f60195ad8af011448269154b18a0a1"
envrecord{ key: string | { secret, value?, literal?, scope?, hosts?, locations? } }{}
sizeenumpico, micro, nano, small, medium, large, xlarge"small"
volumeobject{ gb? }{"gb":12}

Outputs

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

T3_HOST
t3.<stack>.internal
WORKDIR
/work
STATE
/work/.t3

What it runs

BriqImagePortsSizeVolume
t3ghcr.io/briq-cloud/t3-cloud@sha256:d322bd1371df2280d48a54e7f1ea0d96f8f60195ad8af011448269154b18a0a18080, 8081small12 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

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:

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.

On this page

Free to try

Try briq, on us.

Every new account starts with €10 of credits. No card.

Start building

How can we help?

Message to the briq team