Connector 0.2.13 / desktop 0.1.9 (preview) — connection review, shared health, GitHub board sync

Connector 0.2.13 · desktop 0.1.9 · source 437ee6a7143a82e32eae1d6a008203b2df072aaf

English

Preview v0.2.13-preview.20261022 from main. Range: v0.2.12..437ee6a7143a82e32eae1d6a008203b2df072aaf. Changes include the behavior and release preparation commits after v0.2.12, pinned to the source above.

Install and validation

After this preview is published, install the Connector from the same pinned tag:

curl -fsSL https://raw.githubusercontent.com/TED-H-com/bat-agent-connector/v0.2.13-preview.20261022/scripts/install.sh | sh -s -- --tag v0.2.13-preview.20261022

Candidate main CI passed: backend and desktop. The wheel matches all 251 tracked Connector source files byte for byte; the wheel and sdist embed the exact source commit above. The clean-checkout sdist contains no local dependency or test-output files.

The documented real isolated updater fixture passed enrollment, upgrade and rollback, preserved the loaded interpreter and journal, and reused a verified repeated stage. It builds local tag substitutes from the candidate package source; it does not install the uploaded wheel or contact live BAT/model services.

Local receipts match six explicit components: wheel, sdist, bundled Dashboard, Linux managed runtime, README source and tracked site source. The full component set does not pass: the published screenshots intentionally remain pinned to v0.2.12, and native desktop installers and site demo have no supported offline producer claim. README/site source receipts do not certify their release captions. Linux deb metadata reports 0.1.9, the Windows installer version resource reports 0.1.9.0, and the app Info.plist in both macOS DMGs reports 0.1.9.

Signing and acceptance: Linux and Windows artifacts are unsigned; macOS artifacts use CI ad-hoc signing, without verified Developer ID/notarization. CI, package comparison, partial receipts and isolated fixtures are separate from operator installation, native-platform, physical-device and live BAT/model acceptance. No such acceptance is claimed by this release assembly. Checksums establish integrity, not an independent publisher signature.

Behavior changes

