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: Tabnine Proposal: Upgrade Tabnine to 6.5.3 and add organization-level repositories Summary: Upgrade to Tabnine 6.5.3 so admins can add organization-level repositories regardless of selected team, per-team model assignments apply correctly, and Plan Mode can save plan files. Roll Engine 4.340.0, IDE plugins, and Tabnine-CLI 0.34.0. Primary source: https://docs.tabnine.com/main/administering-tabnine/release-notes#v6-5-3

Why it matters

Tabnine 6.5.3 (17 Aug 2026) lets administrators add repositories at the organization level no matter which team is selected. That matches 6.5.0 indexing of organization-level sources once per organization instead of once per team, so shared code should be attached at org scope rather than duplicated per team. The same release fixes team-specific model assignment so per-team model settings actually apply, and restores Plan Mode saving of plan files. Pin plugins to Engine 4.340.0, VS Code & Cursor 3.362.0, JetBrains 1.318.1, Eclipse 1.190.2, Visual Studio 2022 & 2026 1.298.17, Tabnine-CLI 0.34.0, and Tabnine Skills 0.1.4. WebStorm 2026.2 and other JetBrains IDEs on build 262 also need this line to avoid the 6.5.2 startup crash.

Suggested actions

1. Upgrade Tabnine to v6.5.3 with these plugin versions: Engine 4.340.0, Visual Studio Code & Cursor 3.362.0, JetBrains IDEs 1.318.1, Eclipse 1.190.2, Visual Studio 2022 & 2026 1.298.17, Tabnine-CLI 0.34.0, Tabnine Skills 0.1.4.
2. In Tabnine admin, add each shared repository at the organization level regardless of which team is currently selected; do not attach it only to the selected team.
3. In Tabnine admin, open each team and re-save its model assignment so per-team model settings apply correctly after the 6.5.3 fix.
4. In Tabnine Plan Mode, save the plan file for every in-progress plan that previously failed to persist.
5. On WebStorm 2026.2 and other JetBrains IDEs based on build 262, confirm Tabnine JetBrains plugin 1.318.1 is installed so the 6.5.2 startup crash is resolved.

Config surfaces this release may change

• permission rules — check your repo before applying
• MCP servers — 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/tabnine-v6-5-3-upgrade-tabnine-to-6-5-3-and-add-organization-level-repos and mark Applied, Skipped, or Failed. Proposal id: 8880df23-0af8-4ab3-bbd2-77e2552f78e9

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.