Brickr Assistant

> Ask questions about the workspace you are currently viewing without giving the chat permission to change it.

Brickr Assistant is an informational copilot inside the Builder and Form editor. It uses the current workspace and asset context to answer questions, but it is intentionally separate from the personal Brickr Agent that can build through an MCP client.

What the Assistant can read

The Assistant can inspect only data available to your current signed-in user and workspace:

  • Workspace name, plan, and a summary of available resources
  • Assets in the current workspace, including APIs, routes, forms, WebObjects, databases, and functions
  • Whether your personal Brickr Agent exists and which workspaces granted it access
  • The route or form that is currently open in the editor
  • Safe form-submission aggregates such as count, grouped count, sum, average, minimum, and maximum

Form questions such as "How many people voted for option A in this form?" use aggregate queries. The Assistant does not receive an unrestricted dump of submission rows.

How asset inventories are organized

When you ask what exists in a workspace, the Assistant groups the answer by top-level asset class. Each section uses the same kind of asset icon used in the dashboard. Routes use compact method labels and the established GET, POST, PUT, PATCH, and DELETE color dots. APIs, Forms, WebObjects, standalone Functions, KV Stores, Structures, Enums, and connected Cloudflare accounts are top-level assets.

Routes and owned flows are not reported as unrelated assets:

  • Normal routes appear below their API.
  • Submit and render flows appear below their Form.
  • Lifecycle flows appear below their Form or WebObject.
  • Functions owned by another asset appear below that owner; only standalone Functions get their own top-level entry.

Internal IDs stay hidden unless you explicitly ask for them.

Testing the current route

In the Builder, the Assistant can prepare and run the route that is currently open:

1. Ask it to test the current route and include the required query, header, body, or path values. 2. The values appear in the same parameter editor used by the Test Terminal. 3. Brickr saves the current graph first. The test stops if saving fails. 4. The Builder executes the current DEV route and waits for its response. 5. The Assistant receives the redacted result and explains the status, returned data, or structured error.

The Assistant cannot choose another route, call production, deploy, or bypass the permissions of the signed-in user. Test results are redacted and size-limited before they are returned to the model.

What the Assistant cannot do

Brickr Assistant cannot:

  • Create, edit, delete, or deploy assets and routes
  • Change a graph, form, WebObject, database, secret, or workspace setting
  • Read secret values, account credentials, or account email addresses
  • Grant itself or another Agent access to a workspace
  • Run an arbitrary production endpoint

These boundaries apply even when the prompt asks the Assistant to make a change.

Building with a personal Agent

When you ask Brickr Assistant to build or change something, it checks whether your personal Brickr Agent is configured and explains the next setup step. If you have not named an AI client yet, it asks whether you want to use Codex, ChatGPT, Claude, or another MCP-compatible client.

The external client connects to:

https://mcp.brickr.dev/mcp

The setup is client-specific. Codex has a CLI command, while ChatGPT is configured through Settings > Apps > Create and does not have a chatgpt mcp add command. Brickr Assistant uses a canonical client guide before giving instructions so that it does not translate one client's setup into a made-up command for another.

The personal Agent can work only in workspaces and with scopes you explicitly approve. See Brickr Agent for exact Codex and ChatGPT setup, connection, permission, and revocation details.

What's next?

| Topic | Description | |-------|-------------| | Brickr Agent | Connect an MCP client and approve scoped workspace access | | Test Terminal | Configure and run DEV route tests manually | | Form Submissions | View submissions and query safe aggregate insights |