Repository navigation
Tags
Tags
v0.4.24 (2026-08-12) WeCom file delivery, session history for web/Feishu/WeCom/DingTalk, and bulk edit for agent environment variables, plus reliable attachment downloads, touch-reachable row actions, slug-derived issue prefixes, and the removal of the legacy agent templates.
fix(chat): decouple the follow-up queue card from the composer chrome (… …multica-ai#6444) * fix(chat): decouple the follow-up queue card from the composer chrome The queue used to restyle the composer on appearance (hasQueue prop flipping rounded-lg to rounded-4xl plus a stronger shadow), which made the input box visibly jump the moment a message was queued. The stack also relied on a three-way implicit contract (-mb-8 / pb-10 / z-10) spread across both components. Now the composer chrome is constant — no hasQueue prop, no conditional classes, only a static z-10 so it always paints on top — and the tucked look is owned entirely by ChatQueue: it slides its own bottom edge under the composer (z-0, -mb-3, pb-4) and insets itself (mx-3) so the stack reads as two distinct layers. The queue chrome itself is lighter and smaller: caption-size muted rows, xs action buttons, border-only card, and an animate-in entrance. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * test(chat): align queue scroller cap assertion with max-h-40 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
docs(changelog): add v0.4.18 release entry (2026-08-04) (MUL-5716) (m… …ultica-ai#6372) * docs(changelog): add v0.4.18 release entry (2026-08-04) (MUL-5716) Add the 2026-08-04 changelog entry across en/zh/ja/ko and bump apps/web to 0.4.18. Co-authored-by: multica-agent <github@multica.ai> * docs(changelog): retitle v0.4.18 around the leaner agent briefing and tighten copy Co-authored-by: multica-agent <github@multica.ai> * docs(changelog): drop the two entries reverted out of v0.4.18 Both changes they described are no longer in the release: - blocked-Issue re-trigger (multica-ai#6155) is reverted by multica-ai#6377, on product grounds - mobile chat realtime fallback (multica-ai#6325) was already reverted on main by multica-ai#6374 Removed from all four locales. Co-authored-by: multica-agent <github@multica.ai> * docs(changelog): correct the new-channel attachment entry to match multica-ai#6330 Co-authored-by: multica-agent <github@multica.ai> --------- Co-authored-by: Eve <eve@multica-ai.local> Co-authored-by: multica-agent <github@multica.ai> Co-authored-by: Bohan-J <bohan@devv.ai>
docs(changelog): add v0.4.17 release entry (2026-08-03) (MUL-5655) (m… …ultica-ai#6311) * docs(changelog): add v0.4.17 release entry (2026-08-03) (MUL-5655) Co-authored-by: multica-agent <github@multica.ai> * docs(changelog): drop the MCP allowlist fix, reverted in multica-ai#6314 (MUL-5655) Co-authored-by: multica-agent <github@multica.ai> * docs(changelog): add the Kimi resume fix from multica-ai#6308 (MUL-5655) Co-authored-by: multica-agent <github@multica.ai> --------- Co-authored-by: Eve <eve@multica-ai.local> Co-authored-by: multica-agent <github@multica.ai>
feat(labels): remove agent labels from the product (MUL-5600) (multic… …a-ai#6245) Label Settings no longer exposes an Agents catalog, so agent labels can no longer be created, renamed, recolored, or deleted from the UI. Removing only that catalog would have left the agent detail settings form with an attach-only label picker pointing at a catalog the user can no longer populate, so the Labels row there goes too. That picker was the only other agent-label surface in the product — the CLI never managed them, and no list, filter, or chip renders them anywhere else. The backend still models the `agent` resource type and keeps its endpoints; this change removes the product surface, not the API. Co-authored-by: Lambda <lambda@multica.ai> Co-authored-by: multica-agent <github@multica.ai>