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: Zed AI Proposal: Upgrade Zed to v1.25.2 and select Claude Opus 5.5 on Bedrock Summary: Zed v1.25.2 ships ACP context compaction and session notices for external agents, GPT-6 Astra / Claude Fable 5.1 / Claude Opus 5.5 on Amazon Bedrock, double-click inlay-hint edits, and a fix so remote MCP/agent env secrets no longer appear in the local process list. Primary source: https://github.com/zed-industries/zed/releases/tag/v1.25.2

Why it matters

v1.25.2 changes long-running external-agent work in Zed: ACP agents now get context compaction and session notices, first updates in a new thread are no longer dropped, prompts are not stalled by unneeded Git checkpoints, and Gemini no longer errors after a tool call returns an image. Amazon Bedrock now exposes GPT-6 Astra, Claude Fable 5.1, and Claude Opus 5.5, so threads should target those IDs instead of older Bedrock models. Inlay hints that include text edits can be applied by double-click or editor: accept inlay hint, so stop retyping LSP insertions. Anyone who used remote projects must upgrade: environment variables, including secrets, passed to external agents and MCP servers were visible in the local process list. After upgrading, rotate those secrets and reconnect. Smaller binaries (~33% macOS, 28% Windows, 7% Linux) and SSH setup in one probe instead of three cut friction for remote agent sessions.

Suggested actions

1. Upgrade Zed to v1.25.2 from https://github.com/zed-industries/zed/releases/tag/v1.25.2 so ACP external agents get context compaction and session notices, remote MCP/agent env vars are no longer visible in the local process list, and binaries shrink ~33% (macOS) / 28% (Windows) / 7% (Linux).
2. In Zed, open an agent thread on the Amazon Bedrock provider and select Claude Opus 5.5 (also now listed: GPT-6 Astra, Claude Fable 5.1).
3. If this machine ran Zed remote projects with MCP servers or external agents before v1.25.2, rotate every secret previously passed as an environment variable to those processes, then reconnect the remote project on v1.25.2.
4. When an inlay hint offers a text edit, double-click the hint or place the cursor on it and run editor: accept inlay hint instead of typing the insertion.
5. Keep a long ACP external-agent thread open past the old context limit and use the new session notices; do not start a fresh thread just to avoid dropped first updates or hung prompts from Git checkpoints.

Config surfaces this release may change

• context and compaction settings — check your repo before applying
• MCP servers — check your repo before applying
• settings files — check your repo before applying
• background and headless runs — 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/zed-ai-v1-25-2-upgrade-zed-to-v1-25-2-and-select-claude-opus-5-5-on-bedr and mark Applied, Skipped, or Failed. Proposal id: 45290710-e766-4438-8dd7-c35876f8849e

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.