Skip to content

perf(remote-config): specialize WASM for agentless use - #254

Draft
BridgeAR wants to merge 1 commit into
mainfrom
BridgeAR/2026-09-03-wasm-remote-agentless
Draft

perf(remote-config): specialize WASM for agentless use#254
BridgeAR wants to merge 1 commit into
mainfrom
BridgeAR/2026-09-03-wasm-remote-agentless

Conversation

@BridgeAR

@BridgeAR BridgeAR commented Sep 3, 2026

Copy link
Copy Markdown
Member

Requires agentless credentials at the dedicated WASM binding boundary and calls the explicit upstream constructor. The capabilities, pipeline, and remote-config dependency cohort is pinned to the reviewed upstream commit.

The raw remote-config artifact drops from 893,017 to 892,798 bytes.

Tested with both WASM Cargo checks, dependency validation, a rebuilt artifact, and the complete 47-test package and type suite.

The dedicated remote-config entry point is consumed only in agentless mode, but optional credentials kept the generic transport dispatch reachable. Require the agentless inputs and call the explicit upstream constructor so the contract is static at the binding boundary.

With the final dependency cohort, the raw remote-config artifact drops from 893,017 to 892,798 bytes. The dependency stays pinned to the reviewed upstream commit until its release is available.
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