Skip to content

T4 手机 @DeepSeekBot 转交外部 Agent，结果回到同群 #5

New issue
New issue
Open
Open
T4 手机 @DeepSeekBot 转交外部 Agent，结果回到同群#5
Labels
agent:activeAn agent task has an active scoped work claimfeature:messagingMessaging module and external providersready-for-humanRequires human implementationscope:tracerHuman-testable implementation slice

Description

@DoodleBears
DoodleBears
opened on Oct 17, 2026

状态：手机 → 本地 A 模型转交 → 本地 B 模型执行 → 同群结果已合并并有双隔离 Host UAT/native 证据；更广身份/远程撤权、完整 T5 与平台/Human QA 保持开放。 Human 于 2026-10-18 授权合并既有 Draft；不授权 Prod 部署。

Parent

#1

What to build

主人在 DeepSeekBot 桌面显式绑定本地 Bot A 到云群；手机 @A 请求检查，A 转交同群 Agent B，B 在另一电脑完成已授权检查并回报，手机可追踪原始请求与结果。

所有业务走生产目标 owner、持久存储及公开接口；同时交付所需界面、CLI 与回归证据，不交付隔离的横向层。

Acceptance criteria

  • 桌面可连接服务、选择云群并绑定本地 Bot；有相同 DeepSeekBot CLI 入口。只同步选定群，不自动上传本地私聊/Memory/Session/文件。
  • 受信云 actor 经现有 Messaging owner 导入；远端 Human 不作为本机 Human，外部 Agent 不伪造成本地 PersonaBot。
  • 本地 Source Event/placement/Admission 与导入检查点一致提交，持久发送意图保证进程通知丢失可恢复；只本地拥有的 Bot 执行。
  • 手机 Human→A→B 保留原始发起人、目标、请求 ID、授权上限及有效期。B 不因 A 的权限较大而放宽原始 Human 的授权。
  • Cloud Channel 绑定不绕过 Workspace Grant/工具审批；未知或过期身份、权限不足有明确拒绝。
  • 真实模型驱动 A 使用已实现的受限转交能力，B 执行固定 health-check，手机同群看到结果；另有无模型 CLI 工具路径分离协议/Runtime/模型问题。
  • 来源/因果及转交次数有界，Agent 不因结果互相循环。手机可辨识工作状态、执行 Agent 与环境。
  • 复用 Messaging 入站/撤权/Outbox 测试及首个真实 Host/手机 Human QA；T4 只证明正常路径，完整交付仍依赖 T5。

Blocked by

#4 — T3 完成并通过 Human QA。

最初规划阶段的暂不启动约束已被后续 Human 对本任务的 UAT 实施授权替代；Prod、合并、收费仍未授权。

当前完整路径证据（2026-10-18）

Host/mobile #2157 已验证真实手机界面发起 → A 原生模型工具转交 → B 原生模型工具执行固定检查 → 手机同群可见结果。云端序号16/17/18，A执行0、B执行1，原始 Human/截止时间保持；之前两个 Host 重启后工具重放没有新增执行或消息。手机刷新、重启、退出隔离均通过，截图/录屏已发布。

此处两台 Host 是同一 Mac 上独立 Profiles/进程/凭证/数据库，不冒称不同硬件。独立 synthetic staging 登录不重证 Hosted AuthKit/PKCE。完整 T4/T5、Human QA、WebSocket、组织级 Agent 和更广撤权验证仍未关闭；不合并、不动 Prod。当前来源：mobile247a727b8、Hostf02c2423b、cloud3eeed5b、证据d90f28bca。

合并检查点 — 2026-10-18

TOB #17–24 已依次合并，main 44dbb505ae6ba36a82372d7e11f3c356e3651931；DeepSeekBot #2103/#2121/#2131/#2138/#2146/#2150/#2152/#2154 的原始提交由 #2157 整合，main f9ed710b5a718526cc97a30583af80fa14e28424。上述最新 Human 授权取代历史“暂不启动/不合并”描述；未运行的验收仍不算通过。此次没有部署或发布，Prod 未变。

