W18 — Telegram bridge, flow builder upgrades
A 7.7k-LOC single-commit drop: outbound Telegram messaging matures into a reusable skill pattern, and the flow builder gets the upgrades that unblock the next quarter's work.
A focused week. Two commits, both heavy. The headline drop is the Telegram bridge plus a parcel of flow-builder upgrades that have been queued for weeks.
What shipped
Telegram bridge
Outbound messaging is now a first-class skill: plain text, media attachments, parameterized recipients. The “Telegram Bot Agent” pattern crystallized in the same change — a reusable shape any flow can adopt to expose itself as a chat-driven entry point. Inbound webhook handling was wired but not yet promoted to a skill UI; that ships next.
Flow builder upgrades
The bundle:
- Tighter typed connectivity — node ports now refuse mismatched shape connections at canvas time, not runtime
- Inspector parity for new node types added in the previous weeks
- Run history surfaced as a side-panel rather than a modal — closer to the work, less context-switching
- Performance fixes on large canvases (drag latency was creeping up; gone now)
Architecture moves
The Telegram bridge is the first concrete proof point of the multi-channel communication layer the strategic vision calls out. The pattern — messaging is a skill, not a special case — generalizes. Email, Discord, IFTTT-style webhooks all fit the same mold once one channel is properly shaped.
By the numbers
- 2 commits, 1 milestone (the 7.7k-LOC bridge drop)
- +7,708 / −195 (net +7,513)
A reminder that volume of commits is a poor proxy for week-impact. One well-shaped change can move the project further than 50 small ones.
What’s next
Promote the Telegram inbound to a proper skill UI. Begin the public metrics surface — the very page that, eventually, generates this kind of dev log automatically.