[dustinhealy]

Summary

Adds one typed host for background Agent Responses: durable dispatch, signed local worker ingress, canonical completion/recovery, owner review and cancellation. Ordinary synchronous Responses remain available, and background execution stays disabled unless configured.

The host preserves the original source credential's authority on replay, keeps native recovery state visible, and distinguishes deterministic invalid requests from retryable service failures.

How it works

The host composes durable dispatch, signed local worker ingress, completion/recovery and owner review around the existing synchronous Responses handlers. Background reads require an authorized journal and cannot fall through to ordinary history. Continuation preserves retention deadlines; review submission is available only when checkpoint validation and resume execution are installed together.

Type of change

• Feature
• Bug fix

Testing

Tested environments/configuration: Node 24, disposable MongoDB replica sets, real HTTP listeners, actual API-key authentication and durable queue execution.

Automated tests: 568 Responses/remote cases across 26 suites and 99 compiled JSON/SSE controller cases pass. Real HTTP/Mongo cases cover one journal load per poll, source denial and storage failure without fallback, fresh-turn and inherited retention, canonical input/output ancestry, replay without duplicate messages, owner/native boundaries and trusted listeners. Actual Stop/provider-error history is read through the compiled host and real foreground fallback; closing or physically erasing its journal cannot disclose retained background Messages. Ordinary response-ID and legacy conversation-ID reads reject background-marked history even when its full receipt is damaged.

Owning API types, ordered provider/data-schemas/API builds, explicit ten-file import sorting/checks and scoped static checks pass. Three optional full-mode checks are skipped, with types checked separately. Compiled CJS/ESM smoke passes; the isolated Lighthouse harness passes (median LCP 3.58 s, CLS 0.018, TBT 79 ms).

Screenshots / recordings

No user-facing visual change: typed host and HTTP composition.

Risk / compatibility

The host requires explicit durable dependencies and an initialized local listener. Background history requires a readable, authorized journal; legacy conversation-ID retrieval remains foreground-only. Missing authority, unavailable completion proof and incomplete checkpoint cleanup fail closed. Public response state comes from canonical receipts; transient progress does not fabricate completion. Owner browser review and scoped execution credentials retain separate authority.

Checklist

• I reviewed my own changes
• Relevant tests have been added or updated
• Existing relevant local tests pass
• Scoped checks introduce no new warnings or errors
• Complex behavior is documented in code and tests
• Required dependency changes: not applicable
• Required documentation PR: 📚 docs: Document Background Responses and Slack Channels docs#892

[Copilot]

🟡 Changes recommended

Idempotent replays can return output created by a revoked key without rechecking its authority, while non-loopback listener bindings accept queued work that cannot execute.

4 open issues

• Support worker transport for concrete interface bindings · New
• Reauthorize stored source key before idempotent replay · New
• Preserve recovery marker in native review projection · New
• Return 400 for invalid envelope nesting errors · New

What changed in this PR

Adds a shared background Responses host that composes existing services for HTTP handlers and workers, including durable dispatch, access checks, review, and cancellation.

Changes:

• Composes execution, recovery, review, and worker authentication behind one host interface.
• Adds typed HTTP handlers for background creation, retrieval, and cancellation while preserving ordinary Responses handling.
• Adds integration tests covering authorization, idempotency, review decisions, cancellation, and durable execution.

File	Description
packages/​api/​src/​agents/​responses/​index.ts	Exports the new host factory.
packages/​api/​src/​agents/​responses/​http.ts	Adds background Responses HTTP handlers.
packages/​api/​src/​agents/​responses/​host.ts	Composes services and exposes HTTP and trusted-transport operations.
packages/​api/​src/​agents/​responses/​host.spec.ts	Tests host behavior through HTTP, authentication, storage, and queue integration.

_{Review effort: Balanced}

[github-actions]

Lighthouse CI failed. The last 80 log lines contain the measured budgets and assertion failures.

