multica

mirror of https://github.com/multica-ai/multica.git synced 2026-07-06 14:00:09 +02:00

Files

J 2688f18aa4 fix(daemon): bound runtime --version probe so one wedged CLI can't stall startup

A Homebrew-installed claude whose bun shim never returns makes
`claude --version` hang forever. Runtime registration probes every
configured agent sequentially on the daemon startup critical path with no
timeout, so that one wedged probe blocks the loop, no runtime ever
registers, the daemon never flips /health from "starting" to "running",
and the desktop is stuck on "starting" with every runtime offline.

Bound each probe with a 10s timeout plus a WaitDelay that force-closes the
stdout pipe (a wedged claude can fork a bun child that inherits and holds
the pipe open, so killing claude alone would not unblock cmd.Output()). A
timed-out probe now returns an error, the loop skips just the broken
runtime, and every healthy runtime still comes online.

MUL-3812

Co-authored-by: multica-agent <github@multica.ai>

2026-06-29 01:12:29 +08:00

cmd

feat(sidebar): per-workspace switcher dot + count unread per issue (MUL-3695) (#4591 )

2026-06-26 13:28:45 +08:00

internal

fix(server): emit issue:updated when failed-task handler resets stuck issue (#4662 )

2026-06-28 13:01:00 +08:00

migrations

fix(squad): inject leader briefing by task flag, not issue assignee (MUL-3730) (#4606 )

2026-06-26 16:01:33 +08:00

pkg

fix(daemon): bound runtime --version probe so one wedged CLI can't stall startup