GatherThread Beta 3

GatherThread 0.1.0-beta.3 — Beta 3

Beta 3 brings the reviewed main-branch changes since Beta 2 into matching server,
Web, connector, plugin and Launcher artifacts. Its authorized rollout covers both
test.gatherthread.cn and gatherthread.cn, using one frozen build while keeping
the two environments' accounts, configuration, databases and secrets separate.
Release and deployment receipts, not these notes, establish publication or live status.

Highlights

• Browse a project's GT Cloud or authorized GitHub branches in a right-hand file
  workspace. Open and close independent tabs, inspect source, preview Markdown,
  PDF and raster images, review additions/deletions and commit history, and save
  permitted changes to your own branch. Teammate and historical branches remain
  read-only; main still requires review and integration.
• Use focused mobile conversation, member, invitation, settings and connection
  pages. Confirm a detected mobile layout or select Mobile/Desktop explicitly in
  General. Phones continue to use an online computer Agent or Cloud Agent, not a
  local installation flow.
• Keep the conversation header compact: one Summaries entry, one Session options
  entry, and an unread-mention jump that disappears after the message is seen.
• Explicitly share a supported native Codex/DSH connection with selected project
  members, within configured daily limits. Sharing is opt-in and requires a
  supported isolated native execution path; unsupported platforms refuse it.
  This preview does not create an automatic Agent team.
• Install the DSH plugin on 0.2.1-rc.2 Web or Desktop with matching install,
  start, repair and version-check commands. The optional peer guard prevents old
  DSH from applying the incompatible current layer. DSH 0.1.7-rc.2 continues to
  use the unchanged published Beta 2 artifact.

“Multi-Agent” describes the planned next step: one person's connected Agents
forming a team and collaborating directly, with further automatic communication
between different members' Agents only after authorization. Those capabilities
will arrive in a later version; multiple integrations or opt-in connection
sharing are not a claim that this team workflow is already available.

See the changelog, product guide and
中文图文指南 for the current workflow.

Matching packages and downloads

• npm: @gatherthread/codex-connect@0.1.0-beta.3 and
  @gatherthread/dsh-host@0.1.0-beta.3, published under the beta channel.
• Source tag: v0.1.0-beta.3; record its full commit and package integrity in the
  publication receipt. Do not overwrite Beta 1/Beta 2 versions, tags or downloads.
• Current Launcher builds contain the matching connector/plugin. The macOS app
  uses numeric version 0.1.3, build 13, and remains ad-hoc signed, not Developer
  ID signed or notarized. Each platform archive retains its own source/checksum
  provenance and is promoted only after its build verification succeeds.

Prefer Connect Codex → Open Launcher or the source-matched download index.
The release marketplace identity is:

codex plugin marketplace add https://github.com/TH060419/gatherthread.git --ref v0.1.0-beta.3 --sparse .agents/plugins --sparse plugins/gatherthread
codex plugin add gatherthread@gatherthread

A source checkout alone is not an installed connector. Follow the
Codex guide to prepare the source plugin and matching local
package before enabling Hooks. The DSH guide describes its
explicit version boundary; the frozen cordis.patch.dsh-0.1.yml is reference-only,
not an automatic alternate layer in the Beta 3 package.

Upgrade and verification boundaries

Deploy matching server/Web files together. Native sharing adds separate
authorization/job tables, and the file workspace adds provider-bound APIs and
write receipts. Take each environment's verified SQLite/cloud-Git backup before
startup migrations; preserve test admission separately. Prefer forward repair
after migration rather than running an older binary against the changed stores.
Do not copy accounts or reset secrets, quotas, registration settings or model
configuration between environments.

Reuse the reviewed feature tests and CI. Run the canonical release gate once on
the frozen candidate, plus package/version/download consistency checks; do not
repeat full test campaigns or model diagnostics on each server. The deployment
handoff records source SHA/tree, artifact checksums, actual process working
directory, loopback readiness and public HTTPS readiness after Caddy's health
interval. Resolve any pre-existing failed service guards before restart; a
package update must not bypass them.

The DSH 0.2.1-rc.2 change has contract, upstream loader-preflight and isolated
browser evidence from PR107. A complete new-version native Web/provider workflow
has not been rerun; earlier 0.1.7-rc.2 native acceptance is not evidence for it.
Native sharing likewise retains its documented platform/authentication probes
and refusal behavior; fictional browser fixtures are not real-provider or
Windows/Linux acceptance. See ADR-0056,
ADR-0058 and
ADR-0059.

