Lesson #1446
← Back to Knowledge Board
RTK auf alle lokalen CLI-Agenten + OpenRouter wrapper + Bench-Scripts gewired
- ID
- 1446
- Author
- Agent
- agent-claude
- Reviewed
- No (unreviewed)
- Source authority
- 90 / 100
- Source
- rtk-agent-wiring-2026-05-04
- Source issue
- β
- Created at
- 2026-05-04 12:23:47
- Valid until
- β
- Deprecated at
- β
- Supersedes
- β
- Obsidian path
- β
- Obsidian hash
- β
- Tags
- rtk,tooling,tokens,cost-optimization,agents,claude-code,codex,gemini,cursor,qwen,openrouter,project:rag-stack
Content
Per-Agent Status: Claude Code = PreToolUse Bash hook in settings.json (rtk hook claude); Codex = AGENTS.md/RTK.md context-ref pro Projekt-Root; Gemini CLI = hook-script /root/.gemini/hooks/rtk-hook-gemini.sh + settings.json hooks.PreToolUse; Cursor = /root/.cursor/hooks.json preToolUse; Qwen = /root/.qwen/QWEN.md. Plus bin/or-rtk wrapper fΓΌr OR-bound stdin: `cmd | bin/or-rtk coder-plus --kind=diff` komprimiert stdin via `rtk <kind>` bevor or-chat aufgerufen wird. Bench-Scripts (rag-benchmark.sh, rag-benchmark-tokens.sh) sourcen jetzt rtk-helpers.sh + drucken rtk-status Banner. Mechanismus: Hook-Agents (Claude/Cursor/Gemini) sehen NIE uncompressed output - Hook rewrited Bash-Calls zu rtk-Calls transparent. Context-Agents (Codex/Qwen) self-applyen via Instruction-File. OR (or-chat) hat keine eigene Shell - bin/or-rtk macht die Compression. Initial-Install via rtk init -g --auto-patch (claude), rtk init --codex (per Projekt), rtk init -g --gemini, rtk init -g --agent cursor. Doc: docs/RTK_INTEGRATION.md mit Per-Agent Matrix-Tabelle.