Skip to content

feat: configurable description for groups created via /new chat - #220

Open
maiqigh wants to merge 1 commit into
zarazhangrui:mainfrom
maiqigh:feat/new-chat-description
Open

feat: configurable description for groups created via /new chat#220
maiqigh wants to merge 1 commit into
zarazhangrui:mainfrom
maiqigh:feat/new-chat-description

Conversation

@maiqigh

@maiqigh maiqigh commented Jul 28, 2026

Copy link
Copy Markdown

Motivation

Groups created with /new chat currently have an empty description. In practice it's useful to stamp bridge-created groups with a stable marker (e.g. Claude Code session group) so they stay identifiable — searchable in Lark, visible in chat settings — even after the group gets renamed to a topic-specific name later.

The plumbing already exists: createBoundChat() accepts a description and forwards it to channel.createChat(), but handleNewChat() never passes one.

Changes

  • Add optional preferences.newChatDescription config key (documented via schema JSDoc, consistent with the other preference keys).
  • handleNewChat() threads it into createBoundChat().
  • Unit tests: description is passed through to channel.createChat, and omitted when unset.

Default behavior is unchanged when the key is not configured.

Testing

  • pnpm typecheck passes
  • pnpm vitest run tests/unit/bot/group.test.ts — 3/3 pass
  • Full pnpm test: 618 passed; the 2 failures (tests/unit/cli/preflight.test.ts, tests/integration/cli/secrets-profile.test.ts) also fail on unmodified main in my environment — they read the developer's real ~/.lark-channel profile, unrelated to this change.

🤖 Generated with Claude Code

createBoundChat() already accepts a description and forwards it to
channel.createChat(), but handleNewChat() never passed one, so groups
created via /new chat always end up with an empty description.

Add an optional preferences.newChatDescription config key and thread it
through. A stable description marker keeps bridge-created groups
identifiable (searchable in Lark, visible in chat settings) even after
the group is renamed to a topic-specific name. Default behavior is
unchanged when the key is unset.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant