# The briq CLI, your stack in briq.yaml

URL: https://briq.cloud/blog/changelog-2026-10-23

> Week of 19 October: the briq CLI, a stack declared in briq.yaml, a database per git branch, reports in DuckDB and n8n automations.

By Sylvain Goumy, Founder of briq ([LinkedIn](https://www.linkedin.com/in/sylvain-goumy/), [X](https://x.com/goooums), [GitHub](https://github.com/goums)). Changelog, 23 October 2026.

Here is what changed for you and your agents this week.

## The briq CLI

Agents keep the MCP server. The CLI is for you, your scripts, git hooks and CI.

```bash
npm install -g @briq-cloud/cli
briq login
briq run postgres --sleep 2h
```

* **One command per MCP tool**, with the same options: `briq_exec` is `briq exec`.
* **Sign in with a link** you open on any device, or with an API key (`BRIQ_API_KEY`) in CI.
* **Open source**: the code is at [briq-cloud/briq-cli](https://github.com/briq-cloud/briq-cli),
  and each version is published to npm from there, with provenance.

The docs: [CLI](https://briq.cloud/docs/cli).

## Your stack in briq.yaml

Declare the services of a repo in a `briq.yaml` at its root, shaped like GitHub Actions
`services:`: a recipe and the fields it changes, or any image.

```yaml
stack: shop
services:
  db: { recipe: postgres, image: pgvector/pgvector:pg16 }
  cache: { recipe: redis }
```

`briq up` (or `briq_up` for an agent) makes each service the stack does not have yet and leaves
the others as they are. With `--expose`, the connection strings work from your laptop, over TLS.
A secret's value never goes in the file.

The docs: [Stack file](https://briq.cloud/docs/stack-file).

## A database per git branch

Fork a whole stack, data included, into a stack of its own for a branch:

```bash
briq fork --stack main --branch feat/login --env .env.local --expose
briq destroy --branch feat/login
```

The fork's connection strings land in `.env.local`, so the branch runs against its own copy. Put
the command in a git hook, or in Claude Code's worktree hooks, and each agent working in parallel
gets its own database. The template
[claude-parallel-worktree-template](https://github.com/briq-cloud/claude-parallel-worktree-template)
has all of it.

The guide: [Give each Claude Code worktree its own database](https://briq.cloud/docs/guides/claude-code-worktree-database).

## Reports in DuckDB

Ask your agent for a report on a dataset. The [duckdb](https://briq.cloud/cookbook/duckdb) recipe runs DuckDB inside
Shaper: the agent loads the file from its URL, writes the dashboard in SQL and sends you a link.
The data never goes through the agent.

```text
briq_run({ recipe: "duckdb", expose: "private" })
→ duckdb running · url: https://duckdb-r4tq.briq.run/?briq_token=…
```

From the first call to the charts on screen: 21 to 24 seconds. How we measured it:
[A shared report in 30 seconds, with DuckDB](https://briq.cloud/blog/reports-in-30-seconds-with-duckdb). The guide:
[Report on a dataset](https://briq.cloud/docs/guides/report-on-a-dataset).

## Automations in n8n

The [n8n](https://briq.cloud/cookbook/n8n) recipe runs n8n with a public URL for its webhooks. The agent builds,
activates and tests workflows through n8n's API; you check them in the editor.

```text
briq_run({ recipe: "n8n", expose: "public" })
→ n8n running · url: https://n8n-k3x9.briq.run/
```

briq makes n8n's owner before it starts, so no one else can claim the instance. The guides:
[Automate with n8n](https://briq.cloud/docs/guides/automate-with-n8n), and
[Run a webhook bot](https://briq.cloud/docs/guides/run-a-webhook-bot) for a WhatsApp bot in your own code.

## Try it

**Claude**

1. Add briq to Claude:

[Connect in Claude](https://claude.ai/directory/briq)

2. Connect Claude to briq: sign in, or create your account and claim your €10 of free credits.

**Other agents**

1. Paste this prompt into your agent:

```text
Add the briq MCP server to your config:
- name: "briq"
- url: https://api.briq.cloud/mcp (Streamable HTTP, OAuth)
- for all my projects

Then tell me what to do next to connect and activate it. If needed, read the setup instructions for agents: https://briq.cloud/docs/setup/agents.md
```

2. Follow your agent's next steps: usually a restart, then a link to sign in.

**Try it**

- GitHub repo: "Deploy briq-cloud/wall github repo on briq (https://briq.cloud/docs/guides/run-a-github-repo.md) and give me a link to it."
- Sandbox: "Start a sandbox on briq (https://briq.cloud/cookbook/sandbox.md), clone this project into it, run the test suite there instead of on my machine, and tell me what fails."
- Reporting: "Start DuckDB on briq (https://briq.cloud/cookbook/duckdb.md), load 'Our World in Data' energy dataset into it, generate a report on world energy generation, and share it with me." (DuckDB is an open-source analytics database; the dashboards are written in SQL.)
- Postgres: "Start a Postgres for this project on briq (https://briq.cloud/cookbook/postgres.md) and connect the app to it."
- Web app: "Run this app on briq (https://briq.cloud/cookbook/node.md) and give me a preview link."
- Memory: "Start a SiYuan notebook on briq (https://briq.cloud/cookbook/siyuan.md), keep your notes on this project in it, and give me a link to browse them." (SiYuan is an open-source notes app, like Obsidian.)
- Planning: "Start a Plane board on briq (https://briq.cloud/cookbook/plane.md), turn our TODO list into issues, and give me a link to the board." (Plane is an open-source project board, like Linear.)

Tell us what to build next at [hello@briq.cloud](mailto:hello@briq.cloud), or ask your agent to
send it with `briq_feedback`.