Skip to main content

Work with Tines 3B from your terminal using the command line interface (CLI)

Learn how to install and use Tines 3B in your CLI.

Written by Jamie Gaynor

You don't have to leave your terminal to build with Tines 3B. The Tines 3B CLI lets you run and chat with workflows, inspect executions and logs, manage connectors, and authenticate Git, all from the command line. It's a natural fit when you're building workflows in a coding agent like Claude Code, scripting against Tines 3B, or you just prefer the keyboard.

This article walks you through installing the CLI, signing in, and the commands you'll use most.

Install the CLI

You'll find the exact install command in Tines 3B under Settings, then CLI. It looks like this:

curl --proto '=https' --tlsv1.2 -fsSL https://sh.3b.dev/cli/install.sh | sh

The installer saves the CLI to ~/.local/bin. If that directory isn't on your PATH, the installer prints the line to add, for example:

export PATH="$HOME/.local/bin:$PATH"

To install somewhere else, set INSTALL_DIR before running the script.

Sign in to your tenant

Authenticate against your tenant with auth login, passing your tenant host:

3b auth login --host your-tenant.3b.dev

This opens your browser so you can approve the login. A few notes:

  • No browser? Add --no-browser to print the approval URL instead, then open it yourself.

  • Automating with a service account? Add --service-account to authorize a service account rather than your own user.

  • Shorter-lived credentials? Use --ttl-seconds to request a specific credential lifetime. The server caps the maximum.

The CLI stores your profile and credentials under ~/.config/3b, with the config directory locked to your user and the credential files kept private.

Once you're signed in, confirm it works by listing the spaces you can reach:

3b spaces

Run 3b --help at any time to see every command and flag.

Run and chat with workflows

The CLI reads standard input and writes standard output, so workflows compose cleanly with the rest of your shell.

To trigger a run and wait for the result, pipe your input into run with --wait:

echo "Hello" | 3b run wf_abc123 --wait

To send structured input, set the content type to match your data:

cat data.json | 3b run wf_abc123 --wait --type application/json

A few more everyday commands:

  • List recent runs. 3b runs wf_abc123 shows a workflow's latest runs. Add --limit to change how many you see.

  • Check a run's status. 3b status wf_abc123 reports on the most recent run, or pass a run id to check a specific one.

  • Hold a conversation. 3b chat wf_abc123 opens an interactive chat with a workflow. Press Ctrl+D to exit.

Most workflow commands accept --branch so you can target a draft branch instead of the live version.

Inspect executions and logs

When you need to dig into what happened, work down from the workflow to a single execution:

  • List executions. 3b executions wf_abc123 lists recent executions. Filter with --status (pending, success, or error), --kind (build or run), or --step to focus on one step directory.

  • Get the details. 3b execution ex_xyz123 returns an execution's details, and 3b output ex_xyz123 returns just its output.

  • Read the logs. 3b logs ex_xyz123 prints an execution's logs, which is usually where you'll start when something failed.

For example, to find failures and then read one:

3b executions wf_abc123 --status error 3b logs ex_xyz123

Authenticate Git without tokens in the URL

Every Tines 3B space is a plain Git repository, so you can clone it into your own editor or coding agent. The CLI can configure Git to authenticate for you, so you never have to put an API key in a clone URL.

Note: Git authentication happens for your tenant automatically when you log in. Run configure if you need to set it up again

3b configure --host your-tenant.3b.dev

After that, clone the space's Git URL directly. You'll find it under your space settings in the Git URL section:

git clone https://your-tenant.3b.dev/spaces/your-space.git

The CLI registers itself as a Git credential helper for your tenant's origin, so Git asks the CLI for credentials on the fly. If it can't configure Git automatically, it prints the exact git config commands to run by hand.

Manage connectors from JSON

You can create and update connectors without opening the app. Describe the connector's settings and plaintext secrets in a JSON file, then pass it in:

3b connectors create --input connector.json --key key.json

To change an existing connector, use update with its id:

3b connectors update ca_abc123 --input connector.json

The --key file is the tenant connector key, which you'll find in Tines 3B under Settings, then Security. Connector create and update require glibc Linux or macOS, since they rely on the 3b-seal helper.

You can also browse and attach connectors to steps with 3b apps, including 3b apps connect and 3b apps disconnect.

Use profiles and environment variables

If you work with more than one tenant, set up a named profile for each and switch between them with the global --profile flag:

3b --profile staging spaces

Several environment variables give you more control, which is handy in scripts and CI:

  • `THREE_B_PROFILE` selects a profile, the same as --profile.

  • `THREE_B_API_KEY` supplies an API key directly, overriding stored credentials.

  • `THREE_B_API_URL` overrides the API base URL.

  • `THREE_B_UI_URL` overrides the UI base URL used during login.

Keep the CLI up to date

To fetch and install the latest version in place, run:

3b upgrade

Where to go next

The CLI is one of three ways to work with Tines 3B from outside the app, alongside Git (clone a space and push your changes) and the REST API (authenticate with a bearer token, with full docs at /api/v1/docs on your tenant). Pick whichever fits the task, or mix them: build in your editor over Git, then run and inspect with the CLI.

Did this answer your question?