Skip to content

Commit cc38817

Browse files
author
Sim Pi Agent
committed
Pi Babysit: address PR #6367 feedback
1 parent 62d20ff commit cc38817

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

apps/sim/executor/handlers/pi/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@ Implements the PI block executor. Each sub-mode delegates to a dedicated backend
88
pi/
99
├── pi-handler.ts # Single dispatcher — reads the block's mode and routes to the correct backend
1010
├── core/ # Shared contracts and infrastructure
11-
│ ├── backend.ts # Base backend interface and shared execution logic
12-
│ ├── context.ts # Request context type passed to every backend
11+
│ ├── backend.ts # Backend contracts — all run-params types, PiRunContext, PiRunResult, and PiBackendRun
12+
│ ├── context.ts # Skills-resolution and memory helpers (resolvePiSkills, loadPiMemory, buildPiPrompt, appendPiMemory)
1313
│ ├── events.ts # Streaming event helpers
1414
│ ├── keys.ts # API-key resolution utilities
1515
│ ├── pi-sdk.ts # Thin wrapper around the PI SDK client
@@ -39,4 +39,4 @@ pi/
3939

4040
## Dispatch flow
4141

42-
`pi-handler.ts` is the sole entry point registered in the executor. It inspects the block's `mode` field and calls the matching backend's `run()` method. All backends receive a typed `PiContext` (from `core/context.ts`) and stream incremental events back through `core/events.ts`.
42+
`pi-handler.ts` is the sole entry point registered in the executor. It inspects the block's `mode` field and calls the matching backend's `run()` method. All backends receive a typed `PiRunContext` (from `core/backend.ts`) and stream incremental events back through `core/events.ts`.

0 commit comments

Comments
 (0)