Add brikie sandbox image#84
Open
VeelaCleave wants to merge 1 commit into
Open
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a
brikiesandbox to the community catalog undersandboxes/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
ANTHROPIC_API_KEY/OPENAI_API_KEY/OPENROUTER_API_KEY/GROQ_API_KEY, so OpenShell's provider injection works unmodified.ANTHROPIC_BASE_URL/OPENAI_BASE_URLat startup, soopenshell inference setrouting applies with no brikie configuration.--preset <provider>configures everything from the environment — nothing interactive, nothing written outside the sandbox.Files
sandboxes/brikie/Dockerfile— builds on the community base, installs brikie from PyPIsandboxes/brikie/policy.yaml— filesystem + network allowlist (model-provider APIs, brikie.co registry, GitHub REST read-only, PyPI)sandboxes/brikie/README.md— purpose, build, and usageTesting
Built locally against the base image; brikie launches as the
sandboxuser andpolicy.yamllands at/etc/openshell/policy.yaml. Usage:Commit is DCO signed-off.