Consider it done. The open-source AI agent that works out of the box · 想到,就能做到。开源、开箱即用的 AI Agent。
TypeScript agentai-agentai-assistantandroidclaude-codecodexelectroniosllmmacosreact-nativetypescriptwindows
Merge remote-tracking branch 'origin/main' into cindy/sweet-kalam
ylliuuu66db6c2e76ee98
diff --cc apps/desktop/scripts/fixtures/group-control/group-control-fixture.tsxindex 881dad326f,5b9d88cbd5..d57416d94e--- a/apps/desktop/scripts/fixtures/group-control/group-control-fixture.tsx+++ b/apps/desktop/scripts/fixtures/group-control/group-control-fixture.tsx@@@ -6,10 -6,14 +6,15 @@@ import { BotGroupSettingsDrawer } fromimport { BOT_GROUP_SETTINGS_PARAM } from '../../../src/renderer/features/bots/botGroupPresentation';import { refreshBotGroups } from '../../../src/renderer/features/bots/botGroupStore';import { ControlledBanner } from '../../../src/renderer/features/remote-device/ControlledBanner';+ import { applyRemoteSessionActivity } from '../../../src/renderer/features/device-link/remoteSessionActivityStore';interface GroupData {+ workState?: 'thinking' | 'reading-file' | 'testing' | 'waiting' | 'stopping' | 'unknown';+ workRemote?: boolean;+ workParallel?: boolean;+ workLastStopping?: boolean;bodyAnswer?: boolean;+ remoteLimits?: boolean;name: string;members: Array<{ botId: string; name: string }>;messages: number;@@@ -222,12 -258,10 +259,13 @@@ function groupFrom(data: GroupData)? { id: 'p1', status: 'waiting', currentStep: 4, stepCount: 7, currentBotName: 'Pax', currentStepStatus: 'done', kind: planKind }: data.arrangement === 'running' ? { id: 'p1', status: 'running', currentStep: 1, stepCount: 2, currentBotName: 'Nova', currentStepStatus: 'running', kind: planKind } : null,singleSpeaker: true } : {}),- ...(data.bubbles || data.arrangement ? { serverBacked: true } : {}),+ ...(data.bubbles || data.arrangement || data.division ? { serverBacked: true } : {}),+ ...(data.settings ? { autoContinue: false } : {}),...(data.threadUnread ? { threads: threadSummaries() } : {}),- messages: data.bodyAnswer ? bodyMessages() : data.arrangement ? arrangementMessages(data.arrangement) : data.division ? divisionMessages()+ messages: data.remoteLimits ? ['REMOTE_DEVICE_LIMIT', 'REMOTE_TOTAL_LIMIT'].map((runtimeFailureCode, i) =>+ message({ id: `limit-${i}`, sequence: i + 1, kind: 'notice', authorKind: 'system',+ authorBotId: data.members[i].botId, authorName: data.members[i].name, content: '',- noticeCode: 'member-unavailable', runtimeFailureCode, createdAt: T0 + i * MINUTE })) : data.bodyAnswer ? bodyMessages() : data.arrangement ? arrangementMessages(data.arrangement)++ noticeCode: 'member-unavailable', runtimeFailureCode, createdAt: T0 + i * MINUTE })) : data.bodyAnswer ? bodyMessages() : data.arrangement ? arrangementMessages(data.arrangement) : data.division ? divisionMessages(): bubbles ? bubbles.map(m => (data.threadUnread && UNREAD[m.id as string] ? { ...m, threadUnread: UNREAD[m.id as string] } : m)): Array.from({ length: data.messages }, (_, i) => ({id: `m${i}`,diff --cc apps/desktop/scripts/fixtures/group-control/ui-page.mjsindex 3884c9a208,2af1772b33..4465cbc501--- a/apps/desktop/scripts/fixtures/group-control/ui-page.mjs+++ b/apps/desktop/scripts/fixtures/group-control/ui-page.mjs@@@ -21,11 -33,15 +33,20 @@@ export defaultnotCovered:'Sending, round control, real device-link control and revocation, pending interactions, plans and attachments; the bubbles case shows a task snapshot, not a live task; the sidebar is an empty frame',cases: {+ 'remote-limits': {+ about: '#6835: lane-unavailable notices show device and total task limits with recovery advice',+ viewport: { width: 720, height: 700 },+ data: { ...base, sidebar: false, remoteLimits: true },+ },+ 'work-thinking': { about: 'Actual group work status, scenario data: thinking', data: { ...base, messages: 2, workState: 'thinking' } },+ 'work-tools': { about: 'Actual group work status, scenario data: command execution', data: { ...base, messages: 2, workState: 'testing' } },+ 'work-reading': { about: 'Actual group work status, scenario data: file reading', data: { ...base, messages: 2, workState: 'reading-file' } },+ 'work-waiting': { about: 'Actual group work status, scenario data: needs confirmation', data: { ...base, messages: 2, workState: 'waiting' } },+ 'work-stopping': { about: 'Actual group work status, scenario data: stop requested', data: { ...base, messages: 2, workState: 'stopping' } },+ 'work-unknown': { about: 'Remote work with no readable task: generic activity, no invented thinking', data: { ...base, messages: 2, workState: 'unknown' } },+ 'work-remote': { about: 'Authenticated remote target projection, scenario data (not a live device-link run)', data: { ...base, messages: 2, workState: 'testing', workRemote: true } },+ 'work-parallel': { about: 'Two concurrent execution rows, separate task entries and one group stop', data: { ...base, messages: 2, workState: 'testing', workParallel: true } },+ 'work-parallel-stopping': { about: 'Last execution is stopping while the first still runs: the group stop control remains available', data: { ...base, messages: 2, workState: 'testing', workParallel: true, workLastStopping: true } },'body-answer': {about: '#6550: component body is readable; literal punctuation and surrounding Markdown are retained',viewport: { width: 720, height: 700 },@@@ -87,14 -122,22 +127,30 @@@},async check(page, ui) {const definition = this.cases[ui.case];+ if (ui.case === 'remote-limits') {+ const timeline = page.getByTestId('bot-group-timeline');+ for (const [i, code] of ['REMOTE_DEVICE_LIMIT', 'REMOTE_TOTAL_LIMIT'].entries()) {+ const expected = (await ui.t(`bots.groupChat.notice.runtimeFailure.${code}`)).replace('{{name}}', members[i].name);+ assert.ok((await timeline.innerText()).includes(expected));+ }+ return;+ }+ if (definition.data.workState) {+ const state = definition.data.workState;+ await ui.emit('sessionActivity', [{ sessionId: 'fixture-work', phase: 'running',+ workingPhase: ['thinking', 'reading-file', 'testing'].includes(state) ? state : 'processing',+ compactDetail: state === 'testing' ? '检查私聊与群聊的回归结果' : state === 'reading-file' ? '核对群聊状态与任务入口' : '',+ startedAtMs: Date.now() - 83_000, lastActivityAtMs: Date.now(), attention: false,+ gracefulStopState: state === 'stopping' ? 'requested' : 'none', source: 'live' }]);+ await page.getByTestId('bot-group-progress').first().waitFor();+ if (ui.case === 'work-parallel-stopping') {+ const stop = page.getByRole('button', { name: await ui.t('bots.groupChat.progress.stop'), exact: true });+ assert.equal(await stop.count(), 1);+ assert.equal(await stop.isEnabled(), true, 'another running execution must remain stoppable');+ }+ await ui.capture('work');+ return;+ }if (ui.case === 'body-answer') {const timeline = page.getByTestId('bot-group-timeline');assert.ok((await timeline.innerText()).includes('保留 <name>、*literal* 和 & 符号'));diff --cc apps/desktop/src/main/maker-ipc/chatServer.tsindex e76df4b573,b308f9e2d3..23451e0d3d--- a/apps/desktop/src/main/maker-ipc/chatServer.ts+++ b/apps/desktop/src/main/maker-ipc/chatServer.ts@@@ -1436,9 -1871,8 +1871,9 @@@ function createChatServer(local: BotGroconst member = members.find(value => value.id === failure.botId);const cachedCode = failureCodes.get(`${failure.executionId}:${failure.epoch}`);return [{ ...failure, botId: localBot(failure.botId)?.id ?? failure.botId,- botName: member ? memberName(member) : actors.find(actor => actor.id === failure.botId)?.name ?? '',+ botName: member ? memberName(member, members) : actors.find(actor => actor.id === failure.botId)?.name ?? '',- code: !isBotGroupRuntimeFailureCode((row as Record<string, unknown>).failure_code) && cachedCode ? cachedCode : failure.code }];+ // Older servers may normalize a newly introduced category to RUNTIME_ERROR.+ code: failure.code === 'RUNTIME_ERROR' && cachedCode ? cachedCode : failure.code }];});}/** One execution gets one immutable terminal result, regardless of which boundary ends it. */diff --cc docs/dev-rules/protocol-compatibility.mdindex 7493988758,151886a462..cbf7872ec6--- a/docs/dev-rules/protocol-compatibility.md+++ b/docs/dev-rules/protocol-compatibility.md@@@ -3289,14 -3652,102 +3652,113 @@@ Share Server 在创建时保存已验�对应 host。自定义 API 不进入这套策略与新增刷新规则。详细范围及验证见[订阅 Fast 控制交接说明](../subscription-fast-policy.md)。+## 群聊远程任务限额原因(#6835)++既有 `cindy-runtime-error:<code>` detail 与可选 `runtimeFailureCode` 新增安全类别+`REMOTE_DEVICE_LIMIT` / `REMOTE_TOTAL_LIMIT`,不传远程错误正文、设备身份或凭证。+旧客户端不认识新类别时沿用通用失败提示;新客户端消费旧服务器的通用 `RUNTIME_ERROR`+或缺失类别时,仅在本执行端保留同一执行 ID / epoch 的已知具体原因,服务器的其他明确类别优先。+普通回复、话题和分工共用分类与终态提交,不改变重试、租约或权限边界。++跨设备与重启后的具体原因需要 Chat Server 的 detail 解析和 `failure_code` 白名单支持这两个类别;+客户端改动不证明服务端已支持或已部署。未支持时其他查看端保持通用失败,执行端缓存不持久化。+本次不改服务端、数据库、device-link channel 或 Mobile 原生配置。++ ### 聊天通知内容与私聊落点(#7046)++ 聊天推送增量携带 `conversationKind`,新原生端以此区分私聊/群通讯样式,旧端继续使用原通知。手机 `Accept-Language` 只控制服务端固定提示词,真实原文不翻译;云注册到两个服务都保留显式 preview 选择,旧请求缺省 true。完整任务通知预览关闭需要服务端先支持新列/字段;不添加隐私确认或更改默认预览。++ Desktop 在通知点击事件携带可选 `conversationKind: direct`,落入现有时间线的明确私聊模式。`getBotGroup` options、`sendBotGroupMessage` input 与 `manage` 的 read action 的同名可选字段仅用于此模式,主进程读取实际 kind 后确认;普通群入口仍拒绝 direct/channel。私聊不提供群设置、邀请、分工或群话题操作,已读通过既有 read action、发送保留原幂等/引用/附件路径。手机由实际 snapshot.kind 决定私聊标题和单人头像;内部 groups 路径保持旧通知链接兼容,不改变服务器成员权限。此入口补齐通知的阅读/回应,不改伙伴主任务/接管编排。++ ## 伙伴名册的跟进任务链接++ `teammates` 伙伴行的 `links` 在原 `conversation` 链接之后追加 rel `following`,`target` 为+ `{ kind: 'session', sessionId }`,表示该伙伴在跟进的本机任务(伙伴发起的委派子任务与明确接手,+ 扣除解除记录;来源与桌面侧栏「在跟进」相同)。只列在用伙伴、未归档、本机、普通来源且非 Orca+ worker 的任务,按最近更新取前 200 条;伙伴行 `revision` 追加这组 ID 的摘要,变化时照常失效重读。+ 责任记录、委派创建/状态变化都会广播伙伴远程资源变化。++ 旧控制端按未知 rel 忽略,`conversation` 仍是第一条链接,打开聊天不变;新控制端连接旧 Host+ 时没有该链接,任务行不显示标记。Mobile 读取的链接上限由 64 放宽到 256 以容纳这组链接。+ 不增加 IPC channel、请求参数、数据库字段、push 类型或 Mobile 原生配置。++ ## 桌面伙伴来源筛选++ 桌面在读取 `teammates` 名册后,用每个伙伴的 `conversation` 任务 ID 调用既有的+ `maker:bot-delegations:list`。只将 `requestingBotId` 匹配、`childSessionId` 非空的记录+ 作为创建来源;不把接手关系当创建,也不要求远端支持新增的 `created` link。+ 包含活跃和归档任务,实际展示仍由任务列表状态筛选决定;旧版远端也能直接使用。+ 已有 `following` 链接继续提供跟进标记,任务创建关系同时用于远程创建者头像。++ 按电脑 ID + 伙伴 ID 区分筛选,按电脑 ID + 任务 ID 匹配任务;远程头像使用原电脑媒体地址。+ 同一 Host 串行读取伙伴任务记录,关系缓存保留 ID、不保存任务卡正文。委派变更推送与+ 名册变更沿原刷新合并窗口更新;读取失败保留已有归属,成功空结果清空。+ 切账号、撤权、断线后的旧响应仍受原请求代次隔离。只读关系请求失败不重启 relay、+ 不影响其它设备、不重放任何任务操作。不增加 IPC、权限、服务端字段或数据库迁移。++ Task creator filtering resolves built-in Cindy identity through the existing local `listCindyCopies` read,+ which now returns even a single remaining cloud Cindy. The merge settings entry still requires two copies.+ This allows old remote hosts without template metadata to participate in the unified filter without+ changing their wire protocol or triggering any companion merge. Identity is cached with the owner-scoped roster.++ ### 伙伴独立任务的列表归属(2026-10-27)++ `sessions:list/get/get-many` 可选投影 `companion: { id, role, channel? }`,从现有+ `bot_session_links` 读取,不新增数据库列或改运行身份。普通列表仅纳入 `routine/channel`,+ 仍过滤隐藏任务与删除中的伙伴;`canonical/thread/group` 保留伙伴入口。+ 旧远端的普通列表未包含这些任务时,桌面经原有同账号 `history:query/list_sessions`+ 分页读取 `source=bot` 的归属,再用原有批量/单条读取补齐 Session。无权限或接口失败不能+ 清空普通任务;撤权沿原处理路径上报。设备/状态代次失效时丢弃迟到回复,保留其它设备的+ 镜像,不重启链路或重新授权。离线镜像仅保存归属的 id/role/channel,恢复时仍可筛选和显示头像。+++ Mobile follows the same read-only compatibility path for teammate task attribution and independent+ routine/channel Sessions. `taskTeammate` is a client-local display projection (ID/name/avatar), not a+ new wire field or permission. Its slim home cache keeps it with `companion`; optional read failure+ retains that host's previous attribution and successful absence clears it. Account/query invalidation+ and list mutation epochs fence all late results. Home and device list refreshes share this reader.+ Cloud Cindy identities come from the existing owner-scoped `/preferences` profile snapshots, using+ the same exact preset identity helper as Desktop. Only their IDs enter the cloud-home display cache;+ profile bodies are not persisted. This adds no endpoint, database migration or native configuration.++ ## macOS 原生触控板输入++ 本机聚焦的浏览器/插件页可在顶层 HTML 声明+ `<meta name="cindy-native-trackpad" content="touch">`,并用 `data-cindy-trackpad`+ 标记接收触摸的平面元素。宿主将 AppKit 的两指位置映射为该元素的浏览器触摸事件;+ 鼠标位置是落指中心,两轴按触控板物理比例等比映射,按原始抬指/取消结束。+ 映射使用画面长边作为统一距离基准,避免竖屏窄边压缩平移;落指间距与后续位移+ 使用同一比例,未裁切时保持缩放比例、旋转角度和静止手指的位置,不单独加速双指中心。+ 触点在元素边缘停止,越界位移不累计;反向移动立即响应,不要求先退回越界距离。+ 不新增 preload、renderer IPC 或远程请求;插件沙箱仍为零桥,归属与聚焦检查沿用宿主。+ 后台窗口、第三指、页面导航、失焦会取消触摸;原生模块不可用或已有调试会话时保留原输入。+ 旧宿主忽略 meta/属性,继续 wheel 兼容路径;手机、Windows、Linux 不接收本机 AppKit 数据。+ AppKit 鼠标位置固定使用窗口内容坐标;嵌入侧栏须先扣除宿主内对应 webview 的位置,+ 并分别处理宿主与 guest 缩放,再在 guest 内命中检测。独立窗口没有这个偏移,+ 不能单独替代开发版实际侧栏的输入验收。++ `data-cindy-trackpad="contacts"` 可选整帧输入:元素收到 `cindy-trackpad` DOM+ 事件,`detail={phase,touches:[{id,x,y}]}`;坐标相对该元素所属 frame 的 viewport,+ phase 为 begin/change/end/cancel,touches 是仍按下的全部触点。整帧原子投递,避免+ Chromium 把双指拆成单指前奏及等待触摸 ACK。空属性仍投递标准 Touch/Pointer 事件;+ 旧宿主按旧路径工作,插件仍保留标准触摸处理。只有宿主向页面投递数据,没有反向特权桥。++ contacts 在每次 begin 投递前核对原元素仍连接、仍声明 contacts,且仍是落指锚点+ 命中的元素(在元素所属 Document/ShadowRoot 内检测)。目标被替换、移除或遮挡时,+ 向旧元素发送 cancel(断开的旧元素也可接收清理),停止旧采集并重新命中;下一原生采样+ 可在新目标开始,不依赖再次移动鼠标。旧目标迟到的失败回复不能撤销后来的目标。+ 取消、释放 CDP object 完成后才 detach,沿用现有采集代次,无新队列或持久状态。++ 标准 Touch 路径完整结束与取消使用空 `touchPoints`。当前打包 Chromium 默认 WebTouch+ 路径的部分抬指使用 released IDs;仅发送剩余触点的 touchMove 不会释放缺失手指。+ 这与 contacts DOM 事件始终表示「全部仍按下触点」的约定不同;以真实 Electron 的+ 部分抬指、完整结束和取消回归核对,不能只靠 CDP mock 推断浏览器行为。++ ## 主人请求跨任务连续性(2026-10-28)++ 沿用可选 `requestSource.ownerVerified` 和持久 `autoReviewUserText` 回执,不新增字段或 migration。+ 伙伴私信开始携带当前已接受的主人请求;原话与正文包装仍按旧接收端的逐字验证。无原话时不传空回执。+ 当前接受的核实回执可继续转交,`agent-request` 与 `delegated-continuation` 的审核投影保持同一原话。+ 旧接收端仍可能丢弃核实状态或把接收回复标成私密;完整修复需要执行交接的宿主升级。+ 账号、群与 IM 发言人校验、权限档、Plan、输入代次和撤销校验保持不变。+ 不改变连接恢复或重放策略;单次派发失败只影响该请求,不重启连接或扩大设备访问。