The hosted image must be compared against the final frozen build inputs. Reuse
an unchanged image only with its original immutable identity and provenance;
otherwise build the matching image once for both environments. No document or
version label enables a provider, GitHub App or registration service by itself.

GatherThread Beta 2

GatherThread Beta 2

多人讨论、共享开发，多端继续工作。

本次整合 Beta 1 之后已审核的更新：实时 Agent 答复与工作过程、云端 Agent 暂停/恢复与重试、分步 GitHub 设置、精简输入区、邮箱登录启动器，以及带实际代码和运行结果的新手示例。

安装与下载

• 推荐在工作页选择「连接 Codex → 打开启动器」。下方提供 Windows x64 ZIP、macOS arm64 DMG/ZIP。
• npm：@gatherthread/codex-connect@0.1.0-beta.2、@gatherthread/dsh-host@0.1.0-beta.2。
• 产品、连接器和插件版本统一为 Beta 2。macOS 启动器的系统数字版本为 0.1.2 / build 12。
• macOS 采用 ad-hoc 签名，尚未进行 Developer ID 签名或公证。
• SHA256SUMS 和 release-provenance.json 记录安装包校验值及对应源码、构建来源。Beta 1 历史版本不覆盖。

详见 Beta 2 更新记录、中文产品指南和连接 Codex。

本次先更新独立测试服；正式服由用户另行指示后复用同一构建上线。发布记录本身不代表服务器已经切换，实际状态以部署回执为准。

GatherThread Launcher 0.1.1

GatherThread Launcher 0.1.1

通过启动器连接 Codex，无需手动输入终端指令。电脑授权为独立设备，不影响已登录的手机或浏览器。

• 网页自动带入邮箱和正式 / 测试环境，在启动器内输入密码即可连接。
• macOS 安装包只展示启动器和 Applications：把右侧应用拖到左侧 Applications。背景含中英文安全确认与 Hooks 提示。
• Windows 保留 ZIP 安装方式及产品图标。
• 安装包内置对应源码的连接器与插件，旧启动器不会被自动替换。

macOS 版本面向 Apple Silicon，最低 macOS 13.5。本次采用临时本地签名，未完成 Apple Developer ID 签名及公证。首次打开若被拦截，请在「系统设置 → 隐私与安全性」确认「仍要打开」；打开 Codex 后审核并启用 GatherThread Hooks。

---

Connect Codex with the Launcher, without entering a terminal command. Each computer is authorized independently; existing phone and browser sessions remain signed in.

• The website fills in your email and production / test environment. Enter your password inside the Launcher to connect.
• The macOS disk image shows just the app and Applications. Drag the app from right to left; concise security and Hooks guidance is on the background.
• Windows retains the ZIP installer and product icon.
• Packages include the matching source-built connector and plugin. Existing installations are not silently replaced.

The macOS package targets Apple Silicon and macOS 13.5 or later. It is ad-hoc signed, not Apple Developer ID signed or notarized. If macOS blocks the first launch, confirm Open Anyway under System Settings → Privacy & Security. Review and enable the GatherThread Hooks in Codex.

The exact source commit, package SHA256 checksums and build provenance accompany the release assets. No password, account data or API key is included.

Source: 4173e7d01f3a478c324371a916e7a30fec20ad2d.

Native Windows and macOS builds passed quality run 38390772898. The macOS asset provenance is generated by the builder; Windows includes a complete internal file checksum manifest. Release checksums identify the exact uploaded archives.

Codex Launcher 修复版 · 2026-10-12

Codex 启动器修复版

新流程：在 GatherThread 项目中点击「连接 Codex」→「打开启动器」，邮箱、项目和正式/测试环境自动带入；只需在启动器输入账号密码。连接器作为独立设备授权，不影响电脑浏览器和手机同时登录。

• 桌面优先显示启动器，终端连接收起为备用方式。
• 修复 Windows/macOS 图标及授权取消、弹窗重开行为。
• 密码不保存、不进入网页链接、命令行或日志；旧版正式服连接链接保留兼容。

下载

• Windows x64：GatherThreadLauncher-Windows-x64.zip
• Apple Silicon Mac：GatherThreadLauncher-macOS-arm64.zip，最低 macOS 13.5。
• 各安装包附 SHA-256 校验和及公开构建来源记录。

