Show channel task kickoff as an agent message and slim the task card#3346
Show channel task kickoff as an agent message and slim the task card#3346k11kirky wants to merge 5 commits into
Conversation
Channel feed kickoff rows now render as agent messages (robot avatar, "Agent" author) with an inert mention-styled "@name started a new task" body instead of the raw prompt. The task card drops the requested-by line, task slug, and Cloud/Local runtime label. Generated-By: PostHog Code Task-Id: 0a03c896-d426-4b8c-acf7-4833e47d03f2
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
|
React Doctor found no issues in the changed files. 🎉 Reviewed by React Doctor for commit |
Factors the non-self mention chip styling out of MentionText into an exported mentionChipClass so the feed's inert kickoff mention can't drift from real thread mentions, and updates a useTaskStatusDisplay comment that still referenced the removed "· Local" meta text. Generated-By: PostHog Code Task-Id: 0a03c896-d426-4b8c-acf7-4833e47d03f2
Generated-By: PostHog Code Task-Id: 0a03c896-d426-4b8c-acf7-4833e47d03f2
Generated-By: PostHog Code Task-Id: 0a03c896-d426-4b8c-acf7-4833e47d03f2
|
Reviews (1): Last reviewed commit: "Let the channel task card span the full ..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| <span className="inline-flex items-center gap-1 text-muted-foreground text-xs"> | ||
| <GitBranchIcon size={12} /> | ||
| {task.repository} | ||
| </span> | ||
| )} |
There was a problem hiding this comment.
When a local run is non-terminal, useTaskStatusDisplay() returns no badge because the backend can keep the run at queued while it is running on the creator's machine. This change also removes the Local meta text, so a newly started local task with no stage, repository, or PR renders with no status or runtime cue in the channel feed.
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!
| {task.created_by ? ( | ||
| <> | ||
| {/* Mention-styled but rendered inert: the starter shouldn't be | ||
| notified about their own task. */} | ||
| <span className={mentionChipClass}> | ||
| @{userDisplayName(task.created_by)} | ||
| </span>{" "} | ||
| started a new task |
There was a problem hiding this comment.
For non-user_created tasks that still include created_by, this body now says @Name started a new task even though the old card used origin_product to label sources like Slack, Signals, or Automation. Those channel rows can now attribute an automated or product-origin task to a person who did not start it in the channel.
Slack/automation-originated tasks can carry a created_by who didn't start the task in the channel; those rows now fall back to the neutral "A new task was started" copy instead of "@name started a new task". Generated-By: PostHog Code Task-Id: 0a03c896-d426-4b8c-acf7-4833e47d03f2
1 participant
Problem
In Bluebird channel feeds, starting a task showed the full prompt as a message from the user, and the task card repeated metadata (requested-by line, task slug, Cloud/Local runtime) that added noise without helping readers scan the feed.
Why
Requested so channel feeds read like an agent announcing work rather than echoing the user's prompt back, keeping the feed scannable.
Changes
How did you test this?
pnpm --filter @posthog/ui typecheck— passespnpm --filter @posthog/ui test— 1450 tests passAutomatic notifications
Created with PostHog Code