The Codez stack is one system, but it is intentionally split into small layers. Use the lower layers alone when you only need local Codex-compatible execution; add the higher layers only when you need their job.
| Layer | Public surface | Responsibility | Dependency |
|---|---|---|---|
| Codez | Codex-compatible runtime | App Server v2, goal RPC, long-session hardening, prompt pruning, and plugin hooks | Does not require Teledex |
| RTK Codex Plugin | Optional Codex plugin | Shell/token safety through rtk rewrite and bounded output guarding |
Requires a Codex-compatible plugin-hook runtime; does not require Teledex |
| Pitlane Codex Plugin | Optional Codex plugin | Code-navigation/token-saving rewrites through a host-local pitlane CLI |
Requires a Codex-compatible plugin-hook runtime and local pitlane; does not require Teledex |
| Teledex | Telegram gateway/session layer | Topics, queues, live steer, /goal UX, and delivery/recovery around durable agent sessions |
Full mode is optimized for Codez App Server v2; upstream codex exec --json is legacy compatibility only |
Codez runs the agent. RTK makes risky shell output safer and smaller. Pitlane makes routine code browsing smaller by replacing safe source reads with indexed CLI calls. Teledex is the Telegram/session gateway that can drive a runtime, but it is not part of the Codez runtime itself.
Codez does not depend on Teledex. RTK and Pitlane do not depend on Teledex.
Teledex full mode is optimized for Codez App Server v2, including /goal,
typed thread RPC, stable gateway events, long-running session control, and
plugin-aware operation. Upstream codex exec --json remains a legacy
compatibility fallback, not the strategic gateway backend.
- Codez: public at https://github.com/Krablante/codez
- RTK Codex Plugin: public at https://github.com/Krablante/rtk-codex-plugin
- Pitlane Codex Plugin: public at https://github.com/Krablante/pitlane-codex-plugin
- Teledex: public at https://github.com/Krablante/teledex