Skip to content

fix(chat-platform): steady tool status line; label the chart's latest value - #1031

Merged
JeremyFunk merged 4 commits into
mainfrom
feat/chat-bot-tool-labels
Sep 24, 2026
Merged

JeremyFunk merged 4 commits into
mainfrom
feat/chat-bot-tool-labels

Conversation

@JeremyFunk

@JeremyFunk JeremyFunk commented Sep 24, 2026 •

Copy link
Copy Markdown
Collaborator
  • The status line keeps its ellipsis when a call finishes instead of jumping from "Running a query…" to "Running a query"; a failure appends "(failed)".
  • The single-series chart card's top-right value (the last bucket's value) is now labelled "now"; bare, it read as a total next to a spike.

…aw name

Slack and Discord showed the status line as `Tools: `run_sql`…`. Each tool now
has one or more factual phrases ("Running a query…"), picked per call by a hash
of the call id so the phrase varies between calls but holds still across the
edits of one message.
…ol is registered

The phrases lived in a table in chat-platform, keyed by tool name and linked to
nothing. They are now a required `phrases` option on `McpToolRegistrar.tool`,
so a new tool cannot register without them. The session picks one when the call
is declared and records it as `label` on the `tool-call` event; the Slack and
Discord renderer reads it from there and puts an unlabelled call in words.
…nd name the chart's latest value

A finished call dropped its ellipsis, so the status line jumped from "Running a
query…" to "Running a query". It now keeps it; a failure appends "(failed)".

The single-series chart card showed the last bucket's value bare in the top
right, which beside a spike read as a total. It is now labelled "now".
@coderabbitai

coderabbitai Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: d183f9a5-b8b9-40d5-8f8c-965a29a05917

📥 Commits

Reviewing files that changed from the base of the PR and between ba13d2b and d47a05c.

📒 Files selected for processing (4)
  • apps/web/src/og/chart-card.ts
  • packages/chat-platform/src/connectors/discord/render.ts
  • packages/chat-platform/src/connectors/slack/render.test.ts
  • packages/chat-platform/src/connectors/slack/render.ts
 ________________________________________________________________________________________________________________________
< Don't assume it - prove it. Prove your assumptions in the actual environment - with real data and boundary conditions. >
 ------------------------------------------------------------------------------------------------------------------------
  \
   \   (\__/)
       (•ㅅ•)
       /   づ
✨ Finishing Touches
📝 Generate docstrings
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@maple-review-bot

maple-review-bot Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

Note

Maple is reviewing this pull request at d47a05c. This comment updates with the review when it finishes.

…bels

# Conflicts:
#	apps/ai/src/mcp/tools/pull-request.ts
#	packages/chat-platform/src/connectors/discord/render.ts
#	packages/chat-platform/src/connectors/slack/render.test.ts
#	packages/chat-platform/src/connectors/slack/render.ts
@JeremyFunk JeremyFunk changed the title feat(chat-platform): describe tool calls in words; steady status line; label the chart's latest value fix(chat-platform): steady tool status line; label the chart's latest value Sep 24, 2026
@JeremyFunk
JeremyFunk merged commit 713be74 into main Sep 24, 2026
37 of 40 checks passed
@JeremyFunk
JeremyFunk deleted the feat/chat-bot-tool-labels branch September 24, 2026 00:06
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