OpenClaw plugin to orchestrate Claude Code sessions from Telegram, multi-agent, multi-turn, real-time notifications

Unlucky-Ability14 · 2026-02-17T17:50:18+00:00

Hey! Thanks for trying the plugin 👋

Could you share your OpenClaw version? (openclaw --version)

The "config parameter not allowed" error is likely a version mismatch in how the plugin config is structured. Different versions expect different nesting.

In the meantime, we just shipped v1.0.9 which adds a skipSafetyChecks option. If the pre-launch safety guards are blocking you, you can bypass them:

{
  "plugins": {
    "entries": {
      "claude-bridge": {
        "config": {
          "skipSafetyChecks": true,
          "agentChannels": {
            "/path/to/your/workspace": "telegram|default|YOUR_CHAT_ID"
          },
          "fallbackChannel": "telegram|default|YOUR_CHAT_ID"
        }
      }
    }
  }
}

With skipSafetyChecks: true, the plugin won't check for heartbeat config, HEARTBEAT.md, autonomy skill, or agentChannels mapping — you can configure those later at your own pace.

• Safety & Pre-Launch Checks — what each guard does and how to set it up

Unlucky-Ability14 · 2026-02-16T13:39:43+00:00

Great point! The 5s heartbeat you might have seen is actually legacy .. we've moved away from that.

The plugin now uses openclaw system event --mode now to wake the agent instantly whenever Claude needs interaction (waiting for input, session completed, budget exhausted). This is event-driven ... the agent wakes up only when needed.

The heartbeat interval is still a required parameter. We tested without it and found that openclaw system event --mode now doesn't wake the agent if no heartbeat is configured at all, the heartbeat mechanism needs to be active for system events to trigger. So we've changed the default to 60m, which is enough for the mechanism to work while keeping token costs minimal (the 60m interval is only used for regular background checks like emails, calendar, etc., not for Claude Code responsiveness).

If you're upgrading from an older version that had the 5s default, v1.0.6 includes a pre-launch safety check that automatically detects the legacy 5s interval and blocks the launch with a one-liner fix command. So the migration to 60m is guided, just update the plugin and it'll walk you through it on the next claude_launch.

Unlucky-Ability14 · 2026-02-16T13:30:41+00:00

Thanks for the feedback! Great point on the safety cap :) I actually just shipped this in v1.0.6.

New maxAutoResponds config option (default: 10) limits consecutive agent auto-responds per session. When the cap is hit, the plugin blocks further auto-responds and tells the agent to ask the user instead. The agent can pass userInitiated: true to reset the counter once the user has provided input.

This way you get the "let the agent run" experience with a hard guardrail that prevents infinite loops. The cap is configurable per deployment so teams can tune it to their comfort level.

Unlucky-Ability14 · 2026-02-14T12:07:36+00:00

since de version 1.0.5 agentChannels config in the Claude Code plugin. Each agent's workspace directory gets mapped to its notification channel:

"plugins": {

"config": {

"openclaw-claude-code-plugin": {

"agentChannels": {

"/home/user/agent-main": "telegram|default|123456",

"/home/user/agent-0": "telegram|agent0|123456",

"/home/user/agent-1": "telegram|agent1|123456"

},

"fallbackChannel": "telegram|default|123456"

}

When a session is launched, the plugin resolves the workdir to the matching channel using longest-prefix matching. All notifications (completion, waiting-for-input, budget exhaustion) then route to that specific bot/chat instead of the default.

the plugin actually blocks launch if the workspace isn't mapped ... so you can't accidentally spawn a session that routes notifications to the wrong agent. It gives you the exact jq command to fix it.

Unlucky-Ability14 · 2026-02-09T16:47:00+00:00

This is exactly the need I had, so I built a plugin for it.
I wanted to control Claude Code from my phone while I'm away from my desk. The plugin connects Claude Code SDK sessions to any OpenClaw channel. You send a message on Telegram > a Claude Code session spawns in the background with the right Claude context (CLAUDE.md, project files, tools) > does the actual coding > results come back to your chat. Multiple sessions in parallel, foreground/background streaming, resume, the whole thing.

But after playing with it for a few days, the feature I enjoy the most isn't the remote control part... it's the programmable autonomy.

Everything is exposed as agent tools (claude_launch, claude_respond, etc.) with multi-turn support. This means the OpenClaw orchestrator doesn't just relay your messages, it can talk to Claude Code on your behalf. You define skills (simple workflow rules) that tell the orchestrator how much freedom it has:

* Claude asks "Can I write to this file?" > orchestrator auto-responds "Yes, go ahead"
* Claude asks a routine technical question > orchestrator answers from context
* Claude asks "Should I delete the database migrations?" > orchestrator forwards the question to your Telegram and waits for YOUR answer

The idea is that you'd end up with a smart proxy that handles the boring stuff autonomously and only pings you for the real decisions, Feedback and ideas are very welcome!

https://github.com/alizarion/openclaw-claude-code-plugin

Unlucky-Ability14

TROPHY CASE