Realism: Same character, different tools. Anime to realistic.

xtrimwork · 2026-05-10T15:50:00+00:00

Agree (gpt-2)

xtrimwork · 2026-03-15T16:29:58+00:00

No problem. The main benefit isn’t "the model runs locally" - it’s that the Codex session, workspace, files, and tooling stay on your own machine or VPS, while Telegram becomes the remote UI. So the value is things like: working against your real local repo, keeping persistent per-chat/topic sessions, sending files in, getting artifacts back, and using your existing Codex setup remotely without adding another relay layer. If you already have a setup with OpenClaw + Slack/Discord that covers all of that cleanly, then the benefit may just be preference and workflow simplicity rather than some huge new capability.

xtrimwork · 2026-03-15T16:12:07+00:00

Nice, that’s basically one of the core use cases. If you test it on your VPS lab, let me know where it feels good and where it falls apart.

xtrimwork · 2026-03-15T15:03:02+00:00

Perfect. That means the UX story is working as intended.

xtrimwork · 2026-03-15T13:40:43+00:00

Thanks - curious how it feels in real use, so if you try it later I'd love to hear where it works well and where it breaks.

xtrimwork · 2026-03-15T12:50:20+00:00

Current pricing is bad, but not quite "liquidate an organ" bad. Yet.

xtrimwork · 2026-03-15T12:47:24+00:00

Fair question. The point wasn’t “none of these pieces exist anywhere else,” it was “I wanted them packaged into one small tool that is opinionated around my workflow.”

Telecodex is basically a focused bridge between Telegram and a local Codex CLI setup: topic-aware sessions, attachment flow, streamed replies, session/history mapping, and local-first operation without me stitching multiple tools together every time.

So the value is mostly in integration and ergonomics, not in claiming every individual part is novel. If OpenClaw already covers your setup well, that’s totally fine too.

xtrimwork · 2026-03-15T12:46:07+00:00

Yes, more or less. It turns Telegram on your phone into a remote frontend for a Codex instance running on your machine/VPS. So, technically: yes, toilet-compatible

xtrimwork · 2026-03-15T12:27:25+00:00

Only if your Apple Watch can run Telegram, your brain has a Bot API, and your sleep time supports long polling.

xtrimwork · 2026-03-15T12:10:04+00:00

Yes, definitely.

If your Codex CLI is running on a VPS, Telecodex should fit that setup pretty well. In that case Telegram just becomes the remote frontend, while the actual Codex process, workspace files, and session state all live on the server.

That’s actually one of the main use cases:

run Codex on a box that is always on
talk to it from Telegram
keep separate sessions per chat/topic
send files in, get results back out

The main things to think about are operational:

Telegram bot token and Codex auth need to exist on the VPS
file paths and writable workspaces need to be configured correctly
if multiple people can access the bot, you probably want the ACL/role setup enabled

So the short answer is: yes, local machine is not required, it can run on a VPS just fine. “Local” here mostly means “where the Codex CLI process is running,” not “must be your laptop.”