Skip to content

✨ feat(topic): add group-by-status mode to topic sidebar#15366

Merged
arvinxx merged 3 commits into
canaryfrom
feat/topic-group-by-status
Jun 1, 2026
Merged

✨ feat(topic): add group-by-status mode to topic sidebar#15366
arvinxx merged 3 commits into
canaryfrom
feat/topic-group-by-status

Conversation

@arvinxx

@arvinxx arvinxx commented Jun 1, 2026

Copy link
Copy Markdown
Member

💻 Change Type

  • ✨ feat

🔀 Description of Change

Adds a By status (按状态) grouping option to the agent topic sidebar's Organize menu, alongside By time / By project / Flat.

Topics group by status in a fixed priority order, top → bottom:

  1. Awaiting input (waitingForHuman) — highest priority
  2. Running (running)
  3. Active (active, and topics with no status)
  4. Paused / Failed / Completed / Archived

Ordering is resolved server-side. The sidebar only loads the first page of topics, so bucketing that partial list purely client-side could hide high-priority topics (awaiting-human / running) that live on a later page — that was the flaky behavior. The query now accepts sortBy: 'updatedAt' | 'status'; status orders by a priority CASE (waitingForHuman → running → active → paused → failed → completed → archived) before the updatedAt tiebreaker, so the most important topics always land on page one. The client still buckets for display, now over a correctly-ordered page.

Plumbing: sortBy flows TRPC getTopicsTopicModel.query orderBy, and from the client useFetchChatTopics (requests status only when the resolved agent group mode is byStatus; group sessions keep the default) → useFetchTopics → store fetch action (incl. SWR key) → service.

Other details:

  • Only non-empty groups render; favorites stay in their own group on top.
  • Within each status group, topics sort by the user's createdAt / updatedAt preference.
  • The mode persists per-agent (added to TopicGroupMode + both zod schemas).
  • Server priority STATUS_SORT_RANK and client STATUS_GROUP_ORDER carry cross-reference comments to stay in sync.

🧪 How to Test

  • Tested locally
  • Added/updated tests
  • No tests needed

Open the topic filter menu → OrganizeBy status. With more topics than one page, confirm awaiting-human / running topics appear at the top (not stuck on a later page).

  • Model ordering: cd packages/database && bunx vitest run src/models/__tests__/topics/topic.query.test.ts — 61 passed (incl. status-priority + default-order cases).
  • Client bucketing: cd packages/utils && bunx vitest run src/client/topic.test.ts — 17 passed.

📝 Additional Information

Run pnpm i18n before merge to sync the remaining locale files (zh-CN / en-US dev-preview keys are included here).

🤖 Generated with Claude Code

Add a new "By status" grouping option to the agent topic sidebar. Topics
bucket into fixed-priority groups — waitingForHuman first, then running,
then active, with the remaining states below. Topics without a status are
treated as active. Only non-empty groups render.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 1, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
lobehub Ready Ready Preview, Comment Jun 1, 2026 5:35am

Request Review

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @arvinxx, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@dosubot dosubot Bot added size:L This PR changes 100-499 lines, ignoring generated files. feature:topic Topic/Conversation/Session management labels Jun 1, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6b0ca8fa3d

ℹ️ 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".


