Skip to content

Root AGENTS.md tells host-side coding agents they're running in an exe.dev VM #5

Description

@Guria

The repo ships AGENTS.md at the root:

You are running in an exe.dev VM.

https://exe.dev/docs/proxy.md has details about the exe.dev HTTPS proxy.

Only use documented exe.dev features (see https://exe.dev/docs.md). Undocumented local endpoints are internal infrastructure—unstable and unsupported.

Those instructions are meant for agents inside the built image. The Dockerfile (line 305) copies the file to ~/.config/shelley/AGENTS.md and symlinks it into ~/.claude/CLAUDE.md, ~/.codex/AGENTS.md, ~/.config/opencode/AGENTS.md, and ~/.pi/AGENTS.md. That part works.

The problem: Codex, OpenCode, and Pi auto-discover an AGENTS.md at the repo root and load it as project instructions (Claude Code reads only CLAUDE.md and picks this file up solely via an explicit import or symlink). Clone exeuntu, open any of those three in the checkout on a laptop, and the agent believes it runs in an exe.dev VM. In my case a pi session working on a host checkout started obeying exe.dev proxy rules with no proxy present and treated local endpoints as off-limits "internal infrastructure".

Fix: rename the root file to a name no harness auto-discovers (exeuntu-agents.md) and point the COPY at it. In-image behavior is unchanged, since the file still lands at ~/.config/shelley/AGENTS.md under the original name and the symlinks follow. Done in my fork: Guria/misexeuntu@dc9158e.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions