CAIN-42 CAIN StudioAGENTIC AI 75 · #62
Local AI coding on personal computers
Microsoft presented a coding model intended to run directly on PCs.
Last reviewed 2026-11-11
Agentic AI 75 / #62
2026 status: Reported model and hardware announcement · Category: Developer tooling
The 2026 development
Microsoft presented a coding model intended to run directly on PCs.
The governance gap
Local execution reduces data exposure but not action risk. A local agent still writes files, runs builds and can reach the network, and the user may have less monitoring than a server deployment.
Where CAIN-42 fits: Moat 6 — Adversarial Trust Engine
Core question: Can CAIN break its own guarantees? Continuous attack, mutation and red-team testing of the controls themselves.
Apply the same guard locally: a scoped sandbox, an allowlist of tools, no inherited secrets, and a signed local record. Local is a deployment mode, not a trust exemption.
How the wiring works
- Run the model and tools in a local sandbox.
- Restrict filesystem and network access to the task.
- Keep secrets out of the model context.
- Write a local signed record of the run.
What is real today
LIBRARY Production code and tests exist in this repository; there is no hosted route for this exact use.
The sandbox and guard are real on this host. No Microsoft model or PC hardware is involved.
| Component in this repository | What the module says it is |
|---|---|
cain/isolation/sandbox.py | Hardened Execution Isolation Fabric — Evolution 6: Project Sovereign Isolation. |
keystone/guard.py | Fix-safety checks: the fix may repair the defect, but it may not break the code around it. |
keystone/sandbox.py | Run a module's tests inside a bubblewrap sandbox: no network, read-only system, only its own files, time-boxed. |
cain/landlock_sandbox.py | Landlock filesystem (and optional TCP) restriction for processes CAIN launches -- Sovereign Evolution 3. |
Descriptions are the first line of each module's own docstring, read without importing it. A module path is a pointer into this repository, not a hosted endpoint. Its existence is checked by the test suite; its status for this use is the label above.
Check it yourself
- Run the live IDE-diff gate
/vibeguard-keystone - Fire a live decision through the CAIN-42 pipeline
/fabric/try— the same enforcement path every product sits behind.
Commercial package
| Offer | Local Agent Containment Review |
|---|---|
| Buyer | Developer-tool vendors and enterprise IT |
| Price (proposal) | $3,500–$7,500 per review |
| Bundle | Code & Proof — Prove the fix, not just the diff. |
| Operator stream | Stream 2 of the 10-stream operator playbook |
Platform engineering, AI coding-tool vendors, security engineering is the bundle buyer. The entry offer for this bundle is Fabrication audit or long-run engineering attestation; the range is $1,500–$6,000 per audit; $2,500–$4,000/month retainer. A price on this page is a proposal, not a validated rate, and no customer is claimed.
Buy this as a product or service
CAIN-A75-062 — Local Agent Containment Review PILOT
A bounded pilot report: up to five scenarios, the relevant library engine or analysis, a written result and the stated limits. Engineering time is quoted per pilot.
Kind: Assessment · Price (proposal): $3,500–$7,500 per review · Lead time: 10 business days.
Open the product page · all 75 products
What this page does not claim
What this page is not. CAIN-42 is not affiliated with, endorsed by, integrated into, or shipped with the organisation named in the 2026 item. The item is public context; the page describes how CAIN-42 would govern that class of capability. No page here claims a customer, a partnership, a certification, a patent, or a production integration. Prices are proposals. Built by a three-person team.