return useMemo(() => {
const groupModes: TopicGroupMode[] = ['byTime', 'byProject', 'flat'];
const groupModes: TopicGroupMode[] = ['byStatus', 'byTime', 'byProject', 'flat'];

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Wire by-status mode into the rendered agent list

Selecting this new option in the agent sidebar stores topicGroupMode: 'byStatus', but the sidebar rendered from Topic/index.tsx mounts List, and List/index.tsx still only handles flat and byProject before falling through to ByTimeMode. In the desktop agent sidebar, choosing “By status” therefore shows time grouping while the menu checkmark says by-status; the new ByStatusMode branch was added only to TopicListContent, which is used by the mobile topic panel, not this sidebar path.

Useful? React with 👍 / 👎.

@codecov

codecov Bot commented Jun 1, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 86.66667% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 71.15%. Comparing base (58c671b) to head (e177284).
⚠️ Report is 6 commits behind head on canary.

Additional details and impacted files
@@            Coverage Diff            @@
##           canary   #15366     +/-   ##
=========================================
  Coverage   71.15%   71.15%             
=========================================
  Files        3200     3200             
  Lines      319698   319765     +67     
  Branches    29153    34012   +4859     
=========================================
+ Hits       227485   227541     +56     
- Misses      92041    92051     +10     
- Partials      172      173      +1     
Flag Coverage Δ
app 62.04% <66.66%> (-0.01%) ⬇️
database 92.37% <100.00%> (+<0.01%) ⬆️
packages/agent-runtime 80.48% <ø> (ø)
packages/builtin-tool-lobe-agent 18.52% <ø> (ø)
packages/context-engine 84.17% <ø> (ø)
packages/conversation-flow 91.29% <ø> (ø)
packages/file-loaders 87.89% <ø> (ø)
packages/memory-user-memory 74.99% <ø> (ø)
packages/model-bank 99.99% <ø> (ø)
packages/model-runtime 84.68% <ø> (ø)
packages/prompts 72.49% <ø> (ø)
packages/python-interpreter 92.90% <ø> (ø)
packages/ssrf-safe-fetch 0.00% <ø> (ø)
packages/types 35.90% <0.00%> (ø)
packages/utils 88.69% <97.61%> (+0.21%) ⬆️
packages/web-crawler 88.08% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
Store 68.44% <66.66%> (-0.01%) ⬇️
Services 54.60% <0.00%> (-0.01%) ⬇️
Server 72.54% <100.00%> (-0.01%) ⬇️
Libs 57.01% <ø> (ø)
Utils 81.44% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

The sidebar only loads the first page of topics, so grouping that partial
list client-side could hide high-priority topics (awaiting-human / running)
that live on a later page. Push the ordering to the query instead.

- Add `sortBy: 'updatedAt' | 'status'` to the topics query (TRPC + model).
  `status` orders by a priority CASE (waitingForHuman → running → active →
  paused → failed → completed → archived) before the updatedAt tiebreaker,
  so the most important topics always land on the first page.
- Plumb `sortBy` through the service, store fetch action (incl. SWR key),
  and the shared topic hooks; `useFetchChatTopics` requests `status` ordering
  only when the resolved agent group mode is `byStatus` (group sessions keep
  the default). The client still buckets for display, now over a correctly
  ordered page.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
A topic generating a response shows the loading ring via the client-only
`topicLoadingIds` state, not a persisted `status`, so it was landing in the
"active" group. Mirror the sidebar TopicItem icon precedence when bucketing:
waitingForHuman wins, then a topic that is streaming on this client (or
persisted as running) goes to "running", then the persisted status.

The loading overlay stays client-side (the server can't know a given client
is mid-stream); the selector passes `topicLoadingIds` into the byStatus
grouping only.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@arvinxx arvinxx merged commit c809659 into canary Jun 1, 2026
35 checks passed
@arvinxx arvinxx deleted the feat/topic-group-by-status branch June 1, 2026 11:44
@arvinxx arvinxx mentioned this pull request Jun 3, 2026
arvinxx added a commit that referenced this pull request Jun 4, 2026
# 🚀 LobeHub Release (20260604)

**Release Date:** June 4, 2026  
**Since v2.2.1:** 88 merged PRs · 11 contributors

> This week brings Execution Devices out of the lab — run agents and
Claude Code on any configured local or remote machine — alongside Claude
Opus 4.8, token-usage analytics, and Page sharing.

---

## ✨ Highlights

- **Execution Devices** — Pick where an agent runs. Desktop and CLI
devices auto-register with a stable machine ID, route through the
gateway by channel, and surface a device switcher in the chat input. Run
remote Claude Code on a configured device, with a recent-directory
picker you can drag to reorder. (#15300, #15315, #15322, #15343, #15351,
#15371)
- **Claude Opus 4.8** — Day-one support for Anthropic's latest model.
(#15314)
- **Token-usage analytics** — A new token-usage mode on the activity
heatmap, backed by a denormalized topic usage/cost rollup so totals stay
accurate without recomputing from messages. (#15365, #15417, #15425)
- **Page sharing** — Share a Page through a dedicated document share
flow, plus new Workspace and Agent share tables. (#15309, #15439)
- **Self-iteration agents** — Agent Signal's execAgent migration lands a
server-runtime bridge, async memory writer, and a registered
self-iteration tool package, with a CLI trigger command for testing.
(#15360, #15364, #15392)
- **Knowledge search** — BM25 search now extends to file-backed
documents, and the portal ships an editable CodeMirror viewer for local
files with document highlighting. (#15247, #15298)

---

## 🏗️ Core Agent & Architecture

### Agent Signal & Runtime

- **execAgent migration** — Server-runtime bridge, completion
projection, async memory writer, and removal of the legacy
`executeSelfIteration` path. (#15392)
- Registered the self-iteration builtin tool package and restored the
three mode-specific self-iteration agent slugs. (#15202, #15364)
- Added a CLI trigger command with a golden-snapshot fixture for Agent
Signal. (#15360)
- **Skill priority** — Agent Builder now emits a skill-priority
instruction with matching server runtime. (#15409)
- Retry empty LLM completions instead of silently finishing the turn.
(#15355)
- Classify topic/agent/session foreign-key violations as
`ConversationParentMissing` for clearer recovery. (#15408)
- Persist canonical nested usage/performance on assistant messages, and
re-link orphan tool messages at the raw bucket write boundary. (#15359,
#15438)
- Guard `createAgent` against LLM double-encoded array fields. (#15381)

---

## 🖥️ Execution Devices & Gateway

- Auto-register desktop and CLI devices with a stable machine ID, and
add the `@lobechat/device-identity` package. (#15300, #15321)
- New Devices settings page behind the Execution Device Switcher lab,
with a device switcher shown for all agents in the chat input. (#15315,
#15371)
- `connectionId` + channel routing across the gateway client and device
list; preset the local device on the first LLM request for the 本机
target. (#15322, #15435)
- Run remote Claude Code on a configured device, with drag-to-reorder
recent-directory management and client renders for device tool results.
(#15343, #15351, #15437)
- Preserve content and state across gateway tool calls, and prevent
duplicate streaming from stale reconnects. (#15114, #15354)

---

## 🖥️ CLI & Desktop

- Preserve content/state for connect local file and shell tools; render
the `runCommand` tool result card. (#15441, #15442)
- New `lh topic view` command; CLI now auto-registers its device on
login, matching desktop. (#15340, #15377)
- Resolve CLI tools from the shell `PATH`, and clarify local command
session handling. (#15368, #15389)
- Relocate visual-ref helpers to `@lobechat/const` to fix a renderer
crash; upload `.blockmap` files to S3 for differential updates. (#15326,
#15369)
- Fix a market OAuth expiry that triggered the wrong re-login modal, and
kill dev child processes on parent shutdown. (#15246, #15290)

---

## 🗂️ Pages, Library & Knowledge

- Document share flow with business slot stubs, plus Workspace and Agent
share tables. (#15309, #15439)
- Export Agent profiles as Markdown, preserving an empty agent prompt on
export. (#15312, #15316)
- Editable CodeMirror viewer for local files with document highlighting;
BM25 search extended to file-backed documents. (#15247, #15298)
- Default new Agent-doc files to `.md` and preserve IME composition;
refresh folder data on slug switch and dedupe breadcrumb fetches.
(#15335, #15427)

---

## 💬 Chat & User Experience

- Group-by-status mode for the Topic sidebar; dropped the legacy
session→agentId compatibility path from Topic queries. (#15366, #15378)
- Restore editor focus after the file picker closes, and close the skill
dropdown before navigating to settings. (#15391, #15394)
- Strip markdown tokens from fallback Topic titles; keep an open
ActionBar popup when hovering another message. (#15303, #15372)
- Stabilize home starter loading and stop transliterating model names in
the home starter; show artifact source while streaming. (#15310, #15324,
#15386)
- Group the sidebar spacer with recents and agents. (#15373)

---

## 📊 Analytics, Tasks & Notifications

- Token-usage mode on the activity heatmap, backed by a denormalized
topic usage/cost rollup. (#15365, #15417, #15425)
- Push: new `PushChannel`, receipt cron, and `pushToken` tRPC API.
(#15233)
- Tasks now support file and image attachments. (#15141)

---

## 🧩 Models & Providers

- Support Claude Opus 4.8 and configurable model routing with starters.
(#15314, #15384)
- MiniMax M3: new model entry and an Anthropic video runtime. (#15380,
#15403)
- Add `intern-s2-preview` with `thinking_mode`, and `step-3.7-flash`
support. (#15308, #15317)
- Block disabling the official provider; fix default provider setup in
business mode. (#15379, #15382)

---

## 🎨 UI & Modals

- Migrate modals to `@lobehub/ui/base-ui` (LOBE-9711 + eval batch),
including the create-custom-model and feedback/changelog modals.
(#15401, #15416)
- Restructure confirmModal title and content across deletion flows;
polish the service-model form and migrate its Switch to base-ui.
(#15426, #15440)
- Wrap the BlueBubbles bridge config into a connection card; update
`@lobehub/ui` to v5.15.5. (#15325, #15342)

---

## 🔒 Reliability

- Replace hardcoded `session_context` values with template variables in
credentials. (#15352)
- Point `CHANGELOG_URL` to `/changelog`. (#15428)

---

## 👥 Contributors

Huge thanks to **11 contributors** who shipped **88 merged PRs** this
cycle.

@hezhijie0327 · @qybaihe · @sxjeru · @arvinxx · @Innei · @tjx666 ·
@lijian · @sudongyuer · @cy948 · @rivertwilight · @AmAzing129

Plus @lobehubbot and renovate[bot] for maintenance.

---

**Full Changelog**: v2.2.1...release/weekly-20260604
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature:topic Topic/Conversation/Session management size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant