Skip to content

Releases: nullStack65/t3code

Release list

T3 Code (fork) v0.0.43

T3 Code (fork) v0.0.43 Latest
Latest

Choose a tag to compare

View all tags
@nullStack65 nullStack65 released this 28 Sep 11:16
v0.0.43
929b637

Fork build of T3 Code 929b63795e7696855ada61de5fd359dc2f51da78.

Repository: nullStack65/t3code. Fork version 0.0.43 is the fork's own increasing line.

Assets are checksummed in SHA256SUMS; the frozen fork-release-manifest.json records the source and accepted digests.

Assets 12
Loading

A4 non-production prerelease — patched T3 linux-x64 (f014905)

A4 non-production prerelease — patched T3 linux-x64 (f014905) Pre-release
Pre-release

Choose a tag to compare

View all tags
@nullStack65 nullStack65 released this 22 Sep 23:15
a4-netcup-v0.0.42-f014905
f014905

A4 NON-PRODUCTION prerelease — patched T3 Linux x64 runtime artifact

DO NOT INSTALL / DO NOT ACTIVATE. This is a uniquely identified, non-production
qualification artifact for the Closura Netcup patched-T3 lane. It is not stock
upstream T3 and it is not authorized for live installation or activation.

Source (exact authority)

  • repository: nullStack65/t3code
  • pull request: #2 (draft) — fix(server): opt-in fail-closed policy for codex thread resume
  • exact head: f014905ed1c73600310accc6d2bc378c9d5c7840
  • architecture: MINIMAL_T3_PATCH
  • upstream baseline: v0.0.42 target 719a76ca1dbf5490f1aa33ffb9966301e02be9a9
  • reviewed upstream applicability receipt: 7445aa733ada33e45289e5aa5055f79142556513
  • A3 source contract: nullStack65/closura-agent-config PR pingdotgg#227 head 4fba4019b30e25c1ef2cabcf7ff54700381c73ec
  • Closura consumer/gate: PR pingdotgg#1081 head 1cf2499a45bda75ba9443cd7ab6e43ba3910e466

No source carrier was edited, rebased, or merged to produce this artifact.

Artifact

  • asset: t3-0.0.42-f014905-linux-x64.tar.gz
  • architecture: linux-x64 (ELF 64-bit LSB, x86-64, dynamically linked)
  • bytes: 63959255
  • sha256: 16aea0bc979847939a495c367d2835ed5986798152b16fa34c3de8faae947f82
  • main executable t3 (Node SEA): 161361092 bytes, sha256 f36569e1fe2c5da7475336b1b5a07c5e23ecb368bbe463b0045864fb7c9952b2
  • bundled native: node_modules/node-pty/build/Release/pty.node sha256 be4a738efb303e807b88bab995e0300573eb9cd052ce79ceb31858d497cd3f34

Build (official v0.0.42 CLI/SEA path)

  • Ubuntu 24.04.4 LTS x86_64, glibc 2.39, Node 26.8.2, npm 11.19.1, Vite+ 0.3.0 (vp), Rust 1.98.1, gcc 13.3.0
  • source tree a1604e5f4aa1c778b40d884b2a9ce99122feea73, pnpm-lock sha256 9e66a720b5ed44785cc3f03755bbfc5d0f95149dde96cd4ce4bf25e74b4265e0
  • steps: vp install → node scripts/update-release-package-versions.ts 0.0.42-f014905 → vp run --filter t3 build → cargo build --release native/resource-monitor → node apps/server/scripts/cli.ts build-exe → node scripts/build-cli-archive.ts --platform linux --arch x64
  • two independent clean builds (separate VMs, no shared caches): archives differ only by gzip/tar container metadata plus the workspace path byte embedded in the Node SEA blob; after normalizing the build path the unpacked runtimes are byte-identical (proven: patching the single differing byte reproduces the other build's exact sha256).

Proven (no provider/model/openai call)

  • t3 --help and t3 --version succeed under env -i PATH=/nonexistent (no ambient node/npm).
  • loopback-only t3 serve on 127.0.0.1; GET /api/auth/session → authenticated=false; clean shutdown; not LAN-reachable.
  • artifact-level fail-closed resume, driven through the packaged runtime against a deterministic fake codex app-server (request ledger):
    • default fallback-to-new-thread: recoverable resume failure → thread/start IS permitted.
    • fail-closed: recoverable resume failure → no thread/start in the ledger.
    • fail-closed valid resume → thread/resume only.
    • fail-closed nonrecoverable error → error propagates, no thread/start.
    • fail-closed malformed resume payload → fail closed, no thread/start.

Self-update / pinning rule (consumer)

The runtime does not auto-update. A plain t3 serve exposes no server self-update
capability (null unless desktop-managed or boot-service-launcher-managed). t3 update
is an explicit operator command that targets the upstream pingdotgg/t3code release
index and would install stock T3. Minimum downstream control: keep this artifact in an
immutable, version-pinned directory, run its t3 directly, never run t3 update, and do
not register it with the desktop/boot-service self-update surface.

Non-actions

No live Netcup install; no runtime enable; no paid/model/provider call; no
Cloudflare/Netcup mutation; no deployment; no production mutation; no source merge.
activation.active=false, fallback=null, canary_source_ready=true, OMP active/default.

Loading