BrickWright
BrickWright is an agentic framework for creating LEGO® builds with BrickLayer. Using BrickWright, you can direct your favorite AI agents (GPT, Claude, Gemini, etc.) to automatically create brick builds from text or image prompts and export them to LDraw.
Usage
1. Install prerequisites
Install the BrickWright CLI. We recommend using uv:
uv tool install brickwright
LDraw parts library (optional but recommended)
BrickWright can render a build to a preview image, letting the agent visually check a build. To enable rendering,
you must download the LDraw parts library and set the environment
variable $LDRAW_LIBRARY_PATH to its path. Without a library, the rendering tool is disabled.
2. Start creating!
Option 1: External Agent (e.g. Codex, Claude Code)
Simply prompt your favorite agent to create a brick build following the instructions in EXTERNAL_AGENT_INSTRUCTIONS.md.
Option 2: API key (e.g. OpenAI Platform, Claude Console)
Ensure that the key for your favorite AI provider is set as an environment
variable (e.g., $ANTHROPIC_API_KEY, $OPENAI_API_KEY).
export OPENAI_API_KEY="sk-XXX"
# OR
export ANTHROPIC_API_KEY="XXX"
Then, run brickwright generate:
brickwright generate "a detailed cruise ship" [--image ref.png] [--model M] [--effort E]
Specify the generation model (e.g. claude-opus-4-8, gpt-5) with --model or by setting the environment variable
$BRICKWRIGHT_GENERATION_MODEL.
You can run litellm.get_valid_models() for a list of available models based on your environment's set API keys.
Results are saved to --records-dir (default ./records, or $BRICKWRIGHT_RECORDS_DIR
if set).
Run brickwright generate --help for more options.
LEGO® is a trademark of the LEGO Group, which does not sponsor, authorize, or endorse this project.
Metadata
Release files for brickwright 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| brickwright-0.1.0.tar.gz | 73.4 kB | Without provenance | Details for brickwright-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| brickwright-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for brickwright-0.1.0-py3-none-any.whl |
Total release size: 161.0 kB
Release files / brickwright-0.1.0.tar.gz
| Download URL | brickwright-0.1.0.tar.gz |
|---|---|
| Size | 73.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
454c28ee5a855997769428d8600eff72aba9c5c1a1ba4b58163a0d0ba7e3baa7
|
|
BLAKE2b-256 checksum How to use checksums |
3a291d3de729a00a175ae934b57ae2961e1db45546cb391d31156cf3968680cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / brickwright-0.1.0-py3-none-any.whl
| Download URL | brickwright-0.1.0-py3-none-any.whl |
|---|---|
| Size | 87.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
95d53adde6743b295c54342674bb42e7bfe01fb996309fb8adf32e6f86e7316c
|
|
BLAKE2b-256 checksum How to use checksums |
eba69b12e38b83cc69e8bcf98d45a0c63f92e63a907e37e09aa771ecb4d92bd2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for brickwright 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
