Repository navigation
feat(fork): [prototype, do not merge] provider pools, home provisioner hook, and overlay control-socket isolation - #236
orbitingflea wants to merge 1 commit into
Conversation
|
This PR changes the test suite by +55 test cases (browser 0, unit 0, server +55). Keep tests that would fail for a real reason, and test logic below the UI where it can be. See Testing. |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosAll 64 scenario measurements match All 64 scenario measurements
Baseline: Scenario and decoded snapshot size10 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.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
20e2959 to
98c5399
Compare
…and overlay control-socket isolation Provider pools: a model selection may name a pool from `providerPools`; the server places it on one eligible member before anything is persisted. An id that names an instance always reaches that instance, even when an invalid pool shares it. Thread management leaves the project check of a pool to the orchestrator's placement, so a message that switches to a pool is accepted. A switch keeps the thread's instance only while it is an eligible member. Retries of accepted commands replay without placing again. When settings cannot be read, the orchestrator passes only a registered instance. Home provisioner: `homeProvisioner` names a command that receives the homes of the registry's instance map on stdin. Settings changes run it only when the request changed; registry changes always run it. A run that dies or is interrupted never blocks later runs, output is capped at 16 KiB, and every failed run is logged. Provider processes get T3CODE_PROVIDER_INSTANCE_ID and T3CODE_HOOK_STATE_DB. A Codex overlay keeps app-server-control local and drops any symlink there. Skill freshness moves a thread's baseline on any stamp change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
98c5399 to
2d5389c
Compare
|
Superseded: Codex overlays were dropped and T3 Code multi-instance changes are deferred until after anyagent global+project unification. |
改了什么行为
Behaviour change: yes, unmerged prototype only (do not merge). Adds
providerPools(virtual pool selection before thread creation, switch, message dispatch, and MCP delegation, persisting only concrete member instance IDs), an optionalhomeProvisionercommand hook for enabled non-blocked provider homes,T3CODE_PROVIDER_INSTANCE_IDandT3CODE_HOOK_STATE_DBhelper env builders, and removes inheritedapp-server-controlsymlinks from Codex auth overlays.Why
Multi-instance setups need pool routing without persisting virtual IDs on threads, an explicit boundary for external home-wiring tools, and overlay isolation from a shared Codex daemon control socket. Upstream edits stay small (+104/-17 across 8 files), with new logic isolated under
src/fork/. Verified with contracts and server typechecks and 297 targeted tests across 11 files.Undo
Close this unmerged prototype pull request and delete the
proto/multi-instance-architecturebranch. No runtime state changes whenproviderPoolsandhomeProvisionerare unset.