Files
Benjamin Taylor b394f06fdc refactor(channels): rename @copilotkit/bot* packages to @copilotkit/channels* (OSS-438)
Renames the Bots SDK to the Channels SDK. Names only — no behavior change.

- 8 packages @copilotkit/bot* -> @copilotkit/channels* (git mv dirs, names,
  workspace: cross-deps). Now includes @copilotkit/bot-intelligence ->
  @copilotkit/channels-intelligence (landed on main via #5761; unpublished, so
  renamed fresh with the family).
- release.config.json scope keys + versionSource; ReleaseScope union;
  canary/stable-release/publish-release scope dropdowns; verify script
- examples/slack (Kite) + examples/teams: deps, jsxImportSource, imports
- showcase/shell-docs: content dirs docs/bots->docs/channels and
  reference/bot->reference/channels, nav registry, redirects

createBot and other API names unchanged. Old @copilotkit/bot* to be deprecated
after the new packages publish (bot-intelligence was never published).

Re-derived onto latest main (was conflicting after #5761 landed).

Refs OSS-438
2026-07-08 13:27:35 -05:00

88 lines
3.3 KiB
TypeScript

/**
* `issue_list` — renders a set of Linear issues as a compact Block Kit card:
* a header, ONE section with one scannable line per issue (status dot + linked
* identifier + title + assignee · updated), and a count footer.
*
* This is deliberately a fixed THREE-block layout (header + section + context)
* regardless of issue count: a card-per-issue layout (~3 blocks each) blows
* past Slack's per-attachment block limit on long lists and gets rejected with
* `invalid_attachments`. We instead inline up to `MAX` issues into a single
* section and surface the overflow in the footer.
*
* The agent fetches issues from the Linear MCP server and passes the fields
* it wants shown; the Slack formatting lives here. For a single issue (or
* right after creating one) prefer `issue_card`, which shows a full grid.
*
* Authored with the `@copilotkit/channels-ui` JSX vocabulary.
*/
import { z } from "zod";
import { Context, Header, Message, Section } from "@copilotkit/channels-ui";
import type { BotNode } from "@copilotkit/channels-ui";
import { accentForIssues, stateGlyph } from "./_status.js";
const issueSchema = z.object({
identifier: z.string().describe("Linear issue identifier, e.g. 'CPK-1234'."),
title: z.string().describe("Issue title."),
url: z.string().optional().describe("Link to the issue in Linear."),
state: z
.string()
.optional()
.describe("Workflow state name, e.g. 'Todo', 'In Progress', 'Done'."),
assignee: z
.string()
.optional()
.describe("Assignee display name, or omit if unassigned."),
priority: z
.string()
.optional()
.describe("Priority label, e.g. 'Urgent', 'High', 'Medium', 'Low'."),
updated: z
.string()
.optional()
.describe("Human-readable last-updated, e.g. '2d ago'."),
});
export const issueListSchema = z.object({
heading: z
.string()
.optional()
.describe("Optional heading, e.g. 'Open CPK issues this cycle'."),
issues: z.array(issueSchema).min(1).describe("The issues to render."),
});
export type IssueListProps = z.infer<typeof issueListSchema>;
type Issue = z.infer<typeof issueSchema>;
/** Max issues rendered inline; the rest are summarized in the footer. */
const MAX = 15;
/** Max title length before trimming (keeps each line scannable). */
const TITLE_MAX = 70;
/** Render a list of Linear issues as a compact, fixed-size Block Kit card. */
export function IssueList({ heading, issues }: IssueListProps): BotNode {
const lines = issues.slice(0, MAX).map((issue: Issue) => {
const idLink = issue.url
? `[**${issue.identifier}**](${issue.url})`
: `**${issue.identifier}**`;
const title =
issue.title.length > TITLE_MAX
? `${issue.title.slice(0, TITLE_MAX)}…`
: issue.title;
const meta = `${issue.assignee ?? "unassigned"}${issue.updated ? ` · ${issue.updated}` : ""}`;
return `${stateGlyph(issue.state)} ${idLink} ${title} — ${meta}`;
});
const footer =
issues.length > MAX
? `Showing ${MAX} of ${issues.length} issues`
: `${issues.length} issue${issues.length === 1 ? "" : "s"}`;
return (
<Message accent={accentForIssues(issues)}>
<Header>{`📋 ${heading ?? "Linear issues"}`}</Header>
<Section>{lines.join("\n")}</Section>
<Context>{footer}</Context>
</Message>
);
}