feat(sidebar): show Slack icon for tasks from Slack threads

[andrewm4894]

Problem

Tasks created from Slack threads look identical to tasks created in-app. From the Slack thread:

would be nice if i could quickly see which of these are slack threads in the task list — i kinda tend to do different stuff in the app vs via slack and so seeing some slack icons for the cloud ones that are actually slack threads i think could be a nice touch

Changes

• Surface origin_product === "slack" in the sidebar TaskIcon (used by both the sidebar list and the command palette).
  • Cloud tasks from Slack: replace the cloud icon with the Slack logo while keeping the existing running / completed / failed color coding (and the ph-pulse animation while running). Tooltip becomes Slack (running) / Slack (completed) / etc.
  • Local tasks from Slack (no PR, no diff, not pinned, not unread): use the Slack logo instead of the default chat bubble, with a From Slack thread tooltip.
• Thread originProduct through TaskRow → TaskItem → TaskIcon and through CommandMenu's TaskCommandIcon.
• Add a useSlackTasks() hook. The /tasks/summaries/ endpoint doesn't include origin_product, so we fetch the slack-origin subset separately (getTasks({ originProduct: "slack" })) and intersect by id in useSidebarData to flag tasks. For the showAllUsers path (which already uses full tasks), we read origin_product directly off the task.

Drive-by

• Dedupe a duplicate INBOX_VIEWED entry in analytics.ts introduced in feat(inbox): instrument analytics for engagement events #2228 — it was failing typecheck (TS1117 / TS2717) and blocking the local pre-commit hook.
• Drop a stale track(ANALYTICS_EVENTS.INBOX_VIEWED) call in navigationStore that didn't pass the required properties. The canonical track-with-properties call in InboxSignalsTab already fires when the inbox actually loads.

How did you test this?

• Verified tsc -p tsconfig.web.json --noEmit no longer reports the analytics duplicate / navigationStore errors that were on main.
• Ran pnpm exec vitest run over the touched feature folders — 23 / 23 sidebar tests pass. (One pre-existing test suite — useTaskPrStatus.test.ts — fails to resolve @posthog/electron-trpc/renderer; same on main, unrelated.)
• Ran pnpm exec biome check over the 6 touched files — clean.
• Did not boot the Electron UI in this environment, so the rendered icon swap is not visually confirmed end-to-end. Worth a quick local smoke against a Slack-origin task before un-drafting.

Publish to changelog?

no

---

Created with PostHog Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1ca718908d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[greptile-apps]

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
apps/code/src/renderer/features/tasks/hooks/useTasks.ts:78-87
`useSlackTasks` doesn't accept an `options` parameter, so callers can't conditionally disable it (e.g. when `showAllUsers=true`). Adding an `options` argument — consistent with `useTaskSummaries` — allows the caller in `useSidebarData` to skip the fetch when it's redundant.

```suggestion
export function useSlackTasks(options?: { enabled?: boolean }) {
  return useAuthenticatedQuery<Task[]>(
    taskKeys.list({ originProduct: "slack" }),
    (client) =>
      client.getTasks({ originProduct: "slack" }) as unknown as Promise<Task[]>,
    {
      refetchInterval: TASK_LIST_POLL_INTERVAL_MS,
      enabled: options?.enabled ?? true,
    },
  );
}
```

### Issue 2 of 2
apps/code/src/renderer/features/sidebar/hooks/useSidebarData.ts:137
`useSlackTasks` is called unconditionally even when `showAllUsers=true`. In that path, `rawTasks` is built from `fullTasks` which already maps `origin_product: t.origin_product` directly, so `slackTaskIds` is never actually needed to derive `originProduct` (the `task.origin_product ?? ...` short-circuits). The hook still fires on mount and re-polls every 30 s, and `slackTaskIds` is in the `taskData` dependency array, so any refetch triggers a full `taskData` recomputation even though the result is unaffected. Disabling the hook when `showAllUsers` is true eliminates the redundant request and memo churn.

```suggestion
  const { data: slackTasks = [] } = useSlackTasks({ enabled: !showAllUsers });
```

_{Reviews (1): Last reviewed commit: "feat(sidebar): show Slack icon for tasks..." | Re-trigger Greptile}

[greptile-apps]

useSlackTasks is called unconditionally even when showAllUsers=true. In that path, rawTasks is built from fullTasks which already maps origin_product: t.origin_product directly, so slackTaskIds is never actually needed to derive originProduct (the task.origin_product ?? ... short-circuits). The hook still fires on mount and re-polls every 30 s, and slackTaskIds is in the taskData dependency array, so any refetch triggers a full taskData recomputation even though the result is unaffected. Disabling the hook when showAllUsers is true eliminates the redundant request and memo churn.

Suggested change

	const { data: slackTasks = [] } = useSlackTasks();
	const { data: slackTasks = [] } = useSlackTasks({ enabled: !showAllUsers });

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/code/src/renderer/features/sidebar/hooks/useSidebarData.ts
Line: 137

Comment:
`useSlackTasks` is called unconditionally even when `showAllUsers=true`. In that path, `rawTasks` is built from `fullTasks` which already maps `origin_product: t.origin_product` directly, so `slackTaskIds` is never actually needed to derive `originProduct` (the `task.origin_product ?? ...` short-circuits). The hook still fires on mount and re-polls every 30 s, and `slackTaskIds` is in the `taskData` dependency array, so any refetch triggers a full `taskData` recomputation even though the result is unaffected. Disabling the hook when `showAllUsers` is true eliminates the redundant request and memo churn.

```suggestion
  const { data: slackTasks = [] } = useSlackTasks({ enabled: !showAllUsers });
```

How can I resolve this? If you propose a fix, please make it concise.

[andrewm4894]

Adopted in 0e28236 — useSlackTasks({ enabled: !showAllUsers, showInternal }). The showAllUsers path keeps short-circuiting on task.origin_product from fullTasks, so no fetch and no memo churn there.

[joshsny]

thanks for adding this, think we should change to originProduct so we can use this for other sources too

[joshsny]

it'd be nice to plumb this as originProduct so that it can be extended to other products also

[andrewm4894]

Good shout — done in 1d295a2. CloudStatusIcon now takes originProduct (string), and there's a small ORIGIN_PRODUCT_META map at the top of the file keyed by origin_product value, so adding another product is one line. The default-fallback branch (line 230-ish) uses the same lookup, so any other product registered in the map automatically gets a labeled icon there too.