│ 23      │ 'http://localhost:3080/api/permissions/mcpServer/effective/all'                                                 │ 2881.0419999999867 │ 3789.890999999974  │ 200    │
│ 24      │ 'http://localhost:3080/api/prompts/groups?limit=10'                                                             │ 2883.485999999946  │ 4326.845000000001  │ 200    │
│ 25      │ 'http://localhost:3080/api/keys?name=openAI'                                                                    │ 3531.0969999999797 │ 4043.7240000000165 │ 200    │
│ 26      │ 'http://localhost:3080/api/presets'                                                                             │ 3534.0259999999835 │ 4045.8669999999984 │ 200    │
│ 27      │ 'http://localhost:3080/api/tags'                                                                                │ 3534.307999999961  │ 4049.5509999999485 │ 200    │
│ 28      │ 'http://localhost:3080/api/share/link/16390000-0000-4000-8000-000000000001'                                     │ 3536.9529999999795 │ 4309.544999999955  │ 200    │
│ 29      │ 'http://localhost:3080/api/messages/16390000-0000-4000-8000-000000000001?toolPreviews=1'                        │ 3538.600999999966  │ 4567.401999999973  │ 200    │
│ 30      │ 'http://localhost:3080/api/files/config'                                                                        │ 3538.8979999999574 │ 4315.926000000007  │ 200    │
│ 31      │ 'http://localhost:3080/api/user/settings/favorites/tools'                                                       │ 3540.0899999999674 │ 4658.002999999939  │ 200    │
│ 32      │ 'http://localhost:3080/api/endpoints/token-config'                                                              │ 3540.412000000011  │ 4576.503999999986  │ 200    │
│ 33      │ 'http://localhost:3080/api/user/settings/skills/active'                                                         │ 3540.612999999954  │ 4570.562999999995  │ 200    │
│ 34      │ 'http://localhost:3080/api/agents/tools/web_search/auth'                                                        │ 3542.6729999999807 │ 7350.207999999955  │ 200    │
│ 35      │ 'http://localhost:3080/api/agents/tools/calls?conversationId=16390000-0000-4000-8000-000000000001'              │ 3543.5999999999767 │ 4835.075999999972  │ 200    │
│ 36      │ 'http://localhost:3080/api/agents/chat/status/16390000-0000-4000-8000-000000000001?generationProtocolVersion=2' │ 4717.810999999958  │ 4973.4469999999565 │ 200    │
└─────────┴─────────────────────────────────────────────────────────────────────────────────────────────────────────────────┴────────────────────┴────────────────────┴────────┘

Inspect .lighthouse HTML/JSON and e2e/lighthouse/README.md. Reuse loaded user/config data; overlap independent reads without bypassing authorization.

┌─────────┬────────────────────────────┬──────────────────────┬───────┐
│ (index) │ audit                      │ median               │ limit │
├─────────┼────────────────────────────┼──────────────────────┼───────┤
│ 0       │ 'largest-contentful-paint' │ 4735.197             │ 4500  │
│ 1       │ 'cumulative-layout-shift'  │ 0.017901221762542687 │ 0.1   │
│ 2       │ 'total-blocking-time'      │ 463.5079999999698    │ 500   │
└─────────┴────────────────────────────┴──────────────────────┴───────┘

  1) [chromium] › e2e/lighthouse/load.spec.ts:10:5 › serial database latency stays within web-vitals budgets 

    Error: Median largest-contentful-paint must stay within 4500

    expect(received).toBeLessThanOrEqual(expected)

    Expected: <= 4500
    Received:    4735.197

       at audit.ts:127

      125 |   console.table(measured);
      126 |   for (const { audit, median, limit } of measured) {
    > 127 |     expect(median, `Median ${audit} must stay within ${limit}`).toBeLessThanOrEqual(limit);
          |                                                                 ^
      128 |   }
      129 |   return results;
      130 | }
        at auditPage (/home/runner/work/LibreChat/LibreChat/e2e/lighthouse/audit.ts:127:65)
        at /home/runner/work/LibreChat/LibreChat/e2e/lighthouse/load.spec.ts:33:19

    attachment #1: screenshot (image/png) ──────────────────────────────────────────────────────────
    e2e/lighthouse/.test-results/load-serial-database-latency-stays-within-web-vitals-budgets-chromium/test-failed-1.png
    ────────────────────────────────────────────────────────────────────────────────────────────────

    Error Context: e2e/lighthouse/.test-results/load-serial-database-latency-stays-within-web-vitals-budgets-chromium/error-context.md

    attachment #3: trace (application/zip) ─────────────────────────────────────────────────────────
    e2e/lighthouse/.test-results/load-serial-database-latency-stays-within-web-vitals-budgets-chromium/trace.zip
    Usage:

        npx playwright show-trace e2e/lighthouse/.test-results/load-serial-database-latency-stays-within-web-vitals-budgets-chromium/trace.zip

    ────────────────────────────────────────────────────────────────────────────────────────────────


🤖: global teardown has been started
2026-10-29 13:44:46 �[32minfo�[39m: �[32mMongo Connection options�[39m
2026-10-29 13:44:46 �[32minfo�[39m: �[32m{�[39m
�[32m  "bufferCommands": false�[39m
�[32m}�[39m
🤖:  ✅  Connected to Database
🤖:  ✅  Found user in Database
🤖:  ✅  Deleted 1 convos & 2 messages
🤖:  ✅  Deleted user from Database
🤖: global teardown has been started
2026-10-29 13:44:47 �[32minfo�[39m: �[32mMongo Connection options�[39m
2026-10-29 13:44:47 �[32minfo�[39m: �[32m{�[39m
�[32m  "bufferCommands": false�[39m
�[32m}�[39m
🤖:  ✅  Connected to Database
🤖:  ⚠️  User not found in Database
  1 failed
    [chromium] › e2e/lighthouse/load.spec.ts:10:5 › serial database latency stays within web-vitals budgets 

Open the full run

[dustinhealy]

@codex review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-31T00:13:01.432723Z	f80de08	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5c0655efa7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[dustinhealy]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Hooray!

Reviewed commit: f80de081c9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".