Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,8 @@ Bots can be pinned as pixel Window Companions that play their replies, binding o

- Bot settings can export and inspect one verified complete `.botharness-backup`, including retained custom/deleted Memory, current attachments, model templates and independent plans, and the canonical purge checkpoint; the installed local command restores only into a new stopped environment ([#886](https://github.com/BotHarness/DeepSeekBot/issues/886), [guide](docs/settings.md#complete-environment-backup-and-restore)).

- Window Companion bubbles follow the displayed pixel bust's head through tilt, stretch and movement, retain an origin connector when cards move to avoid overlap or viewport edges, and keep text upright; resize updates the clamped character and bubble origin together, while image and unsupported-rig fallbacks use their visible box top ([#1177](https://github.com/BotHarness/DeepSeekBot/issues/1177)).

- WeChat identity enablement and native typing can inherit independent global defaults or retain Bot-specific overrides; existing choices are preserved on upgrade, and unsupported group/Thread settings stay hidden ([#912](https://github.com/BotHarness/BotHarness/issues/912), [guide](docs/wechat-connection.md)).

- Isolated AX launches expose bounded, allowlisted real Client startup/runtime evidence and explicit shell readiness for coding agents, retaining first failures across document retries ([#1184](https://github.com/BotHarness/DeepSeekBot/issues/1184), [guide](docs/dev/guides/client-startup-diagnostics.md)).
Expand Down
2 changes: 2 additions & 0 deletions CHANGELOG.zh.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,6 +53,8 @@ Bot 可以作为像素窗口伙伴固定在窗口里播放回复;绑定一个

- Bot 设置可导出、检查一个完整且已验证的 `.botharness-backup`,包含自定义及已删除身份保留的 Memory、当前附件、模型模板与独立计划,以及真实清除检查点;安装包提供的本地命令仅恢复至新的停止环境([#886](https://github.com/BotHarness/DeepSeekBot/issues/886), [guide](docs/settings.md#complete-environment-backup-and-restore))。

- 窗口伙伴气泡随像素半身的头部倾斜、拉伸与移动定位;卡片因避让或视口限位偏移时保留来源连线,文字保持直立;窗口缩小时人物与连线锚点同步限位,图片与不支持的形象使用可见盒子顶部锚点([#1177](https://github.com/BotHarness/DeepSeekBot/issues/1177))。

- 微信身份启停与原生输入状态可分别继承全局默认值或保留 Bot 自定义;升级保留现有选择,界面不显示未支持的群聊/Thread 设置([#912](https://github.com/BotHarness/BotHarness/issues/912),[指南](docs/wechat-connection.md))。

- 隔离 AX 启动向 coding agent 提供有界、白名单化的真实 Client 启动/运行证据和明确 shell 就绪状态,跨文档重试保留首次失败([#1184](https://github.com/BotHarness/DeepSeekBot/issues/1184), [guide](docs/dev/guides/client-startup-diagnostics.md))。
Expand Down
2 changes: 2 additions & 0 deletions docs/architecture/botharness-architecture.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -623,6 +623,8 @@ If an EventSource enters the terminal CLOSED state after a temporary HTTP failur

The Client's independent `CompanionMotion` owns bounded drag poses, velocity sampling, continuous gravity, damped lateral motion, a small floor rebound and settling. View owns the existing frame loop and eases character transforms; bubbles follow the same position. Resizing preserves the current motion and retargets bounds and the drag origin; pointer cancellation matches the active capture. Final landing persists only the normalized horizontal position. Reduced motion returns directly to the floor without pose effects. These are independently implemented presentation dynamics, informed by Coopanion's drag/air/landing interaction rather than imported source or artwork.

For companion consumers, Avatar exposes a disposable anchor reader. It captures the supported head's local top-center once per Avatar replacement, then reads only that local group's displayed screen matrix in the existing visible-frame loop, including outer rotation, scale and transition origin. Activity pixel covers use the same stable head-region point with the SVG root matrix. Images, unknown rigs and unavailable SVG geometry use the visible Avatar box top-center. There is no whole-SVG bounds scan per frame or Host pose RPC. `CompanionBubbles` keeps the original projected point while placing upright cards within viewport limits, above the toolbar and away from other companions; a pixel-style connector preserves the relationship after displacement. Reading keeps its placement continuity and existing grace period. Hidden/offscreen presentation stops sampling, and Avatar replacement/disposal clears the reader ([#1177](https://github.com/BotHarness/DeepSeekBot/issues/1177)).

The application-defined Window Companion owner lives for the Client Plugin lifetime, outside Bot-mode panels, and renders through the official `shell.overlay` Slot. Its preferences are local to the Client origin and the opaque hash of the native `profileContext.dir`; cards never persist. The authenticated Connection Fetch endpoint `/api/botharness/companion` supplies a Profile context and a future-only SSE baseline. A consumer registers and snapshots synchronously in one Host turn, then projects Registry appearance, the existing all-Bot Activity snapshot and owned committed Human–Bot DM output. The Channel store and Session ownership remain canonical; neither drafts nor historical queries enter this first feed.

The application-defined `WindowCompanions` collection owns Profile selection and shared capacity, composing an independent playback owner and motion View per Bot. Sidebar menus and individual Bot header buttons update this collection independently of Channel pinning. Preferences migrate from single-selection v1 to v2 and persist only selections, sources/scope, positions, walking and capacity. Companions share one authenticated SSE; a native random transient consumer ID and same-path POST atomically replace subscriptions. Control handles expire with the stream and are neither identity nor durable authority. Monotonic selection revisions reject superseded baselines; selecting or removing another Bot does not reset a reading list.
Expand Down
2 changes: 2 additions & 0 deletions docs/architecture/botharness-architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -775,6 +775,8 @@ EventSource 在暂时 HTTP 失败后进入终态 CLOSED 时,集合 owner 用

Client 独立的 `CompanionMotion` 拥有有界拖拽姿态、速度采样、连续重力、横向阻尼、轻微地面回弹与落地收敛。View 继续拥有既有帧循环,对人物变换做缓动;气泡跟随同一位置。调整窗口保留当前运动并重新收敛边界、协调拖拽原点,指针取消只匹配活动捕获。最终落地只保存归一化横向位置;减少动效时直接回到底部并关闭姿态效果。这些呈现动力学独立实现,参考 Coopanion 的拖拽/空中/落地交互概念,不引入其源码或美术。

Avatar 为伙伴消费者提供可释放的锚点读取器:每次形象替换只采集一次受支持头部的局部顶部中心,既有可见帧循环只读取该局部组当前显示的屏幕矩阵,包含外层旋转、缩放及过渡中的变换原点。像素 Activity 覆盖使用相同头部区域点与 SVG 根矩阵;图片、未知 rig 或不可用的 SVG 几何使用可见 Avatar 盒子顶部中心。不逐帧扫描整个 SVG 边界,也不向 Host 发送姿态 RPC。`CompanionBubbles` 保留原始投射点,让直立卡片受视口、工具栏与多伙伴避让约束,偏移后用像素式连线保持来源关系。阅读延续既有位置与离开宽限;隐藏/离屏停止采样,形象替换/销毁清除读取器([#1177](https://github.com/BotHarness/DeepSeekBot/issues/1177))。

应用定义的 Window Companion owner 跟随 Client Plugin 生命周期,位于 Bot 模式页面之外,通过官方 `shell.overlay` Slot 渲染。本地偏好按 Client origin 与原生 `profileContext.dir` 的不透明哈希隔离,消息卡片不落盘。受认证的 Connection Fetch `/api/botharness/companion` 提供 Profile 上下文及只处理未来消息的 SSE 基线;消费者在同一 Host turn 同步注册并读取快照,再投影 Registry 形象、现有全 Bot Activity 和拥有者已提交的 Human–Bot DM 输出。Channel store 与 Session ownership 保持权威;草稿和历史查询不进入首个 feed。

应用定义的 `WindowCompanions` 集合拥有 Profile 的钉选集合和共用容量,组合每个 Bot 独立的播放 owner 与运动 View。侧栏菜单与各 Bot 的 header 按钮均操作此集合,与 Channel 置顶无关。偏好从单选 v1 迁移到 v2;只持久化形象选择、来源/范围、位置、走动与容量。多个伙伴复用一条受认证 SSE,通过原生随机的临时 consumer ID 和同路径 POST 原子替换消费集合;控制句柄随流关闭释放,既不是身份也不是耐久权威。递增选择版本阻止迟到的基线初始化被替换的消费;增加或移除其他 Bot 不重置正在阅读的卡片。
Expand Down
45 changes: 45 additions & 0 deletions docs/assets/pr/1177-companion-anchors/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
# Companion anchor resize qualification

Real isolated DSH 0.2.0-rc.1, Chinese, dark theme, the same Ada and Grace QA PersonaBots and Profile. Official Chrome DevTools MCP captured actual pointer dragging, release, keyboard movement and a 1559 × 865 → 600 × 700 → 1559 × 865 resize. Videos are continuous, silent screen recordings, remuxed without re-encoding; screenshots are unchanged captures. No synthetic presentation or message was injected.

- Before: `1ed6dcbd9caf4d179753c03ea930fb34fb8157c3`.
- After: `c946a74981944250376db5f8dc609a09c501072d`, including resize correction `f9fad41a` and integration of main `8940165f`.
- Main integration adds native onboarding content between captures. The center chat is therefore not a matched visual comparison; the same companion geometry and resize interaction are the subject of this check.

| Settled narrow viewport before | Settled narrow viewport after |
| ------------------------------ | ----------------------------- |
| ![](resize-before-dark.png) | ![](resize-after-dark.png) |

The settled screenshots do **not** show the transient defect. A QA-only observer independently compared the displayed head point with the connector origin every 50 ms. It observed one 588.694 px resize mismatch before correction. After correction, all 101 narrow-viewport samples were within 0.012 px; the maximum across all 1,200 samples was 0.710 px. Both recordings include rest, drag, fall and land; the after run contains 11 trusted pointer events and real focused-character arrow-key movement. Sampling cannot prove the absence of all unsampled transients and is not a performance measurement.

[Before recording](resize-before.webm) · [After recording](resize-after.webm)

Console inspection after the correction found no JavaScript errors; the existing form-field id/name browser issue remains. No historical companion message replayed after restart. Other fallback/tool-cover/reduced-motion and reading-stack scenarios retain their separately stated acceptance status in PR #1183; this check does not qualify them.

## Focused reading and reduced-motion release

At `c946a749` (evidence head `5c16fab9`), three new native Bot replies are verified against canonical Channel messages. The first focused-arrival screenshot shows two Ada cards beside Grace's independently sourced card. The later expanded-reading samples retain Ada's two upright cards; Grace's card has expired by then. Autonomous walking was paused through existing native buttons. As the third real card appears, normal public character focus enters reading before tool latency consumes its short lifetime; a subsequent actual MCP hover retains it. This is focused-reading evidence, not acceptance of mouse hover on a moving character. `focused-arrivals-dark.png` and `expanded-reading-dark.png` show those distinct moments.

The actual Bot Settings menu then selects reduced motion; native drag/release leaves both companions settled at bottom865 in every observed post-release sample (`reduced-released-dark.png`). Message cards have expired by that later screenshot; it does not show reduced-motion message reading or the first release frame. All sampled connector origins match their displayed bust anchors, maximum0px in this stationary/settled workload; sampling every80ms is not performance measurement or a guarantee about unsampled motion. Sanitized details: `reading-reduced-qualification.json`.

`reading-reduced.webm` is continuous silent official MCP output, container-remuxed only. Earlier failed attempts are retained privately and excluded: native hover could not stabilize a roaming character; a paused attempt lost its messages to TTL during capture latency. No fake reply/event, replay or card/store injection was used. Console contained no JavaScript error; the existing native form-field issue remained. Held/reversal, image/tool-cover and background scenarios remain separate.

## Latest-main image fallback and real tool cover

Runtime `d1dde91edc4fd01dab9cbaa12a43ed504be68434` integrates main `04da609342f31b613b4102aa716228f00cb3d171` with the formal pixel-avatar `0.6.0`. Both themes use Chinese and 1559 × 865. These are after-state qualification scenes, not new matched before/after comparisons.

The native avatar editor saves Grace's own current seeded appearance. The owning avatar API then uses its identical PNG bytes without an Appearance, exercising actual image fallback. A newly generated canonical DM supplies the bubble; native drag/release is recorded. The owning reset restores the original absent avatar/appearance/seed fields, independently verified against the immutable original detail snapshot.

Ada first sends a new canonical explanation, then calls actual `ask_user_question`. The owning Activity snapshot and pending question confirm the real tool cover. Light and dark captures retain the bubble above the tool symbol, using the head point sampled before the cover and projected through the displayed SVG root. The native question form is then answered, an actual Bot continuation is verified, and the original bust returns. Both QA requests created during setup/capture were completed; the Host status query after completion returns expired, while actual canonical Bot continuations independently prove the submitted selected labels.

Across the five stationary/post-release phases, every 80ms geometry sample with a connector measures 0px origin error. Native movement is in the two continuous silent official MCP videos, remuxed only. This does not qualify held/reversing motion, first-release-frame timing, moving-hover/grace, background, reduced-motion reading or performance. Normal public character focus retains real cards before capture latency exhausts TTL; walking was paused with native buttons. No synthetic replies, SSE, cards or store mutations were injected. Console has no JavaScript errors. All owned test pages and the isolated browser were closed. `variants-qualification.json` records scope and limitations.

| Image fallback: light | Image fallback: dark |
| ----------------------------- | ---------------------------- |
| ![](image-fallback-light.png) | ![](image-fallback-dark.png) |

| Native tool cover: light | Native tool cover: dark |
| ------------------------- | ------------------------ |
| ![](tool-cover-light.png) | ![](tool-cover-dark.png) |

[Image fallback recording](image-fallback.webm) · [Tool-cover recording](tool-cover.webm)
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -0,0 +1,126 @@
{
"runtimeCode": "c946a749",
"evidenceHead": "5c16fab9",
"viewport": [1559, 865],
"theme": "dark",
"locale": "zh-CN",
"canonicalNativeReplies": [
{
"name": "锚点验收 Grace",
"length": 82
},
{
"name": "锚点验收 Ada",
"length": 80
},
{
"name": "锚点验收 Ada",
"length": 80
}
],
"setup": "Autonomous walking paused by native buttons; when three real new cards appear, public character.focus() enters reading before tool/capture latency expires their TTL. No card/store mutation or message replay.",
"phases": [
{
"label": "full-idle",
"samples": 18,
"motion": ["full"],
"bots": [
{
"name": "锚点验收 Ada · 窗口伙伴",
"reading": "false",
"phase": "rest",
"cards": 0,
"bottom": 865,
"viewport": 865
},
{
"name": "锚点验收 Grace · 窗口伙伴",
"reading": "false",
"phase": "rest",
"cards": 0,
"bottom": 865,
"viewport": 865
}
]
},
{
"label": "expanded-reading",
"samples": 36,
"motion": ["full"],
"bots": [
{
"name": "锚点验收 Ada · 窗口伙伴",
"reading": "true",
"phase": "rest",
"cards": 2,
"bottom": 865,
"viewport": 865
},
{
"name": "锚点验收 Grace · 窗口伙伴",
"reading": "false",
"phase": "rest",
"cards": 0,
"bottom": 865,
"viewport": 865
}
]
},
{
"label": "reduced-reading",
"samples": 18,
"motion": ["reduce"],
"bots": [
{
"name": "锚点验收 Ada · 窗口伙伴",
"reading": "false",
"phase": "rest",
"cards": 0,
"bottom": 865,
"viewport": 865
},
{
"name": "锚点验收 Grace · 窗口伙伴",
"reading": "false",
"phase": "rest",
"cards": 0,
"bottom": 865,
"viewport": 865
}
]
},
{
"label": "reduced-released",
"samples": 22,
"motion": ["reduce"],
"bots": [
{
"name": "锚点验收 Ada · 窗口伙伴",
"reading": "true",
"phase": "rest",
"cards": 0,
"bottom": 865,
"viewport": 865
},
{
"name": "锚点验收 Grace · 窗口伙伴",
"reading": "false",
"phase": "rest",
"cards": 0,
"bottom": 865,
"viewport": 865
}
]
}
],
"maxSampledAnchorError": 0,
"p95SampledAnchorError": 0,
"limits": [
"80ms geometry sampling, not frame-time or proof about unsampled transients",
"Public focus setup before real hover; not moving-character mouse usability acceptance",
"Both earlier failed attempts preserved privately: moving target hover timeout, then cards expired during tool latency",
"Reduced-release samples qualify settled floor alignment, not timing of the first release frame",
"Continuous silent official MCP recording, remux only; no synthetic reply/SSE/card injection",
"Does not qualify held/reversing grab, image/tool-cover variants, background or performance"
]
}
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Loading