Home

box-memory-onprem — wiki

The air-gapped variant of mrdulasolutions/BOX. Skills write only to the local Box Drive desktop-app mount; zero outbound calls to Box during skill execution. Box Drive (a Box-attested product) handles compliant sync to Box cloud.

For HIPAA / FedRAMP / DoD IL4 / ITAR data paths where the agent runtime cannot make outbound calls to Box's API.

Where to go

If you want to…	Read
Understand why this exists	Architecture
Get from zero to a working air-gapped workspace	Quick Start
Install it	Installation
Know which compliance regime fits which deployment	Compliance by Deployment
Verify your trust posture explicitly	Air-Gap Trust Model
Pick an LLM that matches your regulatory regime	Supported LLM Configurations
Set up Box Drive locally	Box Drive Setup
Understand the 5-layer supply-chain hygiene	Security Layers
Become the Designated Security Reviewer	Designated Security Reviewer
See what skill does what	Skills Reference
See the workspace schema	Schema
Find Box Drive paths per OS	Box Drive Paths
Debug known quirks	Operational Notes
Search the FAQ	FAQ
Diagnose a problem	Troubleshooting
See what changed	Changelog

At a glance

• 9 skills, all FS-only — box-drive-detect, box-airgap-status, box-init, box-write, box-recall, box-companion, box-team, box-status, box-index-rebuild
• Zero outbound network calls to Box during skill execution. Enforced by static analysis (CI scans for mcp__, api.box.com, etc.) and by what code physically ships
• Plugin zip: ~28 KB compressed. Matches Anthropic's working Cowork plugin shape
• Schema pinned to a specific commit of the cloud repo via .schema-pin — single source of truth
• 5-layer supply-chain hygiene: pre-commit hook, GitHub Actions CI, SHA256 published per release, audit log per release, quarterly designated security reviewer

When NOT to use this

If you want Box AI features (Ask, Extract, AI Studio, Hubs Q&A), or if you don't need a structural air-gap claim — use the cloud variant instead: mrdulasolutions/BOX.

Both can be installed together. They have separate plugin namespaces (box-memory-onprem: vs box-memory:) and don't conflict. Use the appropriate one per workflow.

Repo links

• Latest release: https://github.com/mrdulasolutions/BOX-Onprem/releases/latest
• Issues: https://github.com/mrdulasolutions/BOX-Onprem/issues
• Cloud variant: https://github.com/mrdulasolutions/BOX
• Cloud wiki: https://github.com/mrdulasolutions/BOX/wiki

License

MIT