SemianiakaVY/openpencil
1
0
Fork 0
Code Issues Pull requests Actions 1 Packages Projects Releases Wiki Activity
openpencil/packages/harness/AGENTS.md
Danila Poyarkov 19d01f0835
fix(harness): start Pi sessions with MCP tools under Node (#897) 
* fix(harness): start Pi sessions with MCP tools under Node

The desktop app always gives Pi OpenPencil's MCP server, and the
published companion failed every such session:

- @ai-sdk/harness-pi imports pi-mcp-adapter, which publishes only
  TypeScript sources, and Node refuses to strip types under
  node_modules. A module load hook now strips them for TypeScript
  dependencies only; Bun runs them as is. (vercel/ai#22040)
- pi-mcp-adapter imports @earendil-works/pi-tui but declares it as an
  optional peer, so npm leaves it out. The companion depends on it at
  the version pi-coding-agent uses, and a test keeps the two in step.
  (nicobailon/pi-mcp-adapter#805)
- Pi reports live-process resume, yet the service handed it state
  saved by an earlier session, and the just-bash sandbox cannot resume,
  so every later session with that ID failed. Live-process backends now
  start fresh and drop saved state.

Pi also installs the packages from a person's Pi settings with npm on
every session, writing npm's output to the companion's stdout. The
companion now keeps the real stdout for protocol messages, sends other
writes to stderr, and quiets npm on success. The app logs companion
stderr as diagnostics, since failures arrive as protocol errors.

* fix(harness): reject another backend's state before dropping it

loadResumeState removed saved state for a live-process backend before
createSession checked which backend owned it, so state saved by another
backend was lost instead of rejected. Ownership is checked first, and
only state that belongs to the live-process backend is dropped.
2026-10-05 17:21:50 +00:00

742 B
Raw Blame History

Harness

Optional Node companion for HarnessAgent sessions. Tauri launches the separately installed command; never bundle a JavaScript runtime into Tauri.

  • Keep the package backend-neutral.
  • Persist only opaque, non-secret resume state. Pi's in-memory just-bash cannot recover across process restarts.
  • Expose the bounded JSONL host protocol; changes to it must keep the desktop launcher and desktop/capabilities/** in sync (desktop/AGENTS.md).
  • stdout carries only protocol messages: write them through the writer reserveProtocolOutput() returns, and let other output, including npm runs Pi starts, go to stderr (tests/output.test.ts).
  • bun run test:tools runs this package's tests together with the repo tooling suites.