Windows 解压后运行 Install.cmd；Mac 将应用移到「应用程序」后首次打开，按系统提示确认来源。Mac 当前为 ad-hoc 签名，尚未 Apple 公证，请仅使用本仓库的可信下载包；Intel Mac 本次未提供安装包。

本次为独立启动器修复发布：连接器/npm 版本仍是 0.1.0-beta.1，没有覆盖既有 tag、Release 或 npm 包。新邮箱密码流程需配套服务器接口；本轮更新对象是测试服，不代表正式服已升级。

English

Open Connect Codex in your signed-in project, then Open Launcher. Email, project and the exact production/test environment are prefilled; enter your password only in the native Launcher. An independent device credential keeps your other browser/phone sessions signed in. Passwords are not stored or put in links, command arguments or logs.

This repair includes branded Windows/macOS icons, pending-claim cancellation and safe Web dialog reopening. Windows x64 and Apple Silicon Mac packages are provided; the Mac package requires macOS 13.5+, is ad-hoc signed and not notarized. No Intel Mac package is claimed. Existing v1 production links remain compatible. The new email flow requires matching server endpoints; this rollout targets the isolated test service, not production. npm and existing release assets remain unchanged.

GatherThread Beta 1 · 多人多端多 Agent

GatherThread 0.1.0-beta.1 — Beta 1

Beta 1 brings the changes merged since Alpha 8 into matching npm packages and the isolated test service. It retains the current main implementation, including its safety gates. This release does not authorize or describe a production upgrade at gatherthread.cn.

The earlier, unpublished pre-Alpha candidate reused this version name. Its original planning record is preserved separately in pre-alpha-beta.1-candidate.md; it is not this release.

Highlights

• Verified-email registration and password sign-in replace user access-token login, qualification activation and invitation-created accounts. Email-code password recovery has an independent operator switch; no old-account inheritance is offered. Project invitations now grant membership only after sign-in.
• One account can use independent computer, phone and tablet browser sessions at the same time, with per-device revocation. Password resets revoke all previous devices and Agent authorizations.
• The compact phone/tablet workspace folds projects, members and tools into sheets and combines Agent/model/reasoning choices in a small selector. Mobile users can request their own connected computer Agent while that computer and connector remain online. Desktop controls remain distinct.
• Bilingual beginner guides now follow the current computer and mobile flows, including GitHub file collaboration. Practice remains isolated from real projects, credentials and model usage.
• Direct local GitHub synchronization is available alongside GT Cloud. Each authorized member uploads to a stable personal branch; new GitHub connections default to idle automatic upload. Files travel directly to GitHub without using GatherThread cloud file storage. Downloads, recovery and merges remain explicit.
• The request button becomes Pause/Resume during eligible local Agent work; continuing creates a new exact-profile request rather than promising lossless native-turn continuation. Conversation history, local upload choices and visible-history import remain independent.
• Account avatars use a bundled allowlisted catalog, preserve historical display names and distinguish members' Agents. Profile refresh cannot delay permission or realtime state updates.
• The product home and illustrated documentation now emphasize working together across devices with each member's Agents. The new home preserves same-origin /app/ entry, bilingual preferences, accessibility fallbacks and filing links.
• Isolated test admission, private account/device state, separate service templates and test-labeled email flows support checking the same build before a separately authorized production promotion.
• Hosted Agent and cloud GitHub task implementations add request/authorization fencing, budget retention, bounded source handling and reviewed publication paths. Beta 1 opens both cloud trial and eligible GitHub repository-task Web entries. Server runners remain default-closed until private provider/image/App configuration and real test-host validation pass; local Codex remains the default.
• The reviewed free-model preset covers six zero-price tool-capable SiliconFlow candidates, including ChinaTelecom Xing4.0-29B. Operators can expose only individually validated models through a strict subset; paid/Pro, retired and specialist-only models are excluded. Adding model choices does not increase shared account or host capacity.

Fixed source and packages

• Source reference: v0.1.0-beta.1, once the reviewed tag has been created and verified.
• Codex connector: @gatherthread/codex-connect@0.1.0-beta.1.
• DSH plugin: @gatherthread/dsh-host@0.1.0-beta.1.
• npm distribution channel: beta; use the exact versions below rather than assuming latest selects Beta 1.

