feat(telegram): add forum topic creation support by nickjlamb · Pull Request #17035 · openclaw/openclaw

nickjlamb · 2026-02-15T10:23:41Z

Summary

Adds topic-create as a new Telegram message action, enabling programmatic creation of forum topics in supergroups via the message tool.

Closes #10427

Changes

src/telegram/send.ts — Add createForumTopicTelegram() function that calls the Telegram Bot API's createForumTopic method
src/agents/tools/telegram-actions.ts — Add createForumTopic action handler
src/channels/plugins/actions/telegram.ts — Wire topic-create into the Telegram adapter's listActions and handleAction
src/channels/plugins/message-action-names.ts — Register topic-create action name
src/infra/outbound/message-action-spec.ts — Add target mode for topic-create

Usage

message action="topic-create" to="-100123456789" name="My New Topic"

Optional parameters:

iconColor — Topic icon color (one of the six Telegram-supported values)
iconCustomEmojiId — Custom emoji ID for the topic icon

Requirements

The bot needs can_manage_topics permission in the target supergroup (set via BotFather or group admin settings).

Testing

Build: ✅ pnpm build passes
Lint: ✅ pnpm lint passes (0 warnings, 0 errors)
Git hooks: ✅ format + lint pre-commit hooks pass

Greptile Summary

Adds topic-create as a new Telegram message action for programmatic forum topic creation in supergroups. The implementation spans the full action pipeline: a createForumTopicTelegram() function in the send layer, action handler registration with proper gating in both the agent tools and channel adapter, config type extension, and action name/target mode registration.

The new action follows established patterns for Telegram actions: action gate checks, token resolution, retry/error handling, and channel activity recording
createForumTopic defaults to enabled (consistent with reactions, sendMessage, deleteMessage, editMessage) and can be disabled via channels.telegram.actions.createForumTopic: false
Input validation enforces non-empty topic name with a 128-character limit; iconColor and iconCustomEmojiId are optional pass-through parameters validated by the Telegram API server-side
The PR includes an unrelated skills/frontend-design/SKILL.md file from a prior commit in the branch history

Confidence Score: 4/5

This PR is safe to merge — the new feature follows established patterns with proper gating, validation, and error handling.
Score of 4 reflects clean, well-structured code that follows existing conventions throughout the action pipeline. The only reason it's not a 5 is the inclusion of an unrelated file (skills/frontend-design/SKILL.md) from a prior commit in the branch. No logical errors, security issues, or missing validation were found in the Telegram-related changes.
No files require special attention. The skills/frontend-design/SKILL.md file is unrelated to the PR scope but harmless.

_{Last reviewed commit: b5bfb73}

greptile-apps

_{6 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2026-02-15T10:27:58Z

src/agents/tools/telegram-actions.ts

+  if (action === "createForumTopic") {
+    const chatId = readStringOrNumberParam(params, "chatId", {
+      required: true,
+    });
+    const name = readStringParam(params, "name", { required: true });
+    const iconColor = readNumberParam(params, "iconColor", { integer: true });
+    const iconCustomEmojiId = readStringParam(params, "iconCustomEmojiId");


missing action gate check - other actions like sendMessage, deleteMessage, editMessage, and sendSticker include if (!isActionEnabled(...)) checks to respect the action gating configuration

Suggested change

if (action === "createForumTopic") {

const chatId = readStringOrNumberParam(params, "chatId", {

required: true,

});

const name = readStringParam(params, "name", { required: true });

const iconColor = readNumberParam(params, "iconColor", { integer: true });

const iconCustomEmojiId = readStringParam(params, "iconCustomEmojiId");

if (action === "createForumTopic") {

if (!isActionEnabled("createForumTopic")) {

throw new Error("Telegram createForumTopic is disabled.");

}

const chatId = readStringOrNumberParam(params, "chatId", {

required: true,

});

const name = readStringParam(params, "name", { required: true });

Prompt To Fix With AI

This is a comment left during a code review. Path: src/agents/tools/telegram-actions.ts Line: 331:337 Comment: missing action gate check - other actions like `sendMessage`, `deleteMessage`, `editMessage`, and `sendSticker` include `if (!isActionEnabled(...))` checks to respect the action gating configuration ```suggestion if (action === "createForumTopic") { if (!isActionEnabled("createForumTopic")) { throw new Error("Telegram createForumTopic is disabled."); } const chatId = readStringOrNumberParam(params, "chatId", { required: true, }); const name = readStringParam(params, "name", { required: true }); ``` How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-02-15T10:27:59Z

src/channels/plugins/actions/telegram.ts

      actions.add("sticker");
      actions.add("sticker-search");
    }
+    actions.add("topic-create");


topic-create added unconditionally - other actions like react, delete, edit, and sticker use gate() checks to respect configuration. consider adding if (gate("createForumTopic")) { actions.add("topic-create"); } for consistency

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

Prompt To Fix With AI

This is a comment left during a code review. Path: src/channels/plugins/actions/telegram.ts Line: 63:63 Comment: `topic-create` added unconditionally - other actions like `react`, `delete`, `edit`, and `sticker` use `gate()` checks to respect configuration. consider adding `if (gate("createForumTopic")) { actions.add("topic-create"); }` for consistency <sub>Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!</sub> How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-02-15T10:28:00Z

skills/frontend-design/SKILL.md

+---
+name: frontend-design
+description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
+---
+
+This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
+
+The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
+
+## Design Thinking
+
+Before coding, understand the context and commit to a BOLD aesthetic direction:
+
+- **Purpose**: What problem does this interface solve? Who uses it?
+- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
+- **Constraints**: Technical requirements (framework, performance, accessibility).
+- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
+
+**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
+
+Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
+
+- Production-grade and functional
+- Visually striking and memorable
+- Cohesive with a clear aesthetic point-of-view
+- Meticulously refined in every detail
+
+## Frontend Aesthetics Guidelines
+
+Focus on:
+
+- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
+- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
+- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
+- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
+- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
+
+NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts, Space Grotesk), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
+


this file appears unrelated to the PR's stated purpose (telegram forum topic creation). the PR description makes no mention of adding a frontend-design skill. this may have been included accidentally from commit 1754daa

Prompt To Fix With AI

This is a comment left during a code review. Path: skills/frontend-design/SKILL.md Line: 1:39 Comment: this file appears unrelated to the PR's stated purpose (telegram forum topic creation). the PR description makes no mention of adding a frontend-design skill. this may have been included accidentally from commit 1754daa0 How can I resolve this? If you propose a fix, please make it concise.

nickjlamb · 2026-02-15T10:33:21Z

RE: skills/frontend-design/SKILL.md — this file already exists on main (commit 1754daa). Our branch only touched it to fix a pre-existing oxfmt formatting issue that was failing CI (format:check). No content changes — just whitespace normalization so the PR's CI checks pass.

nickjlamb · 2026-02-16T18:59:26Z

Friendly bump 👋 — happy to address any feedback or make changes if needed. All CI checks are green (aside from the fork-related formal_conformance permission issue).

This reverts commit c529e60.

… pipe" This reverts commit 8b14052.

This reverts commit 53af9f7.

This reverts commit b6d934c.

…e in build logs" This reverts commit 717caa9.

…mage" This reverts commit 2ab6313.

This reverts commit 32c66af.

This reverts commit 59e0e7e.

This reverts commit b91e437.

This reverts commit d4a142f.

This reverts commit 06b961b.

…ew/reset" This reverts commit d6acd71.

This reverts commit 34b18ea.

openclaw-barnacle · 2026-02-18T00:39:29Z