Sign inGet started
Paper · arXiv

The Compiler May Read It, the Agent May Not: Keeping Part of a Research Code Away from a Coding Agent

The compiler must read modules a physics-based solver cannot build without; the coding agent must not read that intellectual property. The harness, the software around the model that executes its tool calls, does not ship that rule. We classified fifteen read routes against a container, permission rules and a sandbox. None of the three can tell which program is reading.

AuthorsShobhan Roy
Primary categorycs.CR
Published28 September 2026
Last updated at source12 October 2026
cs.CRcs.AIcs.SE
Embed this entry
<iframe src="https://silytics.si/embed/item/d47c158c-7f47-4453-9537-da5d6c31d788" width="420" height="190" style="border:0" loading="lazy" title="Silytics entry"></iframe>

Free, no tracking. More about feeds and embeds.

Silytics shows public metadata from arXiv and links to the original. Information may be incomplete or out of date. Last refreshed 17 October 2026. Licenses and terms of the original apply to the work itself. Not financial, legal or professional advice.