Zulip: add channel plugin by jamie-dit · Pull Request #9643 · openclaw/openclaw

jamie-dit · 2026-02-05T14:22:36Z

Adds Zulip as a channel plugin (streams/topics) under extensions/zulip.

Key behavior:

Monitors a configured stream allowlist and replies in the same stream/topic.
Default outbound topic is general chat when a target omits the topic.
Topics map to OpenClaw sessions (same stream + same topic → same session).
Reaction indicators on the triggering message while responding (configurable):
- Start: eyes
- Success: check
- Failure: warning

Config/targets:

Config lives under channels.zulip (supports accounts.* like other plugins).
Outbound target format: stream:<streamName>#<topic?>.

Scope / limitations:

MVP: stream messages only (no DMs; no attachments).

Implementation notes:

Adds resolveZulipSession for outbound session keys and treats zulip as markdown-capable.

Tests:

pnpm build
pnpm check
pnpm exec vitest run extensions/zulip/src/channel.test.ts src/infra/outbound/outbound-session.test.ts

Greptile Overview

Greptile Summary

This PR adds a new Zulip channel plugin under extensions/zulip that monitors an allowlisted set of streams, maps stream+topic to OpenClaw sessions, supports outbound targets like stream:<stream>#<topic?>, and optionally adds reaction indicators (start/success/failure) to the triggering message. It also updates core outbound session routing to generate stable Zulip session keys (including topic hashing for long topics) and marks zulip as markdown-capable.

Confidence Score: 3/5

This PR is mostly safe to merge, but has a couple behavior mismatches that should be fixed first.
Core architecture and tests look reasonable, but (1) the onboarding/env-var UX doesn’t match actual precedence rules and (2) multi-stream monitoring doesn’t actually constrain the event queue to the allowlist, which can materially change runtime behavior/perf on busy Zulip bots.
extensions/zulip/src/zulip/monitor.ts, extensions/zulip/src/zulip/accounts.ts

_{(2/5) Greptile learns from your feedback when you react with thumbs up/down!}

greptile-apps

_{2 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2026-02-05T14:24:16Z

extensions/zulip/src/zulip/accounts.ts

+
+  const baseUrl = (configUrl || envUrl)?.replace(/\/+$/, "") || undefined;
+  const email = configEmail || envEmail || undefined;


Env vars ignored by config. resolveZulipAccount currently prefers config values over env (baseUrl = (configUrl || envUrl) etc.). In onboarding (extensions/zulip/src/onboarding.ts:684-705) you prompt to “use env vars?” when they’re detected, but choosing “yes” doesn’t actually make env take precedence if config already has values; it just leaves config as-is. This makes the prompt misleading and can’t achieve “use env vars” unless the user clears config manually.

If the intent is to allow env to override config when the user opts in, you’ll need a config flag (or similar) that flips precedence to env || config for the default account, or otherwise ensure the onboarding path clears the stored fields when env is selected.

Also appears in: extensions/zulip/src/channel.ts:358-369 (describeAccount sources are tied to the same precedence).

Prompt To Fix With AI

This is a comment left during a code review. Path: extensions/zulip/src/zulip/accounts.ts Line: 121:123 Comment: **Env vars ignored by config.** `resolveZulipAccount` currently prefers config values over env (`baseUrl = (configUrl || envUrl)` etc.). In onboarding (`extensions/zulip/src/onboarding.ts:684-705`) you prompt to “use env vars?” when they’re detected, but choosing “yes” doesn’t actually make env take precedence if config already has values; it just leaves config as-is. This makes the prompt misleading and can’t achieve “use env vars” unless the user clears config manually. If the intent is to allow env to override config when the user opts in, you’ll need a config flag (or similar) that flips precedence to `env || config` for the default account, or otherwise ensure the onboarding path clears the stored fields when env is selected. Also appears in: `extensions/zulip/src/channel.ts:358-369` (describeAccount sources are tied to the same precedence). How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-02-05T14:24:21Z

Additional Comments (1)

extensions/zulip/src/zulip/monitor.ts
Allowlist not enforced for multi-stream. When more than one stream is configured, registerQueue does not pass a narrow, so Zulip will deliver all message events for the bot’s subscriptions. shouldIgnoreMessage then filters in-process, but this means the plugin still ingests and processes (polls/parses) every subscribed stream, which violates the stated “monitors a configured stream allowlist” behavior and can be a big performance hit on busy bots.

If Zulip’s API supports multiple narrows (e.g. [["channel","A"],["channel","B"]] semantics) or registering separate queues per stream, the queue registration should be updated to actually constrain events to the allowlist when streams.length > 1.

Prompt To Fix With AI

This is a comment left during a code review.
Path: extensions/zulip/src/zulip/monitor.ts
Line: 1278:1284

Comment:
**Allowlist not enforced for multi-stream.** When more than one stream is configured, `registerQueue` does not pass a `narrow`, so Zulip will deliver *all* message events for the bot’s subscriptions. `shouldIgnoreMessage` then filters in-process, but this means the plugin still ingests and processes (polls/parses) every subscribed stream, which violates the stated “monitors a configured stream allowlist” behavior and can be a big performance hit on busy bots.

If Zulip’s API supports multiple narrows (e.g. `[["channel","A"],["channel","B"]]` semantics) or registering separate queues per stream, the queue registration should be updated to actually constrain events to the allowlist when `streams.length > 1`.

How can I resolve this? If you propose a fix, please make it concise.

jamie-dit · 2026-02-05T23:30:29Z

Addressed Greptile feedback re multi-stream allowlist enforcement.

Zulip monitor now registers one event queue per configured stream (each with a channel:<stream> narrow), instead of registering an un-narrowed queue when multiple streams are configured.
Keeps the in-process shouldIgnoreMessage filter as a safety net.

Commit: fc1821e

jamie-dit · 2026-02-06T00:00:59Z

Follow-up: reduce missed replies under rate limiting.

zulipRequest now tags errors with status and retryAfterMs (Retry-After header when present).
Outbound sendZulipStreamMessage now retries on 429/502/503/504 with exponential backoff (prefers Retry-After).

Commit: 75d4096

jamie-dit · 2026-02-06T03:02:00Z

Fix: reaction cleanup (eyes spam)

Zulip reaction removal now uses query params instead of a DELETE request body, which is more reliable across Zulip deployments and should prevent the onStart "eyes" reaction from sticking around.

Commit: 25c0547

jamie-dit · 2026-02-06T03:05:19Z

Fix: reduce Zulip /events 429s

Explicitly set dont_block=false on /events.
Add a small sleep when Zulip returns immediately with no events, to avoid a tight poll loop if long-polling isn't honored.

Commit: cb8c651

jamie-dit · 2026-02-06T03:13:26Z

Fix: larger backoff on Zulip 429s

Increase the monitor backoff base for 429 responses (start at 10s, exponential from there) to avoid getting stuck in a 3s retry loop on stricter Zulip deployments.

Commit: 806dd29

jamie-dit · 2026-02-06T03:17:57Z

Fix: throttle heartbeat-only Zulip events

Some Zulip deployments can return non-message events (e.g. heartbeat) even when event_types is restricted. Treating those as "empty" avoids an immediate re-poll loop that can contribute to 429s.

Commit: fb4775e

jamie-dit · 2026-02-06T03:43:09Z

Fix: retry reaction add/remove on 429

Even with the DELETE query-param fix, reactions can still stick if Zulip rate-limits reaction endpoints (429). Reactions now use zulipRequestWithRetry (2 retries) so 👀 is much less likely to get stuck.

Commit: 2f32e01

jamie-dit · 2026-02-06T03:53:19Z

Feature: option to leave 👀 (onStart) reaction

Add channels.zulip.reactions.clearOnFinish (default true). Set it to false to leave the onStart reaction (e.g. 👀) on the message after the bot responds.

Commit: f2b2806

jamie-dit · 2026-02-06T04:53:05Z

Update: uploads + topic directive

Inbound uploads: detect Zulip user_uploads links, download up to channels.zulip.mediaMaxMb (default 5MB), and attach as MediaPaths/MediaUrls so the agent can see/process the files.
Outbound uploads: sendMedia now uploads via /api/v1/user_uploads and posts the resulting link into the stream/topic.
Topic creation: agent can switch topics by prefixing a reply with [[zulip_topic: <topic>]] (directive is stripped before posting).
Compatibility: register queues using the canonical stream narrow operator.
Docs: docs/channels/zulip.md updated with uploads + topic directive + reactions.clearOnFinish.

Commit: 0ac0da0

rafaelreis-r · 2026-02-06T22:02:05Z

Duplicate #8365

Adds a full Zulip channel plugin with: - Event queue polling with exponential backoff - Authenticated upload downloads from /user_uploads/ - Outbound file uploads via /api/v1/user_uploads - Reaction indicators (eyes → check_mark/warning) - Topic directive [[zulip_topic: <topic>]] - HTTP retry with backoff (429/502/503/504) - Full actions API (stream CRUD, user management, reactions) - Channel docs and unit tests Refs: #5163, openclaw#8365, openclaw#9643

Adds a full-featured Zulip channel plugin with: Core Features: - Event queue polling with exponential backoff and auto-recovery - Authenticated upload downloads from /user_uploads/ - Outbound file uploads via /api/v1/user_uploads - Reaction indicators (eyes → check_mark/warning) - Topic directive [[zulip_topic: <topic>]] - HTTP retry with backoff (429/502/503/504) - Full actions API (stream CRUD, user management, reactions) - Channel docs and unit tests Key Improvement Over Existing PRs: - Implements CONCURRENT message processing with staggered start times - Other PRs (openclaw#9643, openclaw#14182) process messages sequentially, causing reply delays and "message dumps" when multiple messages arrive - This implementation starts processing each message immediately with a 200ms stagger for natural conversation flow - Replies arrive as each finishes instead of all at once Technical Details: - Fire-and-forget message processing with per-message error handling - Maintains event cursor and queue ID correctly during concurrent processing - Tested live and confirmed significant UX improvement Refs: openclaw#5163, openclaw#8365, openclaw#9643, openclaw#12183

Co-authored-by: Ian MoltVS <[email protected]> Inspired-by: #15051

jamie-dit · 2026-02-14T01:20:20Z

New PR created to keep commits clean

feat: add Zulip channel plugin #15887

Adds a full-featured Zulip channel plugin with: Core Features: - Event queue polling with exponential backoff and auto-recovery - Authenticated upload downloads from /user_uploads/ - Outbound file uploads via /api/v1/user_uploads - Reaction indicators (eyes → check_mark/warning) - Topic directive [[zulip_topic: <topic>]] - HTTP retry with backoff (429/502/503/504) - Full actions API (stream CRUD, user management, reactions) - Channel docs and unit tests Key Improvement Over Existing PRs: - Implements CONCURRENT message processing with staggered start times - Other PRs (openclaw#9643, openclaw#14182) process messages sequentially, causing reply delays and "message dumps" when multiple messages arrive - This implementation starts processing each message immediately with a 200ms stagger for natural conversation flow - Replies arrive as each finishes instead of all at once Technical Details: - Fire-and-forget message processing with per-message error handling - Maintains event cursor and queue ID correctly during concurrent processing - Tested live and confirmed significant UX improvement Refs: openclaw#5163, openclaw#8365, openclaw#9643, openclaw#12183

openclaw-barnacle bot added the docs Improvements or additions to documentation label Feb 5, 2026

greptile-apps bot reviewed Feb 5, 2026

View reviewed changes

openclaw-barnacle bot added the commands Command implementations label Feb 5, 2026

FtlC-ian mentioned this pull request Feb 8, 2026

feat: Zulip channel plugin #12183

Closed

rafaelreis-r mentioned this pull request Feb 11, 2026

Add Zulip channel plugin #8365

Closed

FtlC-ian mentioned this pull request Feb 12, 2026

feat: Zulip channel plugin with concurrent message processing #15051

Closed

jamie-dit force-pushed the feat/zulip-channel branch from a0d6f09 to 1e0e185 Compare February 13, 2026 15:37

jamie-dit added 8 commits February 14, 2026 02:39

Zulip: add channel plugin

69b09c1

Zulip: fix monitor startup + outbound send

6af68ea

Zulip plugin: add runtime deps

581b726

Plugins: sanitize npm install manifest

fab90ab

Zulip: enforce stream allowlist

8471c97

Lint: fix zulip narrow test + plugin install

663cb77

Zulip: retry on rate limits

86fcf55

Zulip: default followup queue + alwaysReply

b6dddd7

jamie-dit added 9 commits February 14, 2026 02:40

Zulip: backoff on monitor rate limits

f6b0a51

Zulip: remove reactions via query params

bee5ce9

Zulip: throttle empty polls to avoid 429

16dd15a

Zulip: slow down on 429 rate limits

301ead8

Zulip: throttle heartbeat-only event polls

b7a7291

Docs: make Zulip topic note generic

d35c617

Zulip: retry reaction add/remove on 429

0bf170b

Zulip: allow leaving onStart reaction

42930fe

Zulip: uploads + topic directive

9d2a01c

jamie-dit force-pushed the feat/zulip-channel branch from 1e0e185 to a4b7ce2 Compare February 13, 2026 15:46

feat: concurrent message processing with staggered starts

8dd23cd

Co-authored-by: Ian MoltVS <[email protected]> Inspired-by: #15051

jamie-dit force-pushed the feat/zulip-channel branch from a4b7ce2 to 8dd23cd Compare February 13, 2026 15:47

openclaw-barnacle bot added the size: XL label Feb 13, 2026

jamie-dit closed this Feb 14, 2026


		const baseUrl = (configUrl \|\| envUrl)?.replace(/\/+$/, "") \|\| undefined;
		const email = configEmail \|\| envEmail \|\| undefined;

Uh oh!

Conversation

jamie-dit commented Feb 5, 2026 • edited by greptile-apps bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Overview

Greptile Summary

Confidence Score: 3/5

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot commented Feb 5, 2026

Uh oh!

jamie-dit commented Feb 5, 2026

Uh oh!

jamie-dit commented Feb 6, 2026

Uh oh!

jamie-dit commented Feb 6, 2026

Uh oh!

jamie-dit commented Feb 6, 2026

Uh oh!

jamie-dit commented Feb 6, 2026

Uh oh!

jamie-dit commented Feb 6, 2026

Uh oh!

jamie-dit commented Feb 6, 2026

Uh oh!

jamie-dit commented Feb 6, 2026

Uh oh!

jamie-dit commented Feb 6, 2026

Uh oh!

rafaelreis-r commented Feb 6, 2026

Uh oh!

jamie-dit commented Feb 14, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

jamie-dit commented Feb 5, 2026 •

edited by greptile-apps bot

Loading