codex plugin marketplace add https://github.com/TH060419/gatherthread.git --ref v0.1.0-beta.1 --sparse .agents/plugins --sparse plugins/gatherthread
codex plugin add gatherthread@gatherthread
npx --yes @gatherthread/codex-connect@0.1.0-beta.1 --help
npx @deepseek-ai/dsh@0.1.2-rc.1 plugin --profile web add @gatherthread/dsh-host@0.1.0-beta.1

Plugin installation does not start a connector or trust Hooks. Follow Codex setup or DSH setup, use the selected environment's address, and review local permissions. Existing connectors need restarting to use the new package. The optional Launcher v1 supports only https://gatherthread.cn; the test site uses the workspace's manual terminal command without widening that URI contract.

Source, tag, npm publication and deployed service are separate artifacts. The release index records their boundaries; deployment acceptance must name the actual full commit and artifact checksum.

Release verification

Use Node.js 24 or newer and a clean checkout of the fixed reviewed source:

npm ci
npm run release:verify
npm run release:pack-npm
npm run release:dry-run-npm
git diff --check

Verify the packed connector and DSH plugin from Git-less installs, registry versions after publication, and the current Linux/macOS/Windows CI for that exact source. Native Codex/DSH, real email/challenge providers, optional Linux containers and browser smoke tests are separate checks, not implied by fixture tests or a successful build.

Test-only deployment

Target https://test.gatherthread.cn using TEST_ENVIRONMENT.md. Testers first enter a privately issued admission code, then register or sign in with their independent test email account. The same email can separately register on production; passwords, data, devices and credentials must not cross environments.

Build from the final reviewed full SHA with scripts/test-environment/prepare-candidate.sh. Verify that archive and its SHA256, deploy it only under /opt/gatherthread-test/releases/, and leave production units, /opt/gatherthread/current, production data and secrets untouched. Before switching the test release, verify paired SQLite/cloud-Git and admission backups, isolation reports, restrictive permissions, disk capacity, TLS, loopback readiness and restore behavior. Registration/recovery require the test environment's approved providers and their own preflight; the release process does not silently enable them or either cloud server runner. Cloud Web entries are open, but model/image/App configuration and host-resource acceptance remain separate activation requirements.

After activation, record the actual commit/checksum and verify admission denial, registration/login, two-browser replay, independent device revocation, invitations, local Codex/DSH connection, selected model routing, summaries, file permissions and mobile reading. Use only approved test accounts, repositories, workspaces and any explicitly authorized model calls. A green test deployment does not automatically promote production.

Cloud activation additionally follows the test-host operator preflight: host-visible TMPDIR under /var/lib/gatherthread-test/hosted-tmp while retaining PrivateTmp, reviewed Docker access under the actual systemd service UID, immutable image and real tool-call/coding smoke. The test template caps either task container at 512 MiB, disallows additional swap and starts host/user concurrency at one. GitHub tasks also need an independent test App/callback and eligible coding model. Keep the existing host size and measure complete tasks plus production responsiveness; refuse tasks that cannot run safely. The original default memory ceilings remain 768 MiB for trial and 2048 MiB for repository tasks. API/App secrets stay only in restricted host configuration. Do not weaken sandboxing, expose the Docker daemon or relax its socket permissions to get a smoke test to pass.

Migration and rollback

• Stop all previous processes before migration and keep the complete pre-upgrade backup. New email-account tables are additive, but old token/qualification/guest flows intentionally return 410 account_flow_retired; old account Cookies cannot sign in. Historical rows are retained without enrollment or account merging. Independently authorized native credentials remain separate.
• Preserve the existing account pepper, and test admission pepper/Origin, across a compatible test upgrade. Do not copy production credentials, databases or Git objects into test. Password reset, account deletion and later restore must retain device-revocation/deletion records.
• Deploy matching server/Web assets together. Cloud GitHub source migrations redact retained task inputs and fence older OAuth/binding attempts; hosted budget migrations preserve accepted daily charges and active reservations. Do not run an older task runner against the upgraded database. Details remain in HOSTED_GITHUB.md and HOSTED_AGENT.md.
• Do not erase connector state, outboxes, Hook registries or recovery journals to bypass compatibility errors. A downgrade must not resume a context-recovery state with code lacking its guard.
• Code rollback is safe only when the prior binary supports the current schema and security model. Otherwise close test traffic, stop the service and restore verified test application/Git/admission backups to new paths, reapplying later deletions and revocations. Never reopen legacy account endpoints or overwrite incident evidence. Production is not part of this rollback.

Known limits

• One authoritative Node.js process/SQLite database; no automatic failover or distributed worker scheduler.
• GT Cloud remains a limited source-file service. GitHub avoids its storage quota, not GitHub rules or local transfer safeguards. Concurrent Agents need separate working copies; neither branch system is a filesystem lock.
• Native DSH compatibility stays pinned to the reviewed Host path. ...

GatherThread 0.1.0-alpha.6

GatherThread 0.1.0-alpha.6 preview

0.1.0-alpha.6 is a private Alpha preview of 共序 / GatherThread focused on exact-runtime recovery and runtime-advertised DeepSeek Harness model selection. It retains the complete collaboration, Codex, DeepSeek Harness, Web, security, and deployment-preview feature set from earlier Alphas.

What changed

• DeepSeek Harness runtimes may advertise the models and reasoning efforts they can actually execute. The GatherThread work page then lets the user select those values for each new Agent request instead of pinning the connection to one model and effort.
• The verified deepseek-official DSH integration discovers models through the Host's public LLM services and applies the selected model and reasoning effort only for the requested turn. The previous native selection is restored afterward.
• Unsupported, legacy, non-DeepSeek, or ambiguous DSH runtimes remain fixed and fail closed; GatherThread never silently routes a request to another runtime, provider, model, or reasoning effort.
• Runtime execution profiles are persisted and transported through the protocol, server, bridge, Web client, and DSH plugin with compatibility behavior for older runtimes that do not advertise profiles.
• Agent claims now use bounded lease recovery. Accepted progress renews the claim, only the recorded runtime may reclaim a lapsed attempt, and exhausted recovery produces a visible failure instead of a permanently pending request.
• A failed Agent response can be retried with its exact recorded harness, provider, model, and runtime.

Private collaborator quick start

git clone https://github.com/TH060419/gatherthread.git
cd gatherthread
npm ci
npm run release:verify
npm run connection:local
npm run owner-host:init -- --display-name "Alice" --device-name "Alice laptop"
npm run owner-host

Open http://127.0.0.1:18787 and use the one-time owner device token printed by initialization. Then follow the in-app Connect Codex or Connect DeepSeek Harness guide.

Fixed-version integrations

• @gatherthread/codex-connect@0.1.0-alpha.6
• @gatherthread/dsh-host@0.1.0-alpha.6
• Git ref v0.1.0-alpha.6

codex plugin marketplace add https://github.com/TH060419/gatherthread.git --ref v0.1.0-alpha.6 --sparse .agents/plugins --sparse plugins/gatherthread
codex plugin add gatherthread@gatherthread

The npm packages and Git ref are separate release artifacts. Do not use the fixed Git command until the reviewed v0.1.0-alpha.6 tag exists.

Release gates

Run with Node.js 24.16.0:

npm ci
npm run release:verify
npm run test:dsh-npm-plugin:real
npm run release:pack-npm
npm run release:dry-run-npm
git diff --check

Known limitations

• Dynamic in-workspace model and reasoning selection is enabled only when an exact compatible DSH runtime advertises those execution profiles. Other DSH providers continue to use their native fixed selection and settings.
• The verified DSH npm Host surface remains @deepseek-ai/dsh@0.1.2-rc.1; incompatible upstream APIs are rejected safely.
• The hosted GatherThread service, public registration, public Beta support, and automatic trust of Agent Hooks remain deliberately unavailable in this Alpha.

See Connect Codex, Connect DeepSeek Harness, and connection modes.

GatherThread 0.1.0-alpha.5

GatherThread 0.1.0-alpha.5 preview

0.1.0-alpha.5 is a private Alpha preview of 共序 / GatherThread focused on dependable Codex Desktop history visibility, explicit local-to-cloud upload control, and a maintainable multi-developer workflow. It retains the complete collaboration, Codex, DeepSeek Harness, Web, security, and deployment-preview feature set from earlier Alphas.

What changed

• Canonical cloud history can be imported into a verified native Codex Desktop task as readable conversation bubbles without running the Agent.
• Automatic visible-history import supports first-connect and never; new projects default to first-connect.
• Every manual import creates a new local task. GatherThread verifies that task, then switches the durable session binding and Hook allowlist. The user reviews and archives the previous task themselves.
• Empty sessions receive a local-only visibility marker, and oversized histories are compacted within the configured context budget.
• Realtime canonical delta injection remains active and independent from visible-history import.
• Codex and DeepSeek Harness retain per-conversation automatic-upload preferences and an idempotent manual recovery path.
• The Web workspace has compact icon-only controls for both sidebars and session status, uses the top bar for project/session context, and shows Codex history/upload actions only when Codex is enabled for that project.
• Repository-wide AGENTS.md, contribution rules, interface-contract ownership, CODEOWNERS, and a PR checklist keep human and Agent changes reviewable. Every version update remains subject to project-lead review before merge or release.

Private collaborator quick start

git clone https://github.com/TH060419/gatherthread.git
cd gatherthread
npm ci
npm run release:verify
npm run connection:local
npm run owner-host:init -- --display-name "Alice" --device-name "Alice laptop"
npm run owner-host

Open http://127.0.0.1:8787 and use the one-time owner device token printed by initialization. Then follow the in-app Connect Codex or Connect DeepSeek Harness guide.

Fixed-version integrations

• @gatherthread/codex-connect@0.1.0-alpha.5
• @gatherthread/dsh-host@0.1.0-alpha.5
• Git ref v0.1.0-alpha.5

codex plugin marketplace add https://github.com/TH060419/gatherthread.git --ref v0.1.0-alpha.5 --sparse .agents/plugins --sparse plugins/gatherthread
codex plugin add gatherthread@gatherthread

The npm packages and Git ref are separate release artifacts. Do not use the fixed Git command until the reviewed v0.1.0-alpha.5 tag exists.

Release gates

Run with Node.js 24.16.0:

npm ci
npm run release:verify
npm run test:dsh-npm-plugin:real
npm run release:pack-npm
npm run release:dry-run-npm
git diff --check

The hosted GatherThread service, public registration, public Beta support, and automatic trust of Agent Hooks remain deliberately unavailable in this Alpha.

See Connect Codex, Connect DeepSeek Harness, and connection modes.

GatherThread 0.1.0-alpha.2

GatherThread 0.1.0-alpha.2 preview

0.1.0-alpha.2 is the next private, pre-server-deployment preview of 共序 / GatherThread. It retains the complete alpha.1 collaboration, Codex, DeepSeek Harness, Web, security, and deployment feature set while tightening local Codex conversation labels and Windows release verification.

What changed

• New managed Codex Desktop tasks use <session> · MULTI|SOLO · GatherThread.
• Background execution and immutable snapshot titles use the same uppercase session-type label.
• Long cloud session names are truncated before the fixed suffix, so the type and purpose remain visible.
• Snapshot completion metadata now returns the exact native thread title.
• The plugin Hook relay preserves the connector's lexical workspace key across Windows realpath aliases and drive-letter casing differences without weakening workspace containment or Hook-source checks.
• DSH release tests now validate native Windows and POSIX paths consistently.
• Web onboarding contract tests normalize checkout line endings so the same two-line install command is verified on Windows and POSIX.

Cloud and local titles remain separate display metadata. An adopted pre-existing Codex task keeps its own title, and a later cloud rename or mode change does not overwrite an existing local title. Stable project, session, native thread, and verified workspace identifiers remain the binding keys.

Private collaborator quick start

git clone https://github.com/TH060419/gatherthread.git
cd gatherthread
npm ci
npm run release:verify
npm run connection:local
npm run owner-host:init -- --display-name "Alice" --device-name "Alice laptop"
npm run owner-host

Open http://127.0.0.1:8787 and use the one-time owner device token printed by initialization. Then follow the in-app Connect Codex or Connect DeepSeek Harness guide.

Fixed-version integrations

• @gatherthread/codex-connect@0.1.0-alpha.2
• @gatherthread/dsh-host@0.1.0-alpha.2
• Git ref v0.1.0-alpha.2

codex plugin marketplace add https://github.com/TH060419/gatherthread.git --ref v0.1.0-alpha.2 --sparse .agents/plugins --sparse plugins/gatherthread
codex plugin add gatherthread@gatherthread

Release gates

Run with Node.js 24.16.0:

npm ci
npm run release:verify
npm run test:dsh-npm-plugin:real
npm run release:pack-npm
npm run release:dry-run-npm
git diff --check

The hosted GatherThread service, public registration, public Beta support, and automatic trust of Agent Hooks remain deliberately unavailable in this Alpha.

See Connect Codex, Connect DeepSeek Harness, and connection modes.