multica

mirror of https://github.com/multica-ai/multica.git synced 2026-07-05 13:29:44 +02:00

Files

Bohan Jiang a961d63611 feat(slack): make the chat agent explicitly channel-aware (MUL-3871) (#4755 )

Before this, the chat prompt only carried a generic, always-on hint ('if this
came from a chat channel...'), and the task carried no channel signal — so the
agent never definitively knew it was inside Slack. For an ambiguous ask like
'what did you just talk about', it could read Multica instead of the Slack
conversation.

- Thread a chat_channel_type ('slack') signal: the server sets it on the chat
  task response when the session has a Slack binding
  (GetChannelChatSessionBindingBySession); the daemon Task carries it.
- buildChatPrompt now emits an EXPLICIT block only when channel-backed: 'You are
  operating inside a Slack conversation … this conversation and its history live
  in Slack, NOT in Multica … read it with multica chat history, do NOT look in
  Multica.' Web-only chat sessions get no such block (their history is the
  Multica chat_session the agent already resumes).

Tests: slack-backed prompt asserts the explicit Slack/“NOT in Multica”/command
copy; web-only prompt asserts the block is absent.

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

2026-06-30 17:24:46 +08:00

cmd

feat(slack): unified multica chat history pull for channel backfill (MUL-3871) (#4747 )

2026-06-30 16:48:13 +08:00

internal

feat(slack): make the chat agent explicitly channel-aware (MUL-3871) (#4755 )

2026-06-30 17:24:46 +08:00

migrations

feat(autopilot): View/Write permission layer + member access delegation (MUL-3807) (#4695 )

2026-06-30 12:29:11 +08:00

pkg

fix(agent): recover Antigravity reply from transcript when agy stdout is empty (#4744 )