RTK Codex Plugin is an optional edge component in the Codez ecosystem. It owns shell request classification and model-visible output budgeting; it does not own the runtime, gateway, or indexed navigation service.
flowchart TB
accTitle: RTK Codex Plugin ecosystem position
accDescr: Codez can load RTK and Pitlane as optional local plugins. Teledex may drive Codez as an external gateway. RTK has no dependency on the gateway or the Pitlane plugin.
Teledex["Teledex<br/>optional gateway"] -. "JSON-RPC client" .-> Codez["Codez<br/>agent runtime"]
RTK["RTK Codex Plugin<br/>rewrite and output budgets"] -. "optional hooks" .-> Codez
Pitlane["Pitlane Codex Plugin<br/>indexed navigation rewrites"] -. "optional hooks" .-> Codez
RTK -. "optional local executable contract" .-> RTKCLI["rtk CLI"]
| Project | Owns | Does not own |
|---|---|---|
| Codez | Agent runtime, tool policy, App Server, plugin execution | RTK-specific classification or gateway delivery |
| RTK Codex Plugin | Optional command rewrite adapter, bounded inspection wrapper, PostToolUse output budgets | Sandboxing, approvals, sessions, Telegram delivery, or RTK distribution |
| Pitlane Codex Plugin | Optional indexed source-navigation rewrites | General output budgeting or runtime policy |
| Teledex | Telegram transport, session routing, queueing, and recovery | Runtime command policy or plugin implementation |
- RTK Codex Plugin requires only a compatible hook runtime and Python 3.11+ on POSIX.
- Codez does not require RTK.
- RTK does not require Pitlane or Teledex.
- Teledex may provision plugins for workers, but gateway operation remains outside this repository.
- The optional
rtkexecutable is a separate local dependency resolved fromPATH.
When both RTK and Pitlane are enabled, loading RTK before Pitlane is the recommended integration order:
- RTK handles its general command and output-budget responsibilities.
- Pitlane may claim the narrow indexed-navigation forms it recognizes.
RTK classifier tests preserve documented Pitlane-owned navigation shapes, but this repository does not contain a cross-plugin end-to-end test. Treat the ordering as an integration recommendation, then verify it against the exact plugin releases installed.
Every enabled hook is trusted local code. Plugins can inspect or alter tool input and output, but they do not replace Codez approvals, sandboxing, or host access control. See Security.