DevAgentRadar → Repo Harness Rule Patch

Goal: update our repository's permanent harness instructions based on this release.

Update the file that tool actually reads. Do not dump everything into one file.

• Claude Code → CLAUDE.md plus .claude/ (skills, hooks, settings, agents, commands). It does not read AGENTS.md natively; start CLAUDE.md with @AGENTS.md.
• Codex, Copilot, Cursor, Factory Droid, Grok Build, Roo Code, Goose, OpenCode, Amp, Zed, Aider → AGENTS.md.
• Gemini CLI / Antigravity → GEMINI.md. AGENTS.md only if context.fileName is set.
• Cursor glob-scoped rules → .cursor/rules/*.mdc (plain .md is ignored), not a second constitution.
• Codex MCP → .codex/config.toml, not .mcp.json.
• Copilot extra instructions → .github/copilot-instructions.md; custom agents → .github/agents/.
• Windsurf → .windsurf/rules (do not assume AGENTS.md).
• Cline → .clinerules.
• Procedures → a skill (SKILL.md). Enforcement the model must not skip → a hook. Isolated roles → subagents.
• Do not fork the same rule into three tool files.

Context

Assistant: GitHub Copilot CLI Proposal: Place path-specific files in .github/instructions and keep Copilot CLI /sandbox session-only Summary: Copilot CLI v1.0.99-0 auto-applies path-specific files in .github/instructions, keeps /sandbox on for one session, auto-installs trusted repo plugins, renames the built-in browser plugin to browser-use, and opens a share menu via /share with no args. Primary source: https://github.com/github/copilot-cli/releases/tag/v1.0.99-0

Why it matters

GitHub Copilot CLI v1.0.99-0 now applies path-specific instruction files from the repository root .github/instructions when the agent reads or edits a matching file, so scoped guidance belongs in the repo instead of repeated in chat. /sandbox can keep sandboxing enabled for the current session without enabling it globally. The sandbox allows local network access by default so commands can reach localhost and private-network services, and sandboxed commands can write package and build caches when developer tool access is enabled. Trusted repository plugins install and update automatically before chat runs. The built-in browser plugin was renamed to browser-use, with existing browser plugin preferences still working after upgrade. Open /share with no arguments to view a full-screen action menu for sharing the current session. Where a list's structure is ambiguous, unscoped rules now prompt instead of being granted.

Suggested actions

1. Create path-specific instruction files in the repository root .github/instructions so Copilot CLI v1.0.99-0 applies them automatically when the agent reads or edits a matching file.
2. In GitHub Copilot CLI, run /sandbox and keep sandboxing enabled for this session only; do not enable it globally. Use it when commands need localhost or private-network access (allowed by default) or package/build cache writes with developer tool access enabled.
3. In GitHub Copilot CLI, run /share with no arguments to open the full-screen action menu and share the current session.
4. Rename Copilot CLI plugin config and skills that still point at the built-in browser plugin to browser-use. Leave existing browser plugin preferences in place so they keep working after upgrade to v1.0.99-0.
5. Commit trusted repository plugins so Copilot CLI installs and updates them automatically before chat runs. Scope permission-list rules so unscoped entries prompt instead of being granted when the list structure is ambiguous.

Config surfaces this release may change

• permission rules — check your repo before applying
• skills — check your repo before applying

After you finish

Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.

Tell the human: open https://devagentradar.com/proposals/github-copilot-cli-v1-0-99-0-place-path-specific-files-in-github-instruc and mark Applied, Skipped, or Failed. Proposal id: 2b77229b-656e-4604-9f9b-d76bb4e1acfc

Instructions:

1. Read the existing context files and settings for the tools in this repo.
2. Draft an explicit Git diff. Update ONLY agent harness rules or tool configuration.
3. Call out deprecated flags, obsolete habits, or changed permission boundaries.
4. Do not touch application logic.

Start with the proposed diff and say which layer and which tool's file it belongs in.