手机 → 本地 A 模型转交 → 本地 B 模型执行 → 同群结果已合并并有双隔离 Host UAT/native 证据；更广身份/远程撤权、完整 T5 与平台/Human QA 保持开放。 本总任务保持开放。

Activity

  1. DoodleBears
    added
    ready-for-humanRequires human implementation
    feature:messagingMessaging module and external providers
    scope:tracerHuman-testable implementation slice
    on Oct 17, 2026
  2. DoodleBears
    added a parent issue on Oct 17, 2026
  3. DoodleBears
    marked this as blocked on Oct 17, 2026
  4. DoodleBears
    added
    ready-for-humanRequires human implementation
    feature:messagingMessaging module and external providers
    scope:tracerHuman-testable implementation slice
    on Oct 17, 2026
  5. DoodleBears
    marked this as blocked on Oct 17, 2026
  6. DoodleBears
    transferred this issue fromBotHarness/DeepSeekBoton Oct 17, 2026
  7. DoodleBears
    added a parent issue on Oct 17, 2026
  8. DoodleBears
    marked this as blocking on Oct 17, 2026

  9. DoodleBears commented on Oct 18, 2026

    @DoodleBears
    DoodleBears
    on Oct 18, 2026
    ContributorAuthor

    Agent work claim

    • Agent: Codex
    • Task: codex/local/01a148ae-ec7f-74b2-8157-961411ce54c9 (not a DSH Session)
    • Issue scope: T4, beginning with bounded A-to-B work forwarding through public API/CLI, preserving the original Human, capability, deadline and one-hop limit; then connect the existing DSH Messaging/Runtime seams for two isolated Hosts. This first protocol step is preparatory, not the completed T4 tracer bullet.
    • Branch: codex/5-work-forwarding
    • Started: 2026-10-18 UTC
    • State: active

    The Human's current autonomous UAT implementation/testing goal supersedes this ticket's original planning-only pause. Keep T3 Human QA, T4 two-Host/model/phone evidence and T5 fault qualification distinct. UAT only; no Prod or merges. Builds on Draft #23. No other claim or overlapping open PR was found.

  10. DoodleBears
    added
    agent:activeAn agent task has an active scoped work claim
    on Oct 18, 2026
  11. DoodleBears
    added a commit that references this issue on Oct 18, 2026

    docs: record UAT one-hop forwarding and independent execution proof

    e7ee2ae

  12. DoodleBears commented on Oct 18, 2026

    @DoodleBears
    DoodleBears
    on Oct 18, 2026
    ContributorAuthor

    Active T4 protocol checkpoint

    Task codex/local/01a148ae-ec7f-74b2-8157-961411ce54c9 remains active.

    Draft #24 runtime864b16d / UAT Workerbc7ed0f3 now proves member→Agent A→independent Agent B→same-channel result through the public protocol. Original Human, capability and deadline preserved; duplicate forwarding and fresh-process replay did not repeat execution; parent execution, second hop and B-local permission denial verified. Exactly six correlated messages were read through the formal CLI. Both test Agent credentials revoked; A/B organization selections restored. Runtime and evidence-head CI passed. Source checks:59workerd/41Node/2wizard plus type/build.

    This is not DSH Host or new mobile evidence. Continuing DeepSeekBot #2155 on codex/2155-cloud-host-binding for native credentials + existing Messaging/Runtime and two isolated Profiles. No Host/native window started. T4/T5 and the overall goal stay open; no Prod or merges.

  13. DoodleBears
    added 3 commits that reference this issue on Oct 18, 2026

    Validate Agent connection identity through public API and CLI

    3eeed5b

    Record real UAT Agent identity qualification

    7037e43

    docs: record phone to two native Hosts UAT qualification

    2a56b4e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent:activeAn agent task has an active scoped work claimfeature:messagingMessaging module and external providersready-for-humanRequires human implementationscope:tracerHuman-testable implementation slice

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions