11import { resolve } from "node:path" ;
2- import type { Fixture , ToolCall } from "@copilotkit/llmock" ;
3- import { moduleAccessMounts } from "./helpers/node-modules-mount.js" ;
42import common from "@agentos-software/common" ;
53import pi from "@agentos-software/pi" ;
4+ import type { Fixture , ToolCall } from "@copilotkit/llmock" ;
65import { describe , expect , test } from "vitest" ;
76import type { AgentCapabilities , AgentInfo } from "../src/agent-os.js" ;
87import { AgentOs } from "../src/agent-os.js" ;
@@ -11,6 +10,7 @@ import {
1110 startLlmock ,
1211 stopLlmock ,
1312} from "./helpers/llmock-helper.js" ;
13+ import { moduleAccessMounts } from "./helpers/node-modules-mount.js" ;
1414
1515const MODULE_ACCESS_CWD = resolve ( import . meta. dirname , ".." ) ;
1616
@@ -206,15 +206,7 @@ describe("full createSession('pi') inside the VM", () => {
206206 }
207207 } , 120_000 ) ;
208208
209- // Blocked on shell `>` redirect output being visible to `vm.readFile()`.
210- // The vanilla Pi SDK bash backend spawns the shell directly and the redirect
211- // runs inside the guest shell, but the written bytes do not reconcile to the
212- // host read path yet. Before the adapter dropped its custom bash operations
213- // override this case passed because the override routed the command through
214- // the rpc-client `sh -c` path that the host can observe; the vanilla backend
215- // surfaces the underlying runtime gap. Tracked in
216- // ~/.agents/todo/agentos-runtime-fixes.md (shell-exec redirect visibility).
217- test . skip ( "runs the real Pi SDK ACP flow end-to-end for bash tool calls" , async ( ) => {
209+ test ( "runs the real Pi SDK ACP flow end-to-end for bash tool calls" , async ( ) => {
218210 const fixtures = createToolFixtures (
219211 {
220212 name : "bash" ,
0 commit comments