Telegram Bridges for Gemini CLI and Codex After Hitting Claude Code Limits
Claude Code usage limits forced me into an annoying realization: the thing I had become dependent on was not just the model. It was the workflow. Once you get used to sending work to an agent from ...

Source: DEV Community
Claude Code usage limits forced me into an annoying realization: the thing I had become dependent on was not just the model. It was the workflow. Once you get used to sending work to an agent from your phone, waiting for the reply, then sending the next step while you are away from your desk, normal terminal-only usage starts to feel primitive. So instead of waiting for official remote workflows to improve, I built a small Telegram bridge for two tools I already had locally: Gemini CLI Codex This is not a polished platform. It is a local-first workaround. But it brought back the async loop I actually cared about. The problem was not "which model" Claude Code Channels changed how I work on side projects. I could be in a cafe, walking outside, or traveling, and still move a repo forward from Telegram. That changes the whole shape of development. You stop thinking "I need to sit down and code now" and start thinking "I can send the next instruction right now and review the result later."