Using the AI agent

Documentation Index

Fetch the complete documentation index at: https://docs.bricks.tools/llms.txt

Use this file to discover all available pages before exploring further.

The AI agent is the core of CTOR. It can read and write files, edit code, run shell commands, and search your project — all through a chat interface. This page covers project sessions, scoped to a single BRICKS app. For workspace-level workflows like creating a new project, see Start chat.

​

Create a session

1. Select an app in the sidebar
2. Click New Session

Sessions are stored persistently and auto-titled based on your first message. Each session maintains its own conversation history and model selection.

​

Choose a model

Click the model selector in the input bar to pick an AI model. Models are grouped by provider:

• Anthropic — Claude Sonnet 4.6, Claude Opus 4.6, Claude Haiku 4.5
• OpenAI — GPT-5.3 Codex, GPT-5.2 Codex, GPT-5.2, GPT-5.1 Codex Mini
• OpenAI Codex — GPT-5.3 Codex, GPT-5.2 Codex
• Google — Gemini 3 Flash, Gemini 3 Pro
• GitHub Copilot — Multiple models from various providers
• OpenAI Compatible endpoints — Custom endpoints with per-endpoint model lists (Ollama, vLLM, LM Studio, etc.)

Only providers with configured API keys appear in the list. See settings to configure your API keys.

​

Set thinking level

Click the thinking selector next to the model selector to control the agent’s reasoning depth:

​

Send a message

Type your message in the input bar and press Ctrl+Enter (or click the send button). Use Shift+Enter for a new line. The agent streams its response in real-time. You can see:

• Text responses with full markdown rendering and syntax highlighting
• Thinking blocks showing the model’s reasoning process (expandable, requires Show Thinking Content)
• Tool calls displayed as expandable blocks with the tool name and arguments
• Tool results showing the output of each tool execution

Click Abort to stop a running response at any time.

​

Mention files

Type @ in the input bar to search for files in your project. Select a file to include its path in your message, giving the agent context about which files to work with.

• Browse directories by typing / after a folder name
• Navigate with arrow keys and select with Enter or Tab
• Up to 20 results are displayed

​

Use skills

Type / in the input bar to trigger skill command autocomplete. Selecting a skill injects its instructions as context for the agent. The selected skill appears as a removable pill in the input bar. The agent receives the skill’s content along with your message. See the skills reference for more details on creating and managing skills.

​

Attach images

Click the image attachment button or paste an image from your clipboard. Supported formats: PNG, JPG, JPEG, WebP, GIF. Images are sent to the model as base64-encoded content alongside your text message.

​

Tool calls and approval

The agent has six built-in tools: read_file, write_file, edit_file, bash, glob, and grep. When the agent runs a bash command, you see an approval prompt:

• Click Run to execute the command
• Click Reject to deny execution

If you have MCP servers configured, their tools are also available to the agent alongside the built-in tools.

​

Workspace profile

A pill next to the sandbox-mode selector shows which BRICKS workspace the agent is operating against. In a project chat the pill is read-only — CTOR matches the project’s workspaceId to one of your authenticated profiles and falls back to the active profile when no match exists. To run the agent against a different workspace, switch profiles from Settings → Account or from the main chat input bar before opening the project.

​

Sub-agents

The agent can delegate tasks to specialized sub-agents. Sub-agents run with a focused set of tools and instructions, making them ideal for scoped tasks like codebase exploration or code review. You can manage sub-agents from the sidebar. See the sub-agents reference for details on creating and configuring them.

​

Local devices

Click the Local Devices button in the input bar to scan for BRICKS Foundation devices and BRICKS Buttress servers on your local network. The dialog runs both scans in parallel — a failure on one side doesn’t blank the other’s list. Foundation device rows show address, version, and badges:

• This workspace — the device is bound to the same workspace as the current project
• CDP — the device supports the Chrome DevTools Protocol

Buttress server rows use a distinct violet accent and their own badges:

• JWT required / open — whether the server is bound to a workspace and requires a workspace JWT
• verified / UDP only — whether the HTTP /buttress/info probe succeeded, or only the UDP announcement was seen
• This workspace — the server is bound to the same workspace as the current project

Click any card to toggle its selection — multi-select is supported, but selection is mutually exclusive across kinds (picking a Buttress server clears any Foundation selection, and vice versa). The footer button changes based on what’s selected:

• Foundation devices → Inspect or Deploy inserts a /bricks-cli prompt that the bricks-cli skill runs.
• Buttress servers → Ask Agent to integrate inserts a /bricks-ctor prompt with each selected server’s identity, workspace match status, and announced generator caps. The bricks-ctor skill carries the integration rules — model recommendations per generator type, the canonical auto-discovery buttressConnectionSettings, and the iOS Simulator caveat (UDP discovery only works on real devices).

​

Next steps