brikie is a modular agent harness where every capability is an
optional, hot-swappable Brick. The sandbox installs brikie from PyPI on
top of the community base image and ships a policy.yaml permitting the
common model-provider APIs, the brikie.co brick registry, the GitHub
REST API (read-only), and PyPI.
brikie reads provider credentials from the environment and honors
ANTHROPIC_BASE_URL / OPENAI_BASE_URL, so OpenShell's managed credential
injection and inference rerouting work without extra configuration.
Tested locally: image builds cleanly against the base, brikie launches
as the sandbox user, and policy.yaml lands at /etc/openshell/policy.yaml.
Signed-off-by: VeelaCleave <veelacleave@gmail.com>
What
Adds a brikie sandbox to the community catalog under sandboxes/brikie/.
brikie is a modular agent harness where every capability is an optional, hot-swappable Brick — users compose an agent (interface + provider + tools/memory/security/orchestration) from a brick catalog. It's on PyPI (pip install brikie) and has a public brick registry at brikie.co.
Why it fits OpenShell
Files
Testing
Built locally against the base image; brikie launches as the sandbox user and policy.yaml lands at /etc/openshell/policy.yaml. Usage:
Commit is DCO signed-off.