• Review an existing BAT connection before applying it. A read-only preview shows the configuration changes and source boundary without saving configuration, creating an operation or probing BAT/SSH. Apply checks the reviewed revision and digest, and lost replies retain the original request and key. (#392)
• Keep the successful Adopt and start destination when an earlier view of the same Work is disposed, so view replacement does not discard the pending move to the original Work and Attempt. (#397)
• Use the shared health freshness rule and localized wording in Fleet rows. Producer validity and observation age remain visible; unestablished values stay Checking instead of becoming bare unknown or implying that a machine is offline. Existing reads and probes keep their original ownership. (#396)
• Share explicit BAT profile-directory selection and token-state policy across setup, Connector runtime and native Fleet. Unavailable or unsupported sources retain their reasons instead of scanning unrelated directories or silently changing sources; documented legacy runtime compatibility remains explicit. (#394)
• Use Inventory observation validity for Work readiness, including the last host-attempt time and producer deadline. Renew once per deadline through the existing read and preserve the renewed observation even when the deadline is unchanged; readiness renewal never starts work or retries a mutation. (#398)
• Import and keep a project board synchronized with GitHub issues and pull requests through explicit repository binding and managed polling. GitHub receives read requests only; source closure stays separate from human completion and PM acceptance. Failed or incomplete traversals preserve the previous cards and recoverable import choices. (#322)
• Keep managed browser credentials on the cookie/CSRF path, refuse their use as API or RPC bearer tokens, and pause refused bearer retries until explicit connection recovery. An action-specific permission refusal does not disconnect a valid reader; saved drafts and pending operation keys remain scoped to the original connection. (#383)
• Offer local copying of ordinary drafts from earlier Connector addresses without automatically migrating them or sending requests. Possibly sent requests retain separate warnings and original identities; identity verification gates recovery, while a verified namespace can still offer local copies during a transport outage. (#384)
• Show one scoped health projection across the header and Settings using existing observations, their age and producer deadlines. Unknown, stale, unconfigured and refused states remain distinct from offline. Identity changes withdraw unproven facts, and the health summary preserves focus and reachable conversation controls. (#385)
• Checkpoint preparation preserves existing staging files, directories and links, and retains both paths if the destination appears during cloning. Localized refusal receipts identify kept paths, source-session links and recovery guidance; broken destination links refuse before cloning. (#308)
• Recover a dead local managed Connector in Dashboard while retaining installation identity and operation keys. Windows background launches request permitted job breakaway and report a bounded lifetime warning when the launching job prevents it. (#316)
• Wake uniquely identified idle Tailscale peers before declaring a route unavailable, sharing in-flight wake attempts across aliases with bounded background work and cooldown. (#315)
• Simplify first-run and everyday navigation in English and Traditional Chinese. Host and Fleet diagnosis follow current native route evidence, preserve failure details and withdraw stale readiness rather than repeating an earlier successful check. (#319, #323)
• Keep drafts, selections and operation keys tied to verified Connector identity across port changes, relaunches and same-identity cursor resets. Two independent services retain separate storage; ambiguous legacy scopes are preserved instead of guessed or consumed again. (#318, #333, #336)
• Retain the original PM retry target while an overlapping source refresh moves focus, so an explicit recovery click still applies to its original request. (#328)
• Use one Connector status decision across header, Settings and connection controls, preserving transport, service and source-refresh reasons and the last successful poll time as separate evidence. (#330, #343)
• Explain client write refusals consistently in Work, PM and session forms, without repeating error announcements or treating a source refresh failure as a new operation error. Existing drafts and recovery targets remain available under their original gates. (#332, #376, #379)
• Show the original follow-up admission reason from one decision and preserve the Work draft while admission is rechecked. (#337)
• Keep past setup verification receipts distinct from a host's current readiness, so saved success does not imply that a host is ready now. (#338)
• Retain diagnostics source reasons and observation times in both the on-screen report and its export. (#339)
• Explain PM availability and each profile state using capability/read evidence and the workspace's saved effective runtime route. Previous verification and current readiness remain separate, with evidence times shown once. (#340, #341, #346)
• Share observed session/runtime and version facts across Work, Resources, Results and diagnostics. Unread or partially unknown builds remain explicit, and revisions recorded by past PM runs are labelled as historical facts. (#342, #362)
• Reconcile concurrent private lease-file creation without claiming ownership from an unproven path. (#344)
• Refuse startup when a journal records a newer unsupported data step, before schema changes or checkpointing its WAL, and carry the bounded diagnostic through managed startup. (#345)
• Preserve foreground and selected-Attempt continuity while keeping an explicit Send immediately after IME composition distinct from implicit keyboard submission. (#348)
• Report the loaded build identity from both MCP entry points, independently of files installed later. (#350)
• Share canonical workflow-version validation between desktop updates and agent-skill generation, accepting canonical CRLF checkout endings and rejecting inconsistent declarations. (#347)
• Identify the frontend bytes loaded by the browser separately from the Connector build, and describe mismatches without inventing release ordering. (#352)
• Add read-only rollback compatibility preview for an explicitly selected or default journal. Missing declarations and unversioned credentials remain unknown; preview does not activate a package or change rollback policy. (#354)
• Use one layout decision per Workbench page so preview-layout toggles preserve the selected view and local state. (#353)
• Keep lost acknowledgements and operation outcomes separate from source-read readiness, preserving the original request and explaining explicit recovery clicks blocked by changing gates. (#356, #357, #364)
• Embed verifiable source provenance in wheel/sdist builds and distinguish a managed launcher's bundled build from the service already running, including same-version builds. Conflicting or missing provenance stays unknown; editable installs continue importing source. (#351, #355)
• Provide offline release-component identity checks and candidate capability inventories bound to an exact committed source. Partial receipts, unchecked claims and unavailable native/demo evidence remain explicit and do not certify release acceptance. (#358, #368)
• Reuse completed PM/GitHub observation proofs within veri...

Connector 0.2.12 / desktop 0.1.8 — Windows Fleet tunnel fix

Connector 0.2.12 · desktop 0.1.8 · source 14c62830240148b14a4d28a9c428f7f8b5ba8bf3.

Fixes the Windows native Fleet tunnel launch (#314): the system OpenSSH path was rendered with a mixed / separator (System32\OpenSSH/ssh.exe), so the launched ssh.exe failed the owner/image-path check, was killed and its intent removed every cycle, and tunnels flapped between PROBE_PENDING and down/OWNER_UNPROVEN. The path is now built component-wise and Windows executable paths are compared separator-insensitively (also in the bootstrap policy). Connector 0.2.12 contains no functional changes beyond the version bump; it ships with desktop 0.1.8 as one release.

Install (Linux/macOS):

curl -fsSL https://raw.githubusercontent.com/TED-H-com/bat-agent-connector/v0.2.12/scripts/install.sh | sh -s -- --tag v0.2.12

Backend CI and Desktop CI passed on the source commit (all jobs, including the Windows NSIS build and Windows endpoint oracle). The wheel was compared file-by-file with the source commit (243 files) and the real connector-update fixture (enrollment, upgrade, rollback) passed. SHA256SUMS and release-manifest.json identify every published artifact.

Linux and Windows builds are unsigned; macOS builds use ad-hoc signatures and are not notarized. CI and package inspection do not establish physical-device, real BAT/model or owner acceptance.

Connector 0.2.11 / desktop 0.1.7 — verified installer

Connector 0.2.11 · desktop 0.1.7 · source d7876d64966e7e558a9232af58758568372106c7.

Adds the verified pinned-tag one-liner installer that writes an updater-compatible rollout receipt (#311) and adoption of existing uv-tool installs so batc-update enable works (#313), plus private hosts.d/*.toml overlay fragments (#309), a stable automation facade for external housekeeping sweeps (#310), and the Linux tunnel unit template with pluggable token-file provisioning (#312).

Install (Linux/macOS):

curl -fsSL https://raw.githubusercontent.com/TED-H-com/bat-agent-connector/v0.2.11/scripts/install.sh | sh -s -- --tag v0.2.11

Backend CI: all jobs passed except the repository-wide secrets-scan, which flags test-fixture idempotency keys in commits that exist only on an unrelated branch, not in this source. Desktop CI passed. The wheel was compared file-by-file with the source commit (243 files) and the real connector-update fixture (enrollment, upgrade, rollback) passed. SHA256SUMS and release-manifest.json identify every published artifact.

Linux and Windows builds are unsigned; macOS builds use ad-hoc signatures and are not notarized. CI and package inspection do not establish physical-device, real BAT/model or owner acceptance.

EC-1.1 delivery preview · Connector 0.2.10 / desktop 0.1.6

This preview delivers explicit PM Overview assessment/history and separately granted external conversation reading, together with register opening, provider error and native preflight diagnostics improvements. It also includes compact navigation and retaining proven-unsent instructions as Ideas from the previous merged increments.

Connector 0.2.10 · desktop 0.1.6 · source b44a83abc7d548747983298b8290ab1d544898d6.

The Overview action uses existing configured runtimes with fixed source context and current permissions. Page reads never start model work. External Codex/Claude plaintext histories require separate named-reader grants; original CLI sessions remain read-only, partial coverage is explicit, and source withdrawal hides saved content. Native coding routes, cross-adapter aliases and real-model/mobile acceptance remain separate work.

Checkpoint source-status failures remain unknown instead of being recorded as a clean worktree. Preparing an assessment survives overlapping factual reads; source withdrawal still cancels preparation. The original CI race was reproduced with held replies before the repair.

The original failures and subsequent fixes remain recorded in #295–301 and #283. Fixed-source backend CI and desktop CI passed. Python distributions and all four desktop package payloads were inspected against the exact source commit; SHA256SUMS and release-manifest.json identify every published artifact.

Linux and Windows builds are unsigned; macOS builds use ad-hoc signatures and are validation previews, not notarized releases. CI, synthetic Connector flows and package inspection do not establish physical iPhone/Android, ordinary desktop login, real BAT/model or owner acceptance.

EC-1.1 continuity preview · Connector 0.2.9 / desktop 0.1.5

EC-1.1 continuity preview

Connector 0.2.9, desktop 0.1.5, source 001662eba19cc43a1a5d2085d1f4f9a6fe4a8457.

This preview adds Discussion Back/Forward, safe foreground recovery, shared mobile keyboard handling, early Work next-turn capability notes and explicitly prepared PM continuation briefs. Conversation following also survives late session controls while preserving saved reading positions. A saved brief retains source references, central decision facts, omissions and up to two next steps; later PM turns can reuse it without adopting scope or accepting delivery.

Enrolled preview Connector installations discover this release through their existing user timer. Updates affect future launches; running services, credentials and operation journals keep their existing lifetime. Desktop packages remain unsigned/ad-hoc previews. The previous 0.2.8 release is retained.

The manifest and SHA256SUMS identify all six packages and the exact source. Backend CI and desktop / browser CI passed on this main commit. CI/package evidence remains separate from real BAT/model judgment and physical phone or native owner acceptance.

Connector 0.2.8 / desktop 0.1.4 — mobile Work navigation preview

Workbench on phones now has a full-screen Work list, a direct return link that retains search and position, and browser Back/Forward support for the Results sheet. Reflow keeps the same composer; source withdrawal prevents reopening old Results. Classic remains the default.

Connector 0.2.8, desktop 0.1.4, source 1a5834fe6a42d6cb47048c1bdfc5be8308620a8a.

Enrolled preview Connector installations can discover this release through their existing user timer. Updates change future launches; running services, credentials and operation journals keep their existing lifetime. Desktop packages remain unsigned/ad-hoc previews.

Validation: exact-main backend and desktop/browser checks passed. Package source, native embedded commit and bundled runtime were verified. These checks use controlled providers; physical iPhone/Android and owner live BAT/model acceptance remain separate. The normal sequential full-suite results and original failures are tracked independently.

release-manifest.json and SHA256SUMS identify all six package assets and their source. The prior 0.2.7 release is retained.

Connector 0.2.7 / Dashboard 0.1.3 — automatic-update preview

Connector 0.2.7 / Better Agent Dashboard 0.1.3, from fixed source e94ea547051a059bd040c44a23aff0e24bcd2294.

Existing per-user Linux Connector installations can enroll in automatic updates once. An hourly user timer checks the selected stable or preview channel, verifies the published source and locked package, and switches one version pointer for future launches. Verified rollback disables further automatic application. Running MCP, central and BAT work retain their loaded code and existing operation journals.

This preview also fixes session permission controls becoming available before the complete initial view is ready, which could incorrectly show an offline error. EC-1.1 mobile, continuity and PM requirements are incorporated into the existing plan; their implementation and real-device acceptance remain separately tracked.

Update enrollment and rollback · Backend checks · Desktop, browser and Work-loop checks

release-manifest.json records the exact source, package digests and Connector update compatibility. SHA256SUMS covers the six packages and manifest. Linux and Windows desktop packages are unsigned; macOS packages use ad-hoc signing. These are development preview packages. CI, browser/native fixtures and installed-file verification do not establish real BAT/model or physical-mobile acceptance.

繁中：Linux Connector 可一次啟用自動更新，之後每小時查詢選定通道、驗證固定發布來源並切換下一次啟動使用的版本；回退後會停用自動套用。既有 MCP／central／BAT 工作不被重啟。此版也修正工作階段尚未完整載入時，權限按鈕過早開放而顯示離線的問題。EC-1.1 已納入原計畫，真實 BAT／模型與實體手機驗收仍分開記錄。

Connector 0.2.6 / Desktop 0.1.2 — Work loop preview

This preview brings the complete implemented BAT work loop onto one merged source: create Work, review and adopt a plan, start it, send a second instruction, inspect its fixed Result and diff, run configured verification, and publish a PR from that same Result. Two saved assessments can open a PM discussion draft with their original versions and commits.

It also includes the source-visibility check before cancel/resume and the Fleet deadline-test correction. Requirement acceptance remains an explicit, separate decision. Native CLI/AHP execution expansion and the remaining professional PM plan are still in progress.

Source: f31e7964c627e4b6d3af2e2370e7a38c64a20e25 on main. Connector 0.2.6, desktop 0.1.2. Every download is listed with its SHA-256 and source in release-manifest.json and SHA256SUMS.

The desktop bundles include their matching Python central. Windows/Linux packages are unsigned; macOS packages use ad-hoc signing. This is a development preview, without a production automatic-update channel.

For a standalone Connector with installed commit readback:

uv tool install 'git+https://github.com/TED-H-com/bat-agent-connector.git@f31e7964c627e4b6d3af2e2370e7a38c64a20e25'

The wheel and source archive are also available. A plain wheel reports its package version; the release manifest supplies its source provenance. Existing host, credential, identity and journal data should be retained when upgrading.

Validation is tied to this source: backend CI and browser, work-loop and native packages. The work-loop checks use the real Connector and disk Git with mock BAT/providers. Installation records and live BAT/model acceptance are separate evidence; this release does not claim owner acceptance.