feat(labs): pi agent instead of opencode

[benjaminshafii]

Summary

• add a new apps/openwork-host package: a PI-backed single-workspace host server with health, session, message, prompt, abort, and SSE event routes
• wire Labs local workspaces in this branch to prefer openwork-host as the runtime, while keeping remote OpenWork/OpenCode server URLs as-is
• keep the existing Electron kernel abstraction and make it spawn openwork-host locally, then talk to it through the same OpenCode-style route subset the UI already expects

Validation

• pnpm --filter openwork-host typecheck
• pnpm --filter openwork-host build
• pnpm --filter @openwork/labs typecheck
• pnpm --filter @openwork/labs build
• direct kernel smoke test from the worktree returned a connected local runtime:
  • runtime: openwork-host
  • status: connected
  • sessions: 0

Notes

• this PR is stacked on top of feat(labs): add microsandbox workspace runtime #1303
• the PI host server is intentionally narrow: single workspace, in-memory session state, and a small OpenCode-compatible route subset for Labs
• I did not complete Docker stack + Chrome MCP verification for this branch
• prompt success still depends on PI-compatible model/auth configuration being available in the environment used by openwork-host

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-app	Ready	Preview, Comment	Apr 3, 2026 5:54am
openwork-den	Ready	Preview, Comment	Apr 3, 2026 5:54am
openwork-den-worker-proxy	Ready	Preview, Comment	Apr 3, 2026 5:54am
openwork-landing	Ready	Preview, Comment, Open in v0	Apr 3, 2026 5:54am
openwork-share	Ready	Preview, Comment	Apr 3, 2026 5:54am

[github-actions]

The following comment was made by an LLM, it may be inaccurate: