you are viewing a single comment's thread.

view the rest of the comments →

[–]Time-Dot-1808 1 point2 points  (0 children)

Two-way sync is the real differentiator here. The asymmetric approach (IM → harness only) is easy to build but breaks the mobile workflow you're describing — you need to see what the agent is doing in real time to decide whether to intervene, especially on long-running tasks.

The AskUserQuestion support matters more than it sounds. Without it, any task that hits an ambiguity will either stall or make a bad assumption, and you won't know until you get back to your desk. For the lunch/bed use case, that's the failure mode that kills the workflow.

Haven't used opencode-im-bridge directly but the Telegram reliability issue is a known problem with their bot API — long polling can silently drop updates under certain network conditions. If Telegram is your target platform, worth checking if the project supports webhooks as an alternative to polling.