Installation
Agent to Bricks has three components: a WordPress plugin, a CLI binary, and an optional desktop GUI. You need the plugin and CLI at minimum. The GUI is for people who want a visual interface for managing AI agent sessions.
System requirements
Section titled “System requirements”| Component | Requirement |
|---|---|
| WordPress | 6.0 or higher |
| PHP | 8.0 or higher |
| Bricks Builder | 1.9 or higher |
| Automatic.css | 3.x recommended (not required) |
| Frames | Optional, for component templates |
1. Install the WordPress plugin
Section titled “1. Install the WordPress plugin”Download agent-to-bricks-plugin-X.X.X.zip from the latest GitHub release.
In your WordPress admin:
- Go to Plugins > Add New > Upload Plugin
- Upload the zip file and click Install Now
- Activate the plugin
Then generate your API key:
- Go to Settings > Agent to Bricks
- Click Generate API Key
- Copy the key somewhere safe — you’ll need it to connect the CLI
The API key authenticates all requests from the CLI to your site. Keep it private.
2. Install the CLI
Section titled “2. Install the CLI”Download the binary for your platform from the latest release:
| Platform | File |
|---|---|
| Mac (Apple Silicon) | agent-to-bricks_X.X.X_darwin_arm64.tar.gz |
| Mac (Intel) | agent-to-bricks_X.X.X_darwin_amd64.tar.gz |
| Linux (x86_64) | agent-to-bricks_X.X.X_linux_amd64.tar.gz |
| Windows (x86_64) | agent-to-bricks_X.X.X_windows_amd64.zip |
Mac and Linux
Section titled “Mac and Linux”Extract the archive and move the binary into your PATH:
tar xzf agent-to-bricks_*.tar.gzsudo mv bricks /usr/local/bin/Verify it works:
bricks versionWindows
Section titled “Windows”- Unzip the downloaded file
- Move
bricks.exeto a directory in your PATH (e.g.,C:\Users\YourName\bin\) - Or add the extracted folder to your PATH environment variable
Open a new terminal and run:
bricks versionBuild from source
Section titled “Build from source”If you prefer to compile it yourself, you’ll need Go 1.22 or higher:
cd cligo build -o bricks .sudo mv bricks /usr/local/bin/Or use the Makefile:
make build # outputs to bin/bricksmake install # copies to /usr/local/bin3. Connect the CLI to your site
Section titled “3. Connect the CLI to your site”The fastest way is the interactive setup wizard:
bricks config initIt will prompt you for your site URL and the API key you copied from the plugin settings.
If you’d rather set values directly:
bricks config set site.url https://your-site.combricks config set site.api_key YOUR_API_KEYThis writes to ~/.agent-to-bricks/config.yaml.
4. Verify the connection
Section titled “4. Verify the connection”bricks site infoYou should see output like:
Site: https://your-site.comBricks: 1.11.1WordPress: 6.7.2PHP: 8.2.27Plugin: 1.2.0If you get a connection error, double-check the URL (make sure it includes https://) and confirm the API key matches what’s in your plugin settings.
5. Install the GUI (optional)
Section titled “5. Install the GUI (optional)”The desktop GUI is a Tauri app that manages AI coding agent sessions. Skip this if you only need the CLI.
Prerequisites
Section titled “Prerequisites”- Node.js 18 or higher
- Rust (required by Tauri)
- At least one AI coding tool: Claude Code, Codex, or OpenCode
Development mode
Section titled “Development mode”cd guinpm installnpm run tauri devThis launches the app with hot reload for development.
Build a standalone app
Section titled “Build a standalone app”cd guinpm run tauri buildThe compiled binary lands in gui/src-tauri/target/release/bundle/.
Updating
Section titled “Updating”The CLI can update itself and the plugin in one go:
bricks update # update both CLI and pluginbricks update --check # check for updates without installingbricks update --cli-only # update just the CLINext steps
Section titled “Next steps”With the plugin and CLI installed, head to the Quick start to pull your first page and generate content.