Local Filesystem Access

Purpose

This document defines how Codex, ChatGPT, and MCP-compatible AI clients may access the local Streetline Heroes repository.

Current Codex Access

Codex already has controlled workspace access to this repository:

C:\Users\ramon\RMediaIT\game\StreetlineHeroes

No separate filesystem MCP server is required for this Codex app workspace.

ChatGPT Without Local Filesystem Access

If ChatGPT or another assistant cannot directly read the repository, use:

• studio/CHATGPT_CONTEXT.md
• studio/AI_START_HERE.md
• Specific repository files requested by the assistant

The assistant must not invent status, requirements, blockers, or approval state.

Optional MCP Filesystem Configuration

Only use this with a client that explicitly supports local MCP servers.

{

  "mcpServers": {

    "filesystem": {

      "command": "npx",

      "args": [

        "-y",

        "@modelcontextprotocol/server-filesystem",

        "C:\\Users\\ramon\\RMediaIT\\game\\StreetlineHeroes"

      ]

    }

  }

}

Security Rules

• Allow only C:\Users\ramon\RMediaIT\game\StreetlineHeroes.
• Never expose C:\Users\ramon, Downloads, Documents, Desktop, or an entire drive.
• Prefer read-only access when the client supports it.
• AI may only edit files after an explicit user request.
• Run pnpm validate and relevant validators after repository edits.
• Do not use MCP filesystem access for secrets, private documents, or unrelated projects.

Acceptance Criteria

• New AI sessions start at studio/AI_START_HERE.md.
• External ChatGPT sessions without filesystem access use studio/CHATGPT_CONTEXT.md.
• Codex continues using the existing workspace sandbox.
• MCP filesystem access is only configured for clients that support local MCP servers.