# A desktop for your agent, resize a briq

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

> Week of 26 October: a desktop your agent drives and you watch, resize a briq in place, write to a running command, Cursor and VS Code in one click.

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, 30 October 2026.

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

## A desktop your agent drives

The [desktop](https://briq.cloud/cookbook/desktop) recipe is a screen with Chromium on it, for an agent that must use
a website like a person: sign in, click through, fill a form.

```text
briq_run({ recipe: "desktop", expose: "private" })
```

* **Two MCP servers** in the outputs: the page by its accessibility tree (Playwright MCP), or the
  whole screen in pixels, as computer-use tools expect.
* **Watch it**: the briq's URL shows the screen, view only. Turn View only off to take over for a
  sign-in or a second factor.
* **Stays signed in**: the browser profile is on the volume, through sleep and restarts. It is
  never copied, so a desktop cannot be forked.

## Resize a briq

A database that needs more memory, or a disk that filled up, keeps its data, URLs and secrets.

```text
briq_resize({ briq: "bq_…", size: "medium" })
briq_resize({ briq: "bq_…", volumeGb: 20 })
```

* **A new size** restarts a running briq; a sleeping one gets it at its next start.
* **A bigger volume** grows while the briq runs, with no restart. A volume only grows.
* **In the dashboard**: the **Resize** button on the briq's page.

The docs: [Resize](https://briq.cloud/docs/concepts/lifecycle-and-sleep#resize).

## Write to a running command

A command started with `async: true` can now take input while it runs, for a REPL, an interactive
tool or a session over stdin.

```text
briq_exec({ briq: "bq_…", cmd: ["python3", "-i"], async: true, stdinOpen: true })
briq_exec_input({ briq: "bq_…", exec: "ex_…", seq: 1, data: "print(2 + 2)\n" })
→ written as seq 1
```

* **Follow the output**: `briq_exec_result` with `offset` reads from a byte on, so every byte comes
  once, in order.
* **Safe retries**: a write sent again with the same `seq` is not written twice.
* **Environment per command**: `env` sets variables for one command; `clearEnv` keeps the briq's
  own, such as an API key, away from it.

The guide: [Run a long command](https://briq.cloud/docs/guides/run-a-long-command#write-to-it-while-it-runs).

## Cursor and VS Code in one click

The connect steps on our site and in the dashboard have a **Cursor** tab and a **VS Code** tab,
like Claude's: one button installs briq, then you sign in. Other agents keep the install prompt.
briq is also listed in the [Cursor Directory](https://cursor.directory/plugins/briq).

The steps per client: [Clients](https://briq.cloud/docs/setup/clients).

## A skill for agents that use skills

Some agents find their tools through skills rather than MCP directories. briq has one, in the
Agent Skills format: when to use briq, how to connect it, and the calls for a sandbox and a stack.
It is served from [briq.cloud/.well-known/skills](https://briq.cloud/.well-known/skills/briq/SKILL.md), which Hermes
reads, and is in [briq-cloud/briq-mcp](https://github.com/briq-cloud/briq-mcp).

## 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.

**Cursor**

1. Add briq to Cursor:

[Add to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=briq&config=eyJ1cmwiOiJodHRwczovL2FwaS5icmlxLmNsb3VkL21jcCJ9)

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

**VS Code**

1. Add briq to VS Code:

[Install in VS Code](https://vscode.dev/redirect/mcp/install?name=briq&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapi.briq.cloud%2Fmcp%22%7D)

2. Connect VS Code 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.)

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