CTO Telegram Dispatcher Primer
Start local Codex work from your phone.
The dispatcher is a bridge between Telegram and local Codex running on the ThinkBook. Use it when you want to queue a Codex assessment or handoff without opening the laptop.
Ask for analysis
/cto assess <what you want checked>Ask for Codex handoff
/cto handoff <what Codex should pick up> --for codexPlain English
Text the dispatcher bot. The website files the request. The ThinkBook dispatcher notices it. Local Codex runs the work. You get a short Telegram summary back.
How The Loop Works
/cto command from your phone.
codex exec with the handoff prompt.
Use assess When
You want Codex to inspect, diagnose, compare options, or tell you what is true before changing anything.
Health check
/cto assess verify production health and dispatcher statusBug diagnosis
/cto assess why Telegram CTO commands repeated replies todayPlanning first
/cto assess dark mode implementation plan for D:\ria-marketing-pageUse handoff When
You want Codex to pick up a concrete task. Include the repo path, expected behavior, and verification target.
Codex-owned repo
/cto handoff diagnose and fix the CTO health page failing in D:\dvo88\dvo88-command-center --for codexCross-repo assist
/cto handoff in D:\ria-marketing-page, assess and implement dark mode if safe; preserve the brand system; verify locally before reporting back --for codexDecision Table
| Situation | Use | Why |
|---|---|---|
| You are not sure what is wrong. | /cto assess ... |
Gets a diagnosis before any fix. |
| You know the task and want Codex to act. | /cto handoff ... --for codex |
Creates a direct local Codex handoff. |
| The task is in RIA Builder, marketing, or another non-dvo88 repo. | Usually start with assess. |
Codex can assist, but the agent split normally assigns RIA surfaces to Claude. |
You see old documentation or muscle memory for /codex. |
/codex still works as a compatibility alias. |
Use /cto going forward so the command matches CTO's production intake surface. |
| You want a simple bot response like echo, reminder, or casual chat. | Do not use the dispatcher. | The dispatcher is not a general chat bot. It only understands assess and handoff. |
What Good Looks Like
- Telegram immediately replies that the Codex report was queued.
- The reply includes a report id.
- The local dispatcher claims the report on the ThinkBook.
- Codex runs the request.
- You receive a completion summary in Telegram.
What Not To Send
These are valid Telegram messages, but they are not valid dispatcher commands.
/cto echo hello
/cto remind me tomorrow
/cto do this thing
/ria handoff anythingIf you use an unsupported action, the bot should reply once with guidance. Repeated replies mean the webhook retry path needs attention.
Good Command Writing
- Be concrete. Name the repo, feature, error, or production URL when you know it.
- Choose the right verb. Use
assessfor diagnosis andhandofffor action. - Say what to preserve. For design work, mention the brand system or existing layout if it matters.
- Say how to verify. Ask for local checks, production health checks, or Telegram confirmation when relevant.
- Keep secrets out. Do not paste tokens, private keys, or passwords into Telegram commands.
Copyable Templates
General diagnosis
/cto assess <problem or question>Production check
/cto assess verify <site or feature> in production and report the current stateCodex implementation handoff
/cto handoff in <repo path>, implement <specific change>; preserve <important behavior>; verify <checks> --for codexSafer first step for another agent's lane
/cto assess implementation plan for <task> in <repo path>; note which agent should own it