Consider it done. The open-source AI agent that works out of the box · 想到,就能做到。开源、开箱即用的 AI Agent。
TypeScript agentai-agentai-assistantandroidclaude-codecodexelectroniosllmmacosreact-nativetypescriptwindows
import { isSharedTaskPeer } from '@cindy/device-link';
/**
* connectionBannerVisibility.ts — ConnectionBanner 可见性判定的决策核。
* 纯函数(不依赖 React / react-native),node 可单测;useShowConnectionBanner
* 只负责传入状态,浮窗统一经过三秒防闪延迟:
* - 没有故障证据的 connecting / 内容同步 / 同步完成 → 标题轻量反馈,不弹浮窗;
* - 请求级 error / 可分类连接问题(鉴权失效、被顶号等)→ 具备浮窗展示资格;
* - 关联设备熔断 open(电脑端未响应)→ 具备浮窗展示资格——relay 可能仍 online,
* 只看 status 的旧判定对「进程活着但内部卡死」的半死态完全失明
* (2026-07 事故:presence 恒 online,banner 一直不出现,用户零信号);
* - 普通弱网断线 → 持续超过防闪窗口才显示(规则 7:杜绝跳变)。
*/
export function resolveConnectionBannerVisibility(input: {
offline: boolean;
connecting?: boolean;
offlineLongEnough: boolean;
hasError: boolean;
hasIssue: boolean;
hasUnstableIssue: boolean;
deviceUnresponsive: boolean;
}): boolean {
return input.hasError
|| input.deviceUnresponsive
|| input.hasUnstableIssue
|| (input.offline && (input.hasIssue || (!input.connecting && input.offlineLongEnough)));
}
/**
* 连接类恢复全部由系统处理,不给用户一个与自动重连并行的“同步”按钮。
* 只有链路已在线、没有连接级 issue,且确实是非自动恢复的请求级同步失败时,
* 才保留手动重试入口。
*/
export function resolveConnectionBannerSyncActionVisibility(input: {
online: boolean;
hasActiveIssue: boolean;
deviceUnresponsive: boolean;
hasRequestError: boolean;
requestErrorAutoRecovering: boolean;
}): boolean {
return input.online
&& !input.hasActiveIssue
&& !input.deviceUnresponsive
&& input.hasRequestError
&& !input.requestErrorAutoRecovering;
}
/**
* 屏幕层持有的请求级 error 是快照:熔断 open 期间的重试失败会把
* DEVICE_UNRESPONSIVE 文案存进去,而探测成功自动关熔断只翻转
* deviceUnresponsive,不会替屏幕清 error(review P1)。熔断已关时这类
* 错误必然是陈旧的——它描述的状态(未响应 + 自动重试中)已不成立,
* 按 null 处理,让 banner 随恢复自动消失;熔断仍 open 时保留原样
* (banner 的 unresponsive 分支优先,error 本就不会被展示)。
* hook 与组件都要用同一份结果,否则会出现「可见但无内容可渲染」的空壳。
*/
export type HomeDeviceFailure = { deviceId: string; deviceName: string; error: string };
export type HomeConnectionError = string | HomeDeviceFailure | HomeDeviceFailure[] | null;
/** Shared task peers have scoped membership checks, not account device presence. */
export function resolveHomeDeviceDisconnected(
devices: readonly { deviceId: string | null; sessionCount: number; available: boolean }[],
selectedDeviceId: string | null,
connecting: boolean,
): boolean {
if (connecting) return false;
const scoped = devices.filter((device) => device.deviceId !== null
&& !isSharedTaskPeer(device.deviceId)
&& (!selectedDeviceId || device.deviceId === selectedDeviceId));
return scoped.some((device) => device.sessionCount > 0)
&& !scoped.some((device) => device.available);
}
/** A recovering device must not mask another device's actionable failure on Home. */
export function resolveHomeConnectionFeedback(
error: HomeConnectionError,
recoveringDeviceIds: ReadonlySet<string>,
describe: (error: string) => string | null = (error) => error,
) {
const failures = error === null ? [] : typeof error === 'string'
? [{ deviceId: '', deviceName: '', error }] : Array.isArray(error) ? error : [error];
// Classify only the raw error's leading code, before adding user-controlled names.
const manualFailures = failures.filter((failure) => !recoveringDeviceIds.has(failure.deviceId)
&& !/^\[DEVICE_UNRESPONSIVE\](?:\s|$)/.test(failure.error));
const effectiveFailures = manualFailures.length > 0 ? manualFailures
: failures.filter((failure) => recoveringDeviceIds.has(failure.deviceId));
return {
error: effectiveFailures.slice(0, 2).map((failure) => {
const message = describe(failure.error);
return failure.deviceName ? `${failure.deviceName}: ${message}` : message;
}).join(';') || null,
deviceRecovery: recoveringDeviceIds.size > 0 && manualFailures.length === 0,
};
}
export function resolveEffectiveConnectionError(
error: string | null,
deviceUnresponsive: boolean,
): string | null {
if (error && !deviceUnresponsive && error.includes('DEVICE_UNRESPONSIVE')) return null;
return error;
}