PluginStats@intentface/latch-channels weekly downloads statistics
By intentface (9 listings) · npm · AI SDKs
Latch channels — bring a Latch agent to chat platforms (Slack first). A generic run→render-event projection plus per-platform adapters, reusing the core runtime, storage and durability (no separate state store).
@intentface/latch-channels has 496 recorded weekly downloads on npm, an increase of 484% over the past 30 days.
It ranks #1500 of 2,251 tracked npm listings by weekly downloads.
PluginStats has 543 daily observations since Apr 23, 2025; the latest is from Oct 17, 2026.
About @intentface/latch-channels
@intentface/latch-channels
Bring a Latch agent to the places people talk — Slack, Telegram, WhatsApp. Reuses the core runtime, storage and durability (no separate state store); identity (platform user → Principal) and channel → agent binding stay in user-land, per Latch's isolation model.
What it does
• Generic core (.) — the platform-agnostic half: • consumeRun(response) → AsyncIterable folded from the runtime's SSE Response; pendingApprovals / pendingQuestion read what a paused turn is waiting on from persisted history. Adding a platform is "translate RenderEvents", never "re-parse the AI stream." • createTurnKernel(config, surface) — everything a direct-message surface does between "a webhook arrived" and "the platform API was called", written once: dedupe, the identity gate (with stash + post-link replay), thread epochs (/new), commands, questionnaires, media folding (files inline, voice transcribed), the answer posted once at finish (split past the cap; a typing hint meanwhile), approvals and button taps back into the run. A Surface is pure protocol: send text / link / approval / question, edit or retire a card, download a file. • AuthResult, the lta: / ltq: button-payload codecs, splitText. • Telegram (./telegram) and WhatsApp (./whatsapp) — a webhook parser plus a Surface each, over the kernel. telegramChannel(config) / whatsappChannel(config) verify the webhook, ACK fast, and run the turn in the background (waitUntil). • Slack (./slack) — slackChannel(config): one agent's dedicated app; native message streaming with tool calls as task cards, initiator-owned threads, signed actor-bound approval buttons, atomic admission (claimOnce). One live run per chat comes from core's storage invariant on the shipped adapters; on a custom adapter without it, wire the optional claimTurn / releaseTurn lease — every adapter (kernel and Slack) honours it. Plus the per-agent app manifest generator, a minimal Web API client and hand-rolled Block Kit (no Chat SDK runtime dependency). Slack keeps its own engine because its surface is threads, not DMs.
Usage
A new DM platform: implement Surface and a parser from your webhook body to Inbound, then createTurnKernel(config, surface).handleInbound(event).
Description from the npm listing.
- ai
- ai-sdk
- agents
- llm
- slack
- telegram
- chatbot
Where @intentface/latch-channels sits in the listing
Each band is one page of 20. Weekly downloads on a log scale. Placement is projected from weekly downloads, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.
Charts
Images: 30d · 1y · all time · 1600×900 dark
Adoption over time
7/30/90-day growth
Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.
Recent observations
Full history (543)Similar npm AI SDKs plugins
Data source
Weekly downloads (trailing 7 complete days) come from the official npm downloads API. Downloads include CI and mirrors and are not equivalent to installs or users. npm publishes no ratings.
Listing: https://www.npmjs.com/package/@intentface/latch-channels. First seen Oct 16, 2026; last successful collection Oct 18, 2026. See the methodology.