My coding agent wrote outside the repo. Nothing stopped it.

A .NET 10 framework called Orkeon addresses a real risk in coding agents: an agent's write tool can call File.WriteAllText on any path the model produces, and a system-prompt instruction to 'stay in the repo' is not an enforceable boundary. Orkeon enforces filesystem access through virtual paths and a mount table (physical:virtual:rights syntax), refusing writes outside declared mounts before any disk write occurs. A Roslyn analyzer (Orkeon.Compliance.Vfs, shippable standalone) turns any direct System.IO call in annotated projects into a compiler error, closing the loophole where a tool or loader could bypass the mount table. The framework also adds execution budgets for autonomous agents (tool calls, delegation depth, wall time, tokens, spawned agents), a read-only shell allowlist, circuit breakers for graph-orchestration cycles, and supply-chain attestation (GitHub attestation, SBOM, Trusted Publishing) for its NuGet packages. At 1.0.0-rc.4 it ships 16 LLM providers, 79 tools, 6 orchestration modes, and a forge CLI that generates and sandbox-tests agent crews from a natural-language description, but is .NET 10 only, unproven in production, and maintained by a single person.

Source: https://goatreview.com/my-coding-agent-wrote-outside-the-repo-nothing-stopped-it. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.