feat(providers): add Enclawed agent provider#1689
Closed
enclawed wants to merge 1 commit into
Closed
Conversation
Enclawed (https://enclawed.com/, source at github.com/enclawed/enclawed-oss) is a classification-gated AI agent gateway with an MCP-attested transport layer. It composes with OpenShell as an agent provider in the same shape as Claude Code, Codex, Copilot, and OpenCode. Unlike those, Enclawed bootstraps every credential into the operator's OS keyring at install time (libsecret / Keychain / Credential Manager) and reads none from the environment, so the provider has nothing to discover at provider-discovery time. The matching sandbox image (github.com/enclawed/openshell-enclawed-sandbox) runs Enclawed's installer at first boot to populate the keyring. Modeled on GenericProvider for the zero-credential case. Network policy declares the two default backends Enclawed ships with: api.anthropic.com (codex / pi-coding-agent path) and 127.0.0.1:11434 (local Ollama; secretary path with qwen2.5:32b-instruct). Operators using a different LLM backend extend the allowlist in their sandbox config rather than here. Changes: - providers/enclawed.yaml: declarative provider spec. - crates/openshell-providers/src/providers/enclawed.rs: ProviderPlugin impl with empty discovery + a smoke test. - crates/openshell-providers/src/providers/mod.rs: module entry. - crates/openshell-providers/src/lib.rs: registry entry. - README.md: Supported Agents table row pointing at the partner sandbox repo (enclawed/openshell-enclawed-sandbox). Signed-off-by: Alfredo Metere <alfredo.metere@metereconsulting.com>
|
Thank you for your interest in contributing to OpenShell, @enclawed. This project uses a vouch system for first-time contributors. Before submitting a pull request, you need to be vouched by a maintainer. To get vouched:
See CONTRIBUTING.md for details. |
|
Thank you for your submission! We ask that you sign our Developer Certificate of Origin before we can accept your contribution. You can sign the DCO by adding a comment below using this text: I have read the DCO document and I hereby sign the DCO. You can retrigger this bot by commenting recheck in this Pull Request. Posted by the DCO Assistant Lite bot. |
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
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.
Summary
Adds Enclawed as an agent provider, in the same shape as Claude Code, Codex, Copilot, OpenCode. The actual sandbox image lives in a partner-owned external repo (
enclawed/openshell-enclawed-sandbox) per the OpenClaw / NemoClaw pattern; this PR is only the OpenShell-side plumbing.What's Enclawed?
A classification-gated AI agent gateway with an MCP-attested transport layer (see arXiv:2605.24248, source at github.com/enclawed/enclawed-oss). It composes admission control + tool-level authorization + a hash-chained audit log around standard MCP servers. The bundled
secretaryandcodexapps run on top.Why zero-credential discovery
Unlike the env-var-discovered providers, Enclawed bootstraps every credential into the operator's OS keyring at install time (libsecret on Linux, Keychain on macOS, Credential Manager on Windows) and reads none from the environment. The provider plugin has nothing to discover at provider-discovery time — modeled on
GenericProviderfor that reason. The matching sandbox image runs Enclawed's installer at first boot to populate the keyring inside the sandbox.Changes
providers/enclawed.yaml— declarative provider spec,category: agent,credentials: []. Endpoints declare the two backends Enclawed ships with:api.anthropic.com(codex / pi-coding-agent path) and127.0.0.1:11434(local Ollama; secretary path).crates/openshell-providers/src/providers/enclawed.rs—ProviderPluginimpl with empty discovery + smoke test.crates/openshell-providers/src/providers/mod.rs— module entry.crates/openshell-providers/src/lib.rs— registry entry.README.md— Supported Agents table row pointing at the partner sandbox repo.Test plan
mise run ci(lint + compile + tests) passescargo test -p openshell-providersincludesenclawed_provider_discovery_is_empty_by_defaultopenshell provider create --type enclawedsucceeds with no env credentials presentenclawed/openshell-enclawed-sandbox) public and reachable from the README linkDCO signed-off-by Alfredo Metere. Commit is SSH-signed.