Make Codex and Claude Code subscriptions go further: a local model router that gives routine agent work to economical models and keeps your strongest model for the hard parts.
Worker native context and profile
Worker lifecycle · Worker context map
The installation source resolves the selected executable and
builds a profile for an admitted run. NativeWorkerContext
reads only the effective Unix instance HOME, or the native Windows Known Folder
Profile, and the selected Harness's config-root variable. Windows ignores ambient
HOME/USERPROFILE for account discovery; explicit native config-root selectors still
apply. Libtest's identified isolated child and explicit probe contexts use their
private test-owned homes. It never searches for another user's home from an executable
path. The child receives a fresh explicit
environment; preserving command search paths does not import upstream credentials.
State and ownership
New tasks bind their effective home, native config root and canonical workspace
once in the task-owned metadata directory. Continue reads that descriptor instead
of resolving today's environment. Only Codex/Claude accept the registered legacy
private-root path when the descriptor is absent; Qoder/OpenCode require it. A damaged
descriptor must fail rather than fall back.
TaskSessionRoot still owns HiRoute metadata and the frozen Codex alias catalog.
The borrowed native config/history tree is never a launcher material or cleanup
target. History binding and retention belong to materials and the
existing delegation lifecycle, not these renderers.
The profile builder projects the admitted permission policy, supplies explicit context and temporary paths, and combines one Harness renderer with the validated native or adapter launch form. Tests and the older adapter-only loopback installation probe explicitly request isolated contexts. They never silently use the developer's HOME. Qoder requires the borrowed context; that older probe does not establish its login or execution capability.
The shared validated launch form rejects Qoder adapter/Node fields and missing
Codex/Claude adapters. Qoder discovery checks metadata for both qoder and
qodercli names and the official standalone directory. It never runs the
discovered CLI or replaces a missing explicit selection with another candidate.
Native launch contracts
- Codex uses a task-specific provider key so a user's ordinary provider
table cannot accidentally contribute extra routing/auth fields through native
table merging. The private per-run executable launcher passes the same managed
settings used by
CODEX_CONFIGas native-coverrides beforeapp-serverstarts. This covers the adapter's earlyaccount/readand model-catalog lookup. Only the environment contains the run token; startup arguments and files refer to its variable name. Continue reuses the task's provider key/catalog and obtains a fresh launcher/token. Unix uses a private executable script. Windows uses the daemon's internalapp-serverentry and a token-free descriptor binding the selected native executable and any npm script prefix to held file identities. The native argv contains every exact-coverride beforeapp-server, without a shell. The private Windows adapter bootstrap admits frozen npm bundle hashes for codex-acp 2.1.1 and 2.2.2; it only rewrites 2.1.1's known shell launch into native argv. Unknown producers fail explicitly and require a new audited compatibility gate. - Claude loads user/project/local setting sources and exposes
Skillin the default approve-all tool set. Its selected Node runs a private adapter bootstrap before importing the selected JavaScript adapter. The bootstrap prevents managed settings from changing or deleting the host's routing, credential, context, CLI and runtime-loader environment values; protected absent provider credentials stay absent too. Ordinary settings variables remain available. This guard belongs only to the adapter process: it does not useNODE_OPTIONSor install a child-process preload, and it is not a sandbox for arbitrary JavaScript. Native host-managed provider protection, a custom model option and explicit session model maintain the selected route after the native CLI starts. Restricted profiles retain their existing tool sets.strictMcpConfigwith an empty explicit MCP map suppresses ambient MCP;disableAllHookssuppresses user/project/plugin hooks without disabling plugin skills. Native managed-policy hooks and adapter callbacks remain separate. These options are not a claim that every extension is available or universally disabled. - Qoder starts the selected native CLI with
--acp, explicit--config-dirand user/project/local resource sources. It consumes the single shared Qoder renderer for a token-free per-run settings file. The task-specific provider prefix belongs only to the native selected model ID; Plan, run authorization and Gateway retain the raw alias. New/Load use the shared typed ACP model confirmation before prompt. Defaultyolopermission applies to the explicit Read/Write/Edit/Bash/Grep/Glob/Skill tool set. Native Agent and other unproven model-using tools are not enabled; ApproveReads/DenyAll fail before launch rather than upgrading permission. Explicit empty strict MCP configuration and disabled hooks preserve that boundary without excluding user and project skills. The overlay disables native updates, periodic history cleanup and plan-driven model switching, and fixes supported model purposes to the frozen alias. Actual auxiliary routing needs native wire evidence; the presence of these settings is not that evidence.
Qoder's budget projection
uses the frozen Plan's existing effective context policy, including total and
reasoning reservations, and the smallest exact output bound across all active
candidates and protocols. The shared renderer writes both contextWindow and
maxOutputTokens into the native provider model entry. Qoder 1.1.65 uses this
catalogue output value for both request limits and compaction reservation; its
ACP path does not apply the CLI --max-output-tokens flag as a substitute.
Unknown, zero, unrepresentable or nonpositive effective compaction budgets fail
before native launch. A positive threshold does not promise every skill or
prompt fits. The independent collaboration probe uses its own synthetic 2048
output budget without claiming a Worker Plan context. Existing Codex/Claude
budget projections are unchanged.
Read the budget contracts for mixed-route minima, total/reasoning reservations and exact rejection edges; the Qoder profile test checks the rendered New/Continue materials. The real Qoder core journey separately verifies 32768-context/4096-output native skill execution and exact Continue through the public Worker entry.
Qoder retains only the task-owned context descriptor and exact native-session binding in HiRoute metadata. Its native history is opaque: Continue requests that exact ACP session ID and fails if the native client cannot load it. There is no Qoder private-root legacy reader, transcript scanner or shared-history deletion. The native client must already be logged in under the selected context; HiRoute does not copy authentication or inherit an ambient personal access token.
Borrowed Claude supplies only the Gateway IP as NO_PROXY and no_proxy in both
the adapter environment and the native flag settings. These two non-secret values
bypass user-configured proxies for the local model route; other native tool proxy
settings remain available. The bootstrap rejects conflicting managed proxy/TLS
environment writes before ACP starts: managed policy outranks flag settings and
the native CLI would read it again, so silently ignoring that write is insufficient.
Compatible managed bypass values are allowed. Rejection diagnostics contain no
setting values or credentials. This is a boundary for the local HTTP Gateway,
not general transport management for native tools.
Borrowed Claude execution requires an explicitly selected Node runtime and a
JavaScript ACP adapter entry. An executable/shebang adapter with no saved Node
selection can still be discovered and selected under the existing installation
contract, but this capability fails with CapabilityUnavailable before starting
the unguarded adapter. Select a Node runtime alongside that adapter in the Worker
installation configuration. HiRoute does not guess a runtime from PATH or inspect
the adapter's program text. Existing isolated tasks/probes retain their direct
adapter launch behavior.
At a borrowed Claude launch, the runtime capability check
executes only the selected CLI's bounded --version with the selected command
search path and disposable HOME/native/XDG roots and cwd, without inherited run
credentials or user configuration. The owned Unix process group or Windows Job is stopped before
those temporary roots are removed. This narrowly requires
the known Claude 2.x host-managed-provider capability (2.1.231 or later); it is not
an installation readiness probe or a compatibility guarantee. An unsupported,
unknown, failed or timed-out response rejects this launch before model execution.
Native client effort preferences may still affect client-side behavior. They are not the authority for the frozen Plan's upstream reasoning settings: AgentPlan routing projects the frozen candidate configuration at the Gateway. This change does not introduce a new effort policy.
Context discovery, skill discovery/invocation, model access, native session restoration and process startup are separate capabilities. This module does not add ecosystem scanning/import, general Agent launch, a new execution backend or a plugin framework. ACP model/session verification remains in ACP, and the OS launcher owns executable material permissions and process cleanup.
OpenCode native ACP and opaque history
OpenCode rendering launches the selected native executable with
acp --cwd, an explicit loopback hostname and an ephemeral authenticated listener.
Stdio ACP, its listener and native tools share the existing process-group/Job owner;
there is no separately managed server. No Node runtime or ACP adapter is selected.
The context descriptor additionally freezes OpenCode's XDG config/data/cache/state
roots, optional absolute config file, additive config directory and exact database
path. Canonical XDG roots must retain the opencode leaf used by the child's XDG
projection. A link resolving to another leaf name is refused on New and Continue,
so admission and the child cannot address different directories. Extra config
directories use their explicit selector and are not subject to this leaf rule.
Existing borrowed history is checked read-only against the audited native
migration-ID set before launch. Initial format admission uses adjacent official
npm platform-package metadata for 1.19.3; it does not run a shim, fingerprint a
binary, decode sessions or migrate history. A new absent database may be initialized
by OpenCode, while Continue requires the existing bound database and exact ACP ID.
Other installation forms can retain independent configuration/Skill capabilities.
OpenCode shares the existing daemon-local native initialization permit, keyed by the frozen database path. Final database/composition admission runs after waiting; the captured configuration digest must still match. The permit ends at successful ACP initialize, before New/Load or prompt, so cold schema creation cannot race between participating Workers while their tasks can still execute concurrently. Cancellation, deadline, fresh authority and uncertain-stop handling stay shared. There is no native database prewarming, repair or persistent lock file.
One task provider supplies the frozen raw Plan alias, protocol and context/output bounds through a final native overlay. Main, small, title, summary and compaction models share that selector, with a fresh run token and stateless Responses. The shared typed ACP helper confirms the primary mode first, then confirms the model from the latest typed config options before New/Load prompt intent.
The supported static composition preserves native project rules and user/project
Skills. Approve-all admits native read/search/edit/shell/Skill; nested tasks, external
MCP, plugins and custom executable tools are excluded. Existing nonempty tool/agent
directories, late remote/organization/managed settings or unsupported agent overrides
fail before launch. Native LSP/formatter execution is disabled. The bounded reader
rechecks dependencies without rewriting daily configuration or copying credentials.
Project inspection stops at a Git root only after bounded native rev-parse checks
in the same filtered HOME/XDG/PATH as the Worker. Invalid .git/worktree pointers,
unavailable or rejecting Git, and unconfirmed roots make this Worker unavailable;
they cannot hide ancestor configuration or custom tools. Final admission rechecks
the boundary after waiting for native initialization, using the captured child PATH.
This permission boundary is not an OS sandbox for approve-all shell commands.
The native acceptance guide separates saved ordinary model use, the installed shared Skill, frozen Worker execution, real compaction/auxiliary requests, cancellation and exact Continue.
Pi resources and SDK transport
Pi rendering binds the selected official npm CLI, its SDK export and the selected Node to the bundled ACP bridge. Native user/project and installed-package resources are borrowed through scope-preserving in-memory settings, with offline discovery and no package installation. The bridge uses an empty credential store so unrelated native credential commands cannot run. Only the frozen provider/model, run key and effective context/output budget enter its model runtime; extensions and MCP are outside this Worker contract.
Task-owned native-pi.jsonl has a strict v3 body/context contract, including native
branch-local context edits. Continue requires validated native open of that exact
history, without repair or replacement. See the
operation capability map
and bridge process regressions for interface and
creation/cancellation/disconnect boundaries.
DSH public composition
DSH rendering uses the selected CLI's public --profile acp --patch entry.
The final run-owned patch supplies the frozen model, context/output budget and
permission policy. Borrowed HOME/DSH_HOME, project resources and custom Skill roots
remain native-owned. History and attachments live under the task root; HiRoute
binds the native/ACP session identity without decoding native history. Resume
requires the advertised session/resume capability and the exact saved binding.
Generated JSON is a public YAML subset. The patch disables auxiliary model
providers, telemetry and background-shell promotion, while preserving required
Skill/read/bash resources. Local native checks
use the public composition dump in a private root without activating model plugins; relevant
resource overrides cannot disable those capabilities or replace dshHome.
The collaboration proof excludes unrelated model-provider edits.
Run secrets remain in the environment through apiKeyEnv. On Messages the native
x-api-key carrier is admitted only for a live run-model token on /v1/messages;
Gateway authority tests
reject account keys, model grants and control-run tokens on that carrier.
Saved Web model edits remain owned by the
native configuration guide,
not this per-run renderer. See DSH acceptance
for actual CLI, Skill, tool, cancellation and exact-resume evidence.
Representative product contracts
Profile tests cover token-free startup configuration, literal argument passing for quoted paths, preserved daily settings, task catalog/provider reuse, fresh run credentials, and Claude skills without widening restricted tools. Context tests cover explicit native roots, Pilot HOME and rejection of unusable selectors. Existing isolated-root tests retain legacy history/material lifetime assertions.
Qoder profile tests cover single-CLI launch, user/project sources, tool boundaries, exact selected ID, fresh credentials and token-free materials. Discovery and availability test metadata-only single-CLI selection without replacing an unavailable explicit choice. Native identity and borrowed-binding tests cover Qoder alongside the existing exact-ID contracts; they do not establish real login, history flush or auxiliary-model routing.
Run node --test crates/daemon/src/delegation/profile/claude_adapter_bootstrap.test.mjs
with the repository's Node version for the bootstrap boundary. The tests execute
the production bootstrap with a synthetic settings-writing adapter, prove the
unguarded regression, check child environment delivery without a propagated guard,
reject managed transport conflicts, and verify that rejected startup diagnostics
do not expose the runtime credential.
These tests do not prove a real installed adapter discovers or invokes skills. Start with the native context journey and its acceptance guide. The existing Worker scenarios under product-e2e and Worker read/Continue must exercise the selected installation on Linux and macOS, including two runs, frozen routing, exact Continue and hidden-content rejection. Native history may remain physically present after HiRoute hides its own content. A real Claude run with conflicting user proxy settings must also complete with no proxy-trap requests; bootstrap fixtures alone do not establish native flag-layer precedence.
Windows Worker processes enter their unnamed Job as part of native process creation,
with only the selected stdio handles inherited. A daemon resident Job also contains
all ordinary descendants across a forced daemon stop. Native npm .cmd shims are
resolved through the known package's declared bin entry and launched with selected
Node, without evaluating the shim's command text. DSH's Windows shell tool is
tool-pwsh; background promotion stays disabled in the managed profile.
Windows workspace identity uses volume/file-index ancestry, while native cwd and history keys use ordinary Win32 path spelling. Rust's verbatim I/O prefix is not persisted as part of the native Claude/Pi history key. Native existing configuration and history retain accessible ACLs; only HiRoute-owned metadata and private profiles require the owner-only descriptor. Windows native runtime and real ACP/model journeys need their own CI evidence; metadata checks and Job fixture tests do not establish Agent feature parity.
The opt-in Windows native-client gates execute selected Pi, DSH and Qoder artifacts through these production profiles with a fresh authenticated loopback endpoint. Each must initialize, create a session, reload its exact native history and cancel an in-flight request with complete Job cleanup. The existing Codex/Claude installation gates use their selected real adapters and clients. CI must select each ignored case explicitly and require a nonzero pass count; missing artifacts or Qoder login prerequisites fail the gate. These lifecycle checks cover the native protocol and profile tool configuration. The separate Windows tools gates require actual user/project Skill discovery, correlated native Read/Edit/Shell results, edited file and shell receipt side effects, exact loaded tool history and complete Job cleanup. Codex reads Skills through its shell and edits through its declared patch tool when available, or a native shell when the current Plan catalog has no patch tool; Claude/Qoder invoke their native Skill tool, and Pi/DSH use their native resource loader and read/edit tools. CI selects all five exact ignored cases using the same fixed upstream clients, selected Node and real daemon launcher. These gates use a fresh private context and controlled model endpoint. Main-Agent collaboration via the installed public CLI, compaction and account/OAuth behavior retain their separate product journeys; successful Worker tool effects do not prove those other paths.