Here is what changed for you and your agents this week.
A desktop your agent drives
The 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.
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.
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.
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.
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_resultwithoffsetreads from a byte on, so every byte comes once, in order. - Safe retries: a write sent again with the same
seqis not written twice. - Environment per command:
envsets variables for one command;clearEnvkeeps the briq's own, such as an API key, away from it.
The guide: Run a long command.
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.
The steps per client: 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, which Hermes reads, and is in briq-cloud/briq-mcp.
Try it
Add briq to Claude
In Claude: Settings → Connectors → Add custom connector.Name it briq-stg, paste this URL, then click Connect.
https://api.stg.briq.cloud/mcp
In Claude: Settings → Connectors → Add custom connector.Name it briq-local, paste this URL, then click Connect.
http://localhost:3001/mcp
Connect Claude to briq
Sign in, or create your account and claim your €10 of free credits.
Connect Cursor to briq
Sign in, or create your account and claim your €10 of free credits.
Connect VS Code to briq
Sign in, or create your account and claim your €10 of free credits.
Paste this prompt into your agent
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
Add the briq MCP server to your config: - name: "briq-stg" - url: https://api.stg.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://stg.briq.cloud/docs/setup/agents.md
Add the briq MCP server to your config: - name: "briq-local" - url: http://localhost:3001/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: http://localhost:3000/docs/setup/agents.md
Follow your agent's next steps
Usually a restart, then a link to sign in.
Try it
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.
Deploy briq-cloud/wall github repo on briq (https://stg.briq.cloud/docs/guides/run-a-github-repo.md) and give me a link to it.
Deploy briq-cloud/wall github repo on briq (http://localhost:3000/docs/guides/run-a-github-repo.md) and give me a link to it.
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.
Start a sandbox on briq (https://stg.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.
Start a sandbox on briq (http://localhost:3000/cookbook/sandbox.md), clone this project into it, run the test suite there instead of on my machine, and tell me what fails.
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.
Start DuckDB on briq (https://stg.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.
Start DuckDB on briq (http://localhost:3000/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.
Start a Postgres for this project on briq (https://briq.cloud/cookbook/postgres.md) and connect the app to it.
Start a Postgres for this project on briq (https://stg.briq.cloud/cookbook/postgres.md) and connect the app to it.
Start a Postgres for this project on briq (http://localhost:3000/cookbook/postgres.md) and connect the app to it.
Run this app on briq (https://briq.cloud/cookbook/node.md) and give me a preview link.
Run this app on briq (https://stg.briq.cloud/cookbook/node.md) and give me a preview link.
Run this app on briq (http://localhost:3000/cookbook/node.md) and give me a preview link.
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.
Start a SiYuan notebook on briq (https://stg.briq.cloud/cookbook/siyuan.md), keep your notes on this project in it, and give me a link to browse them.
Start a SiYuan notebook on briq (http://localhost:3000/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, or ask your agent to
send it with briq_feedback.