docs(integration): dylib integration issue tracker#1510
Open
NathanFlurry wants to merge 2 commits into
Open
Conversation
Living tracker for the Zid team's dylib-preview migration: their reported blockers (Q0-Q5) and our agentOS/secure-exec bugs surfaced while investigating. Key finding: reproduced their exact pattern + a faithful replay of their actor sequence on native linux-x64 with their pinned versions (815fcda). Q1-Q4 do NOT reproduce and createSession("pi") works end-to-end, so their blockers are environment-specific (custom bundled adapter and/or Rosetta x86-emulation), not SDK bugs. Tracks the genuine our-side gaps (toolKit Zod v3/v4, native-actor dropped config, defaultSoftware ignored, node_modules-mount helper, no mountFs on native actor, port DX, patch audit) and links secure-exec PR #114. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
…1=node_modules hoist, Q2-4=Rosetta
Bundled their actual adapter.js with their build-adapter.mjs (stub+eval+minify),
swapped over agentos-pi, and ran createSession('pi') on their pinned version: it
reaches session/new and returns a sessionId. Unbundled variant resolves too. So
Q1-Q4 don't reproduce on native even with their code. Q1 root cause is the
node_modules hoist layout (dep not on the /root/node_modules ancestor chain core
mounts); Q2-Q4 point to OrbStack/Rosetta x86-emulation (no native repro).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
🚅 Deployed to the agentos-pr-1510 environment in agentos
🚅 Deployed to the agentos-pr-1510 environment in rivet-frontend
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Living tracker for the dylib-preview migration — their reported blockers (Q0–Q5) and our agentOS/secure-exec bugs surfaced while investigating. Use this as the single source of truth; individual fix PRs reference the numbered items.
Key finding
Reproduced their exact core-direct pattern and a faithful replay of their actor sequence (create → seed writes → their three
createInMemoryFileSystemJS-driver mounts →createSession("pi")withcwd:"/workspace"andcwd:"/") on native linux-x64 with their pinned versions (…815fcda/common@0.3.0-rc.2). Q1–Q4 do not reproduce;createSession("pi")succeeds end-to-end. So their blockers are environment-specific — prime suspects: their custom bundled adapter (the stockagentos-piadapter works) and Rosetta x86-emulation. Decisive test for them: stock adapter and/or native linux-x64 (Railway prod), not OrbStack/Rosetta.Contents
defaultSoftwareignored by core, no public node_modules-mount helper, nomountFson the native actor (blocks the proxy pattern), port:6420/:6421DX, carried-patch audit, and the_resolveModulediagnostics fix (secure-exec PR #114).Doc:
docs/integration/zid-dylib-issues.md. This PR is the tracker, not the fixes; merge or keep open as a checklist per team preference.🤖 Generated with Claude Code