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. A fresh upstream DSH 0.1.2-rc.1 dependency resolution can fail default live configuration reload; the complete isolated native/browser/fake-model flow passes in the explicit startup-only fixture. Follow the narrow startup-mode workaround only for that error; no user's profile is changed by release tests. Very large first history imports may exceed native context; summaries remain lossy, and compaction may consume model quota.
• Manual Codex visible-history import creates a new local task; users review and archive the prior task themselves. Realtime history delivery is not affected.
• Cloud Web entries are open, but model/provider/container and GitHub App validation are required before test execution. Shared-summary generation and Pause/Resume remain local Codex/DSH features. The optional Launcher prototypes are not production-signed/notarized. Provider, filing and live host validation are operator gates.
• The Web's pinned KaTeX 0.16.47 has the upstream Low-severity conditional prototype-pollution advisory. This release does not upgrade that dependency or claim to resolve the advisory; review and rendering/security regressions for the upstream fix (0.18.2 or later) remain a separate prerequisite before production promotion. The standalone Codex npm package does not bundle this Web dependency.