Skip to content

feat(native): AssemblyAI voice and founder inboxes on 0.1.10 with portable Linux desktop build - #62

Merged
nullStack65 merged 3 commits into
release/native-0.1.10from
feat/native-0.1.10-inbox-voice
Nov 17, 2026
Merged

nullStack65 merged 3 commits into
release/native-0.1.10from
feat/native-0.1.10-inbox-voice

Conversation

@nullStack65

Copy link
Copy Markdown
Owner

Why

Jeff's Omarchy desktop runs official 0.1.10, but the native release line here (feat/assemblyai-current, f6ec6450) is still on a 0.1.9 base. The Omarchy candidate (AssemblyAI voice + founder inboxes on 0.1.10) was built and delivered from the private fallback repo. This PR puts that exact source on this fork, so the native line carries 0.1.10 without a mass merge of old fork history.

What

Base release/native-0.1.10 (ca2478f5) is upstream pingdotgg/t3code v0.1.10 (7d32075e) plus one CI commit:

Push and manual runs stay pinned to feat/assemblyai-current, so creating these branches started no runs.

This PR adds three commits, cherry-picked with provenance:

  1. 3bb1475b feat(voice): AssemblyAI cloud transcription, including the Sync endpoint and custom words (word_boost). Same patch as 083270eb.
  2. f3cbc150 feat(threads): founder inboxes (owner/assignee/audience/attention; All/Kameron/Jeff/Shared/Agents picker; All shows everything; organizational only, no access control). Port of PR feat(threads): organize the shared fleet into founder inboxes #59 7ba01581. Three upstream conflicts were resolved by keeping both sides.
  3. 1461341a build(closura): scripts/closura/build-linux-desktop-noble.sh plus a lock of 56 Ubuntu packages pinned to a snapshot. It builds the Linux x64 desktop with noble gcc-13 against a glibc 2.39 sysroot, so scripts/linux-glibc.ts's 2.39 ceiling passes unchanged. It also passes the public cloud keys from .env.example and sets no update feed.

Equivalence proof (no feature loss)

  • Every added and removed line of the voice (122) and inbox (594) patches is identical to the 0.1.9 release line (f6ec6450); 0 lines differ.
  • Apart from .github/ and .gitmodules, this head's tree is byte-identical to 6ebd01cb, the source of the AppImage already delivered and staged on Omarchy:
    • AppImage sha256 a03942458ec8dcd030fb537526115c51107161626dbff02ed709128fcaae0f3d
    • native Electron node-mode node-pty test passed on Omarchy
    • not activated there

Verification of that identical source (local, no paid calls)

  • Typecheck: contracts, client-runtime, provider-core, server and web all pass with 0 errors.
  • Workflow test files: 6 files, 102 tests passed (CloudSpeech, threadInbox, threadMetadataMcp, threadActionMenu.logic, ThreadLaunchService, SubagentProjection).
  • Tests next to every changed file: 30 files, 677 tests passed. Two browser tests weren't run because no qualified browser was available.
  • Builds: server bundle, web build and output verification pass.
  • Clean-room desktop build: run from a fresh worktree of 6ebd01cb using only the committed script, with 0 tracked changes afterwards.
    • The bundled server and web hashes are identical to an independent earlier build.
    • 50 ELF files with a maximum of GLIBC 2.39 and GLIBCXX 3.4.22; node-pty was built by GCC (Ubuntu 13.3.0-6ubuntu2~24.04.1).
    • No update feed is embedded.
  • On this exact head:
    • all 11 static workflow guard checks pass
    • the workflow's own source guard step passes
    • git submodule foreach --recursive exits 0

This PR's ARC run on t3code-ci-arc (4Gi/8Gi) is the remaining real-runner check. I won't call it green before it finishes.

Not in scope

  • feat/assemblyai-current (0.1.9) is unchanged.
  • ASUS and the Air keep their builds.
  • No change to Omarchy, which owns its own cutover.

Task: CLO-866

🤖 Generated with Claude Code

nullStack65 and others added 3 commits November 17, 2026 23:37
Model: gpt-6.1-sol
Task: implementation
Agent: Codex
(cherry picked from commit 083270e)
(cherry picked from commit 7e4faf1)
Port of 7ba0158 (PR59, organize shared T3
fleet into founder inboxes) onto upstream v0.1.10 7d32075 for the Omarchy
0.1.10 host. Organizational owner/assignee/audience/attention metadata and the
device-local All/Kameron/Jeff/Shared/Agents picker only; every thread stays
visible under All. No access control or security segregation.

Conflict resolutions (behavior preserved on both sides):
- project MCP tools: keep upstream clampedPositiveInt import and add
  ThreadInboxRoutingPatch;
- subagent projection: keep upstream `...inherited` (drops delegatedFrom for
  subagents) and add the child agent-only inbox derived from the parent;
- ThreadLaunchService: keep upstream initialMessage/workspaceStrategy and pass
  through optional inboxOrigin/inboxRouting.

Native v0.1.10 free-form thread tags and the client-runtime working/return
inbox sorting are separate upstream features; this port neither replaces nor
depends on them.

(cherry picked from commit 7ba0158)

Task: CLO-866
Model: claude-opus-5-5

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 6b05fae)
The supported desktop build compiles node-pty from source, so on an Ubuntu
26.04 builder its pty.node needs GLIBC_2.42 and scripts/linux-glibc.ts
rightly refuses it (ceiling 2.39). Add a wrapper that keeps that gate and
the build unchanged and compiles with Ubuntu noble's gcc-13 against a
glibc 2.39 sysroot from pinned, SHA-256-verified snapshot packages. It
needs no root, and --provide-build-tools adds noble binutils/make for the
stock noble ARC runner image.

It also pins the inputs the earlier server candidate got wrong: the four
public cloud keys from .env.example (relay URL, Clerk publishable key,
JWT template, CLI OAuth client) are passed, no update repository is set,
the official v0.1.10 native helpers are reused only while native/ equals
v0.1.10, and the version goes through --build-version instead of editing
tracked files.

Task: CLO-866
Model: claude-opus-5-5

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 6ebd01c)
@nullStack65
nullStack65 merged commit eed9ff7 into release/native-0.1.10 Nov 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant