Skip to content

fix(relay): accept delegated thread IDs in activity routes - #12484

Merged
juliusmarminge merged 2 commits into
mainfrom
fix/relay-long-thread-ids
Sep 18, 2026
Merged

juliusmarminge merged 2 commits into
mainfrom
fix/relay-long-thread-ids

Conversation

@juliusmarminge

@juliusmarminge juliusmarminge commented Sep 18, 2026

Copy link
Copy Markdown
Member

Delegated thread IDs can exceed the HTTP router's default 100-character parameter limit, causing valid signed activity updates to miss the route. Raise the relay limit to 512 characters, matching the environment server, and widen both activity and delivery-attempt thread ID columns with a forward migration.

The route regression exercises both ordinary and escaped long IDs through authentication, signature verification, and publication. The 512-character boundary is covered. Applying the full migration history in PostgreSQL/PGlite preserves old rows, accepts 512 characters in both tables, and rejects 513. All 14 API tests, relay typecheck, and targeted lint pass. No visual UI change. The production deployment workflow runs after merging.

Model: GPT-6. Harness: Codex.

Summary by CodeRabbit

  • Bug Fixes
    • Fixed relay HTTP routing for delegated thread IDs that are percent-encoded or up to 512 characters long.
    • Ensured these requests authenticate successfully and preserve the original thread ID and environment metadata when publishing activity.
    • Expanded supported thread ID storage capacity to prevent failures when processing longer delegated thread IDs.

@github-actions github-actions Bot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:XS 0-9 changed lines (additions + deletions). labels Sep 18, 2026
Comment thread infra/relay/src/http/Api.ts
@macroscopeapp

macroscopeapp Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Approved at 7e8e19c

Macroscope's review found this PR approvable — This is a focused relay bug fix that raises the route and storage limits for delegated thread IDs while preserving existing shorter-ID behavior. The migration is backward-compatible, and targeted tests cover delegated and maximum-length IDs.

You can add or adjust custom eligibility rules. Learn more.

@github-actions

github-actions Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider Metric Main baseline This PR Impact PR ceiling
Codex Total thread wire 13.5 KiB 13.5 KiB +2 B (+0.0%) 15.1 KiB
Codex Thread snapshot wire 7.1 KiB 7.0 KiB −3 B (−0.0%) 7.3 KiB
Codex Live turn WebSocket wire 6.5 KiB 6.5 KiB +5 B (+0.1%) 7.8 KiB
Codex Live turn WebSocket decoded 56.2 KiB 56.3 KiB +44 B (+0.1%) 66.4 KiB
Codex Live turn messages 9 10 +1 (+11.1%) 21
Claude Total thread wire 13.5 KiB 13.5 KiB +20 B (+0.1%) 15.1 KiB
Claude Thread snapshot wire 7.1 KiB 7.1 KiB +3 B (+0.0%) 7.3 KiB
Claude Live turn WebSocket wire 6.4 KiB 6.5 KiB +17 B (+0.3%) 7.8 KiB
Claude Live turn WebSocket decoded 57.0 KiB 57.0 KiB 0 B (0.0%) 66.4 KiB
Claude Live turn messages 9 9 0 (0.0%) 21

Baseline: ccad9f6 · PR result: 7e8e19c · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

  • Codex decoded thread snapshot: 114.0 KiB
  • Claude decoded thread snapshot: 114.7 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

@coderabbitai

coderabbitai Bot commented Sep 18, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: bfd472a1-146f-4106-b535-cad8ec4cbdfc

📥 Commits

Reviewing files that changed from the base of the PR and between acfc616 and 7e8e19c.

📒 Files selected for processing (4)
  • infra/relay/migrations/postgres/20260918175607_long_thread_ids/migration.sql
  • infra/relay/migrations/postgres/20260918175607_long_thread_ids/snapshot.json
  • infra/relay/src/http/Api.test.ts
  • infra/relay/src/persistence/schema.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 1 remains after this review.


📝 Walkthrough

Walkthrough

The relay HTTP router now accepts path parameters up to 512 characters. The worker applies this configuration. Relay persistence schemas and migrations support 512-character thread IDs. Integration tests cover UUID, long, and percent-encoded delegated thread IDs.

Changes

Relay thread ID support

Layer / File(s) Summary
Router parameter limit and worker wiring
infra/relay/src/http/Api.ts, infra/relay/src/worker.ts
The relay exports a 512-character router configuration. The worker passes this configuration to the HTTP router.
Persisted thread ID length
infra/relay/src/persistence/schema.ts, infra/relay/migrations/postgres/20260918175607_long_thread_ids/migration.sql, infra/relay/migrations/postgres/20260918175607_long_thread_ids/snapshot.json
Activity and delivery thread_id columns now use varchar(512). The migration casts existing values, and the schema snapshot records the updated database definitions.
Delegated thread routing integration test
infra/relay/src/http/Api.test.ts
The test verifies HTTP 200 responses, activity publication, preserved thread IDs, environment metadata, public keys, null state, and signature verification for UUID, 512-character, and percent-encoded delegated thread IDs.

Priority: ⬇️ Low

Estimated code review effort: 3 (Moderate) | ~25 minutes

Change: Bug fix

Sequence Diagram(s)

sequenceDiagram
  participant Client
  participant HttpRouter
  participant ServerRouter
  participant AgentActivityPublisher
  Client->>HttpRouter: Send request with thread ID
  HttpRouter->>ServerRouter: Route path parameter up to 512 characters
  ServerRouter->>AgentActivityPublisher: Publish activity with original thread ID and environment
  AgentActivityPublisher-->>ServerRouter: Complete publication
  ServerRouter-->>Client: Return HTTP 200
Loading

Merge Risk: ⚪ Minimal · up to 7e8e1

The available evidence identifies no remaining actionable risk for supported long or percent-encoded thread IDs.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 4…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly and concisely describes the main change: accepting delegated thread IDs in relay activity routes.
Description check ✅ Passed The description explains what changed, why it changed, test coverage, and the absence of UI changes. It does not reproduce the template headings or checklist, but it provides the required substantive …
✨ Finishing Touches
📝 Generate docstrings
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added size:XXL 1,000+ changed lines (additions + deletions). and removed size:XS 0-9 changed lines (additions + deletions). labels Sep 18, 2026
@juliusmarminge
juliusmarminge merged commit 80c1f77 into main Sep 18, 2026
22 checks passed
@juliusmarminge
juliusmarminge deleted the fix/relay-long-thread-ids branch September 18, 2026 18:13
aorwall added a commit to aorwall/t3code that referenced this pull request Sep 19, 2026
Merges `pingdotgg/t3code` at `5378f87f9` into the fork, 51 commits from
base `994654198`.

`4232` files landed against `4233` in the upstream range; the gap of one
is `apps/server/src/cli/pair.ts`, which this fork deletes on purpose.
Fork delta afterwards: `777` files.

## Usable as-is

Nothing here needs Moatless backend or deployment work.

- **Client spans reach the trace proxy again** (pingdotgg#12332). Upstream
rebuilt the fork's own `ClientTracingLive` as
`apps/web/src/observability/clientTracer.ts` — same behaviour,
upstream's name — so the fork delta retired into it. `clientTracing.ts`
and `lib/runtime.ts` are byte-identical to upstream again.
- **Sidebar search matches message content** (pingdotgg#11761), with a new
`ThreadSearchMatch` component and the logic moved out of the command
palette.
- **A file-to-symlink type change no longer crashes the diff view**
(pingdotgg#11075).
- **Obsolete code removed** (pingdotgg#9917). This deleted `SidebarGroupLabel`
from `components/ui/sidebar.tsx`; the fork's `SettingsSidebarNav` was
its only caller, so the label is now inlined there rather than
re-exported from an upstream-owned file.
- **Build fixes**: executable imports parsed without matching source
strings (pingdotgg#12488), and multiple license notices retained for one package
(pingdotgg#12489) — the second sits on the `vp build` path this fork's image
workflow runs.
- **Dependencies**: Effect rc.115 and Alchemy beta.78 with their
reference sync (pingdotgg#12326, pingdotgg#12327), plus two security bumps of vulnerable
transitives (pingdotgg#12417, pingdotgg#12411).
- **`test-t3-app` rewritten around the desktop Browser panel** (pingdotgg#12414).
Taken whole with the fork's scope note re-applied.

Not applicable rather than usable, listed so the next merge does not
re-derive them: the relay deploy and client-config work (pingdotgg#12401, pingdotgg#12484,
pingdotgg#12518, pingdotgg#12519) and the CI label/report automation (pingdotgg#12517, pingdotgg#12492)
belong to infrastructure this fork does not run — every inherited
workflow here is `disabled_manually`.

## Unsupported in Moatless / needs implementation

- **Sort pull requests by what is blocked on me** (pingdotgg#12508,
`apps/web/src/components/pullRequest/pullRequestList.logic.ts`). Needs
`pullRequests.list`, `detail` and `activity`, which the backend does not
dispatch. `FEATURES.pullRequestSurface` is `false`, so the route this
lands in is not reachable here; Moatless serves `pullRequests.summary`
and nothing else in the family. The server half of the same surface is
pingdotgg#11825, below.
- **View and control agent devices from mobile** (pingdotgg#12531,
`apps/mobile/src/features/devices/`). A device panel driven by a device
stream brokered by the bundled server between a client and a registered
device. Moatless has no device registry and device pairing is decided
out in this fork, so the whole path — registration, stream transport,
control commands — is backend work.
- **The mobile client generally.** Twenty-two further mobile changes
landed in this range — pull-to-refresh, native settings and snooze
controls, model favourites, project search, platform header and menu
splits, Live Activity and Material You import isolation, notification
and permission delegate synchronization, copy-thread-id. They are in the
tree and typecheck, but whether this fork's mobile client can reach a
Moatless backend at all is still unverified; see `docs/fork/gaps.md`,
_Mobile testing against Moatless is undocumented because it is
unverified_, which this merge extended.
- **ACP SDK elicitation requests** (pingdotgg#11294,
`packages/effect-acp/src/{client,protocol,rpc}.ts`). Elicitation is an
agent-to-client request: the agent asks the user for input mid-turn and
blocks on the answer. Moatless drives its own agents rather than hosting
upstream's ACP adapters, so the round-trip has to exist on the backend
before any client surface can render it.

## Backend behavior to consider reproducing in Moatless

Nine server-side fixes, all recorded in `docs/fork/gaps.md` under
_Runtime fixes upstream made to its own server_ with the file each lives
in:

- **An oversized pull request diff should not be cached** (pingdotgg#12523) — 512
KiB cap on cached patch text, with invalidation of an entry already
held. A capacity-bounded cache with no size bound is how one enormous PR
pins memory.
- **Checkpoint git commands should be retried on a transient failure**
(pingdotgg#11665) — `…lock: file exists` and `no such file or directory`
classified as retryable and retried twice at 75 ms. The race is an agent
writing files while a checkpoint is captured, which a sandbox makes more
likely.
- **A failed settings write should roll its secret changes back**
(pingdotgg#12487) — otherwise a persistence failure leaves a provider key removed
with nothing to restore it from, and nothing says so until the provider
is next used.
- **A fetch failure should be explained without echoing the remote**
(pingdotgg#12485) — four recognised stderr shapes mapped to fixed sentences,
anything else left generic, because fetch stderr can carry credentials
from the remote URL into a persisted error.
- **A branch switch should not be readable as a path checkout** (pingdotgg#10574)
— one `--` appended to `git checkout <ref>`, with losing uncommitted
work behind it.
- **Rate limits from a tolerated read should still be recorded**
(pingdotgg#12486). Bitbucket is not a fork target; the shape is — the budget was
spent whether or not the caller wanted the answer.
- **An evicted preview host should be able to register again** (pingdotgg#12535)
— completes the RPC stream instead of shutting the queue down, so a
desktop that was merely slow can re-register. Follows pingdotgg#11381 from the
2026-09-16 merge. The client half landed here in
`packages/client-runtime`.
- **A server should export log records, not only traces and metrics**
(pingdotgg#12493) — `otlpLogsUrl` plus a shared `otlpResource`, which is what
makes the three signals joinable at the collector. The fork already
exports client spans.
- **Pull request reads should be batched rather than fanned out**
(pingdotgg#11825) — far fewer GitHub requests per preview, with a measurement
script. Moatless does its own GitHub reads behind
`pullRequests.summary`.

## Merge notes

Five conflicts, each resolved with the verdict `preflight.mjs` printed.
The one that needed thought was `apps/web/src/lib/runtime.ts`: pingdotgg#12332
reimplemented the fork's tracer layer upstream and, in the same change,
removed the `activeDelegate` binding the fork's layer read — so the fork
block auto-merged into `clientTracing.ts` referencing a symbol that no
longer existed. Resolved by converging onto upstream rather than
repairing the fork copy.

Two inventory gaps this merge closed: `apps/server/src/bin.ts` had no
path-policy entry despite holding the only references to the deleted
`cli/pair.ts` (now `server-cli-entrypoint`, `converged`), and the fork's
own `typecheck.yml` was missing from `offRepo.allowedActiveWorkflows`,
which made `tripwires.mjs` report it as an inherited workflow switched
back on.

`unsupported-methods.mjs` reported ADD 0 / DROP 0 — no change to
`packages/contracts/src/rpc.ts`.

`verify.mjs`: all 10 checks green on the final full pass, tests included
— 334 files, 5144 tests. Tripwires: Clerk 4, pairing 96, session
bootstrap 8, 5 known deletions, 4 active workflows.

Tracker entry: `docs/fork/upstream-merge-log.md`, 2026-09-19.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---
Moatless task:
https://moatless.soaplabstest.com/tasks/0a5d08b0-0bd4-412e-a837-782ac67e5a13
github-actions Bot added a commit to omarcresp/t3code-flake that referenced this pull request Sep 19, 2026
## What's Changed
* fix(mobile): use singular label for one settings environment by @juliusmarminge in pingdotgg/t3code#12282
* feat(mobile): add copy thread ID to thread list actions by @jakeleventhal in pingdotgg/t3code#12228
* fix(mobile): remove Android input underline backgrounds by @juliusmarminge in pingdotgg/t3code#12394
* chore(deps): upgrade Effect to rc.115 and Alchemy to beta.78 by @juliusmarminge in pingdotgg/t3code#12326
* chore(refs): sync Effect and Alchemy references to rc.115 and beta.78 by @juliusmarminge in pingdotgg/t3code#12327
* chore(relay): deploy with the Alchemy CLI and publish client config through an Action by @juliusmarminge in pingdotgg/t3code#12401
* chore(deps): bump the npm_and_yarn group across 1 directory with 3 updates by @dependabot[bot] in pingdotgg/t3code#12411
* fix(git): prevent stale branch selections from restoring files by @yashranaway in pingdotgg/t3code#10574
* chore(deps): bump parents that carry vulnerable transitive dependencies by @juliusmarminge in pingdotgg/t3code#12417
* fix(web): keep a file-to-symlink type change from crashing the diff view by @Mnigos in pingdotgg/t3code#11075
* Use T3 Device panel for mobile testing by @juliusmarminge in pingdotgg/t3code#12414
* fix(web): client spans reach the trace proxy again by @yordis in pingdotgg/t3code#12332
* fix(bitbucket): preserve rate limits from optional PR reads by @juliusmarminge in pingdotgg/t3code#12486
* fix(mobile): synchronize native permission registry access by @juliusmarminge in pingdotgg/t3code#12482
* fix(build): retain multiple license notices for one package by @juliusmarminge in pingdotgg/t3code#12489
* fix(build): parse executable imports without matching source strings by @juliusmarminge in pingdotgg/t3code#12488
* fix(mobile): synchronize native notification delegates by @juliusmarminge in pingdotgg/t3code#12483
* fix(relay): accept delegated thread IDs in activity routes by @juliusmarminge in pingdotgg/t3code#12484
* fix(git): explain fetch failures without exposing remote output by @juliusmarminge in pingdotgg/t3code#12485
* fix(web): sidebar search matches message content by @koushikxd in pingdotgg/t3code#11761
* fix(server): restore secrets when settings persistence fails by @juliusmarminge in pingdotgg/t3code#12487
* fix(ci): accept V2 transfer reports without cross-scenario comparisons by @juliusmarminge in pingdotgg/t3code#12492
* fix(web): speed up PR previews with fewer GitHub requests by @dominic-r in pingdotgg/t3code#11825
* fix(server): retry transient git failures during checkpoint capture by @saphid in pingdotgg/t3code#11665
* fix(mobile): keep archived threads visible during iOS search by @juliusmarminge in pingdotgg/t3code#12420
* perf(mobile): isolate Material You conversion on Android by @juliusmarminge in pingdotgg/t3code#12379
* perf(mobile): isolate iOS Live Activity imports by @juliusmarminge in pingdotgg/t3code#12380
* refactor(mobile): split home headers by platform by @juliusmarminge in pingdotgg/t3code#12381
* refactor(mobile): split native menus by platform by @juliusmarminge in pingdotgg/t3code#12382
* refactor(mobile): isolate thread row appearance by platform by @juliusmarminge in pingdotgg/t3code#12383
* refactor(mobile): split settings selection rows by platform by @juliusmarminge in pingdotgg/t3code#12384
* refactor(mobile): centralize platform header rendering by @juliusmarminge in pingdotgg/t3code#12388
* refactor(mobile): configure thread headers through the shared core by @juliusmarminge in pingdotgg/t3code#12389
* refactor(mobile): share file header actions and search configuration by @juliusmarminge in pingdotgg/t3code#12390
* refactor(mobile): share terminal header and menu configuration by @juliusmarminge in pingdotgg/t3code#12391
* refactor(mobile): share archived thread header configuration by @juliusmarminge in pingdotgg/t3code#12399
* refactor(mobile): compose review menus through the shared header by @juliusmarminge in pingdotgg/t3code#12400
* feat(mobile): search projects when starting a task by @juliusmarminge in pingdotgg/t3code#12496
* fix(mobile): preserve multiple model favorites by @juliusmarminge in pingdotgg/t3code#12505
* feat(server): export log records over OTLP by @yordis in pingdotgg/t3code#12493
* fix(mobile): use native settings and snooze controls by @juliusmarminge in pingdotgg/t3code#12512
* feat(web): sort pull requests by what is blocked on me by @flamboh in pingdotgg/t3code#12508
* fix(mobile): prefer pull-to-refresh on list screens by @juliusmarminge in pingdotgg/t3code#12515
* fix(acp): accept SDK elicitation requests by @shivamhwp in pingdotgg/t3code#11294
* fix(release): read relay configuration without loading deployment providers by @juliusmarminge in pingdotgg/t3code#12518
* fix(ci): reconcile native change labels against pinned commits by @juliusmarminge in pingdotgg/t3code#12517
* fix(release): strip Alchemy progress before parsing relay state by @juliusmarminge in pingdotgg/t3code#12519
* refactor: remove obsolete code by @t3dotgg in pingdotgg/t3code#9917
* fix(server): release oversized pull request diff cache entries by @juliusmarminge in pingdotgg/t3code#12523
* feat(mobile): view and control agent devices by @juliusmarminge in pingdotgg/t3code#12531
* fix(preview): recover host registration after request timeouts by @juliusmarminge in pingdotgg/t3code#12535
* fix(mobile): align built-in theme colors with desktop by @juliusmarminge in pingdotgg/t3code#12534
* feat(desktop): export main process telemetry over OTLP by @yordis in pingdotgg/t3code#12520
* fix(codex): surface app permission requests as approvable by @Exotic209093 in pingdotgg/t3code#7861
* chore(desktop): leave main process metrics export off until a metric exists by @juliusmarminge in pingdotgg/t3code#12540
* fix(release): drop placeholder allowBuilds entry that broke desktop builds by @juliusmarminge in pingdotgg/t3code#12544

## New Contributors
* @dependabot[bot] made their first contribution in pingdotgg/t3code#12411
* @koushikxd made their first contribution in pingdotgg/t3code#11761

**Full Changelog**: pingdotgg/t3code@v0.0.43-nightly.20260918.1895...v0.0.43-nightly.20260919.1948

Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.0.43-nightly.20260919.1948
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XXL 1,000+ changed lines (additions + deletions). vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant