T3 Code 0.1.9-netpro2k.1

T3 Code 0.1.9-netpro2k.1 rebuilds the revised seven-patch fork stack on exact upstream v0.1.9 (24e77473ecf41bc1f7142529c7911c1c1aae1d76). This revision supersedes the original 0.1.9-netpro2k draft; that draft and its artifacts remain preserved as backup. Later upstream/main commits are excluded apart from the explicit unchanged pingdotgg#21661 backport described below.

Release remains on hold. This draft requires a new explicit approval of this exact rebuilt candidate before publication.

Upstream highlights

• New T3 Connect sign-in approval for external agents, including approval on app.t3.codes without copying a pairing code.
• New native OpenCode goals, synchronized across clients on OpenCode 2.2.5 and later. Use /goal in the composer; pause and resume are supported.
• New screen-reader announcement settings in Settings → Chat for turn status, completed messages, and agent steps.
• Expanded Usage → Limits support: Muse session/weekly limits after its first thread, plus xAI and Antigravity accounts from configured CLIProxyAPI hubs.
• Improvements to attachment uploads, pull-request deep links, GitLab reviews/reverts, image visibility, and preview layout.
• Fixes for long-thread memory and database reads, provider switching, queued turns, Desktop shutdown, and stable-release notes.

Upstream release and full changelog

Revised fork stack

Source: 3586b387d967bccdf2f8605bf3cba99d7c9df962.

The mandatory packaged-Desktop attachment patch has been removed, including private Desktop authentication provisioning/renewal, attachment IPC/contracts, and obsolete monitoring/update assumptions. Upstream's Local environment default is unchanged. Before eventual migration or installation, manually turn Local environment OFF and pair the same-home background service as a normal saved environment. Standard paired-credential expiry applies; renewal is outside this revision. No live settings have been changed.

Saved-host file/editor/Finder actions and pickers come from an unchanged backport of upstream pingdotgg#21661, commit 52d621a6f10f5a80ec433e3f3515eafbeabac74b. Its stable patch ID is cc88916f64a43b4ee7edfec00fa84c08fd62d4ee, identical to upstream. It reuses the existing host environment identity and destination-specific editor configuration, and should be dropped once the selected upstream base includes it. File intake, folder references, and uploads are unchanged.

Agent browser uses upstream streamed server Chromium. No unpublished native-browser repair from Studio's old 0.1.8 branch is included. Independent background-service installation/update/readiness/cutover, fork update feeds, signing, and release automation remain. Grok skill/session behavior, package-manager recency, and per-instance native Claude policy remain reachable and unchanged.

The audit compared the original 4f1d222148 stack with this rewritten source and traced production consumers for all seven patches. No old attachment commits were merged back. The original ready claim, source ref, receipts, and draft remain preserved separately.

Verification

• Required vp run check:changed ba787dfe598da457c29586d6c5110d3b4354e21d passed on Oma: 7,799 tests across 368 files, three existing skips, five Node tests, all 41 affected package typechecks, and React compiler checks for 255 files (260 compiler tests).
• Focused Oma checks passed: 62 saved-host file-action tests in three files and 55 OpenCode/maintenance tests in two files. All five release-state Python tests passed.
• Studio's earlier wider run remains recorded as non-green: four unchanged OpenCode maintenance tests failed (unknown versus current), with 675 tests passing and nine skipped as reported by the source author. Oma reproduced exactly those four failures using a process-local seven-day npm release-age cutoff; the no-cutoff control passed all five selected cases. Studio sets npm min-release-age=7, while Oma has no cutoff. The test refresh callback uses the default age service, and its fake registry response lacks publication timestamps required by the cutoff path. This is a configuration-sensitive fixture issue; no source, host npm settings, or tests were changed or silently skipped to obtain the required normal-configuration Oma gate.
• Linux x64 AppImage/DEB and signed Mac ARM64 DMG/updater ZIP were built from this exact commit. The Mac app passed strict signature and configured leaf-certificate checks using the existing dedicated identity. These personal builds are not notarized.
• Both standalone server archives passed version, service-launcher, and isolated HTTP-server smoke checks.
• Combined validation passed: both receipts bind to the exact candidate and matching public configuration; asset SHA-256, updater-manifest SHA-512, versions, and sizes match.
• No runtime Electron/client pass was performed, as requested. No Electron client was launched and no login/system Keychain settings were changed.

Publication remains on hold. Only the candidate branch was pushed. Preparation did not move main, publish a release, install into live applications, change live settings, or restart production services. A new explicit approval of this exact rebuilt candidate in its owning thread is required before publication; the original draft's approval context does not apply.

T3 Code 0.1.8-netpro2k

T3 Code 0.1.8-netpro2k

Upgrades this fork from upstream v0.1.7 to the published v0.1.8 release, at bf469bb. Commits newer than that stable tag are excluded.

Upstream highlights

• New voice input on web and Desktop: choose a transcription environment in Settings → Voice, run a local model there, or opt into OpenAI, Grok or OpenRouter cloud transcription. Desktop browser annotations share the same consent.
• New text generators in Settings → Providers: use OpenAI, Anthropic, OpenRouter or an OpenAI-compatible endpoint for titles, commit/PR text and transcript cleanup. Review guides continue to use a coding agent.
• New /clear command starts a fresh provider session inside the current thread while keeping its history and diffs. Scheduled tasks can also start a fresh session on each run in one thread.
• New private secret-request cards keep credentials out of chat. Secret-provider settings and 1Password references are present upstream behind a preview feature flag; this release does not enable that flag by default.
• Model discovery now refreshes when the picker opens; Claude support adds Fable 5.2 and Ultracode choices for Sonnet 5.5 and Haiku 5.5.
• Fixes and performance work improve long-thread completion, sidebar switching and background service/resource-monitor overhead.

Fork patch audit

Seven self-contained patches remain. Upstream's mise implementation replaces the fork's custom resolver and outdated/cache plumbing; npm/Bun release-age filtering and the pnpm opt-out remain. Automatic mise updates now follow upstream's active latest shim/latest-path workflow. Pinned, fixed-version-path, wrapper and unsupported backend configurations remain manual. The upstream OpenCode v1 major-upgrade guard is preserved.

The other six patches retain their reachable behavior: patch-stack/recovery tooling, Grok skills and session modes, mandatory background-service attachment, fork-only update feeds and native publishing tools, per-instance native Claude channel policy, and this draft-approval workflow. The native signer was adapted to upstream's deferred-notarization helper while preserving the existing dedicated keychain.

Verification

All required changed-file checks passed on candidate ba787dfe598da457c29586d6c5110d3b4354e21d (tree 4760e835fbc17cc1209fd5197b7e49b85095c29b): formatting, lint, both knip passes, generated operations, 41 affected package typechecks, 793 test files with 13,883 passing tests / 8 skips, and React compiler checks. Five release-state tests and shell syntax checks also passed.

Linux x64 AppImage/DEB and signed Mac ARM64 DMG/updater ZIP were built natively on oma and Studio. Both standalone archives passed version, service-launcher and isolated-server smoke checks. Receipts bind both targets to that exact commit and the same public configuration; updater manifest sizes and SHA-512 digests passed validation. The Mac application passed strict signature and configured certificate-fingerprint checks. Apple notarization is not configured for this personal channel.

This draft is retained for explicit approval. Preparation does not replace main or install/restart running applications or servers.

Upstream release and full changelog

T3 Code 0.1.7-netpro2k.1

Desktop now reconnects automatically when the background server takes longer to restart during an update. Previously it could stop retrying a few seconds before the server was ready, leaving a startup error until you quit and reopened the app.

This fixes Desktop on macOS and Linux. There are no server behavior changes in this revision. The shared release channel includes matching server builds, so Update Everything may also update older servers; publishing this release does not install or restart them automatically.

T3 Code 0.1.7-netpro2k

Updated the fork from upstream v0.1.5 to v0.1.7.

• Side chats through /side or /btw, with project pinning and archiving.
• Commit-by-commit review in Diff → Commits.
• A combined model and effort picker, plus Markdown source editing in the composer.
• Kiro provider support and upstream performance and reliability fixes.

Keeps the fork update channel, Desktop attachment to the separately managed background server, Grok slash skills and access modes, and installer-aware provider update checks. Grok and Claude now reuse more upstream support while preserving the fork's behavior.

Built from 0920cb3429 for macOS ARM64 and Linux x64. Both standalone server archives passed version and startup smoke tests. Mac packages use the existing signing identity; manifests and file checksums are verified.

T3 Code 0.1.5-netpro2k.1

Fix native Claude update notifications to follow the version its installer actually offers.

• Determine Claude's effective Stable or Latest update channel using its read-only doctor command, then check Anthropic's native release feed.
• Keep unavailable or unrecognized native update information unknown rather than advertising npm-only releases.
• Preserve native Claude's configured home for update commands and isolate version caches between differently configured instances sharing one executable.
• Keep existing npm, Homebrew, mise, and other package-manager handling.

This addresses Studio showing native Claude 2.1.314 as outdated because npm advertises 2.1.316, even though claude update correctly reports the native installation is up to date. The corrected resolver was checked against Studio's real installation and reports installed 2.1.314 / installable latest 2.1.314.

Based on the same official upstream v0.1.5 as the previous fork build. Mac ARM64 and Linux x64 desktop/server artifacts are built from the same source. Use the normal in-app update flow; the installed Claude version and update channel are preserved.

T3 Code 0.1.5-netpro2k

Personal fork release based on official v0.1.5 (6d450a4284852af137b2f3407fddd89eb76e7644). Includes the maintained Grok, provider update-policy, background Desktop attachment and fork release-channel patches.

• Customize the thread details card, including persistent provider usage and context-window information.
• Turn a No Project thread into a project in place.
• Includes upstream Antigravity improvements, Copilot follow-up fixes and the updated Electron runtime.
• Keep Mac and Linux client/server updates on this fork's published stable releases. Upstream and npm releases do not drive fork updates; Stable/Nightly switching is unavailable in fork builds.
• Linux standalone archives include libatomic and its license. Mac artifacts use the same persistent signing certificate as 0.1.4-netpro2k.

Use Update Everything from the installed 0.1.4-netpro2k Desktop client to update connected background services and then the app. Mac ARM64 and Linux x64 artifacts were built natively from the same patched source, with matching public configuration and verified updater manifests. Server archives include SHA256SUMS. Private signing material is excluded from release assets.

T3 Code 0.1.4-netpro2k

Personal T3 Code fork for netpro2k's Mac ARM64 and Linux x64 installations, based on official upstream v0.1.4.

This release establishes the fork-owned desktop and server update channel. It preserves Desktop's local file integrations while attaching to the independently managed server, renews the private local Desktop session automatically, and rejects upstream-only server update requests. npm and upstream nightly publication do not make fork updates available.

The first installation migrates the existing source-run services to T3's service launcher. Subsequent fork releases use the normal client update flow. Mac packages use the persistent local signing certificate; private signing material is not included.

Source: 1454901

Server archives are verified with SHA256SUMS. Desktop manifests include their package checksums. Build and rollout procedure.