fix(pi): preserve cloud model selection

[jonathanlab]

Problem

Cloud Pi tasks did not use the selected model at start. After a renderer reload, the Pi picker could show only the saved model.

Cloudflare GLM 5.2 also failed before responding because LiteLLM interpreted the client-side web_search tool as native web search and forwarded unsupported web_search_options.

Changes

• Send the selected model and thinking level when a cloud Pi task starts.
• Reapply the deferred model and thinking level after a cloud sandbox retry replaces the session.
• Use the PostHog provider catalog for Pi pickers.
• Add the harness source alias to the web Vite build.
• Save model changes when a cloud sandbox is inactive. Apply them before the next prompt starts the sandbox.
• Move PostHog Pi catalog code from the agent package to the provider extension.
• Rename the client-side web search tool to posthog_web_search so LiteLLM does not treat it as a native web-search tool for GLM.
• Preserve legacy web_search subagent tool settings by translating them to the new tool name.

Validation

• pnpm --filter @posthog/harness build
• pnpm --filter @posthog/harness test
• pnpm --filter @posthog/core test -- piSessionController.test.ts
• pnpm --filter @posthog/web build

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

[trunk-io]

😎 Merged successfully - details.

[github-actions]

React Doctor found 1 issue in 1 file · 1 warning.

1 warning

src/features/pi-sessions/PiSessionView.tsx

• ⚠️ src/features/pi-sessions/PiSessionView.tsx:419 JSX element passed as a prop jsx-no-jsx-as-prop

_{Reviewed by React Doctor for commit e8f8e2a.}

[greptile-apps]

Comments Outside Diff (1)

1. packages/core/src/pi-runtime/piSessionController.ts, line 1146-1148 (link)

   Deferred config lost on retry

   When the initial send fails with "No active sandbox", this retry replaces the session without reapplying the deferred model and thinking level. The prompt then runs with the previous configuration, and the successful submission causes the UI to clear the user's pending selection.

   Context Used: CLAUDE.md (source)

   Knowledge Base Used: Shared foundation: packages/shared, packages/core, packages/di

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: packages/core/src/pi-runtime/piSessionController.ts
   Line: 1146-1148
   
   Comment:
   **Deferred config lost on retry**
   
   When the initial send fails with "No active sandbox", this retry replaces the session without reapplying the deferred model and thinking level. The prompt then runs with the previous configuration, and the successful submission causes the UI to clear the user's pending selection.
   
   **Context Used:** CLAUDE.md ([source](https://github.com/posthog/code/blob/main/CLAUDE.md))
   
   **Knowledge Base Used:** [Shared foundation: `packages/shared`, `packages/core`, `packages/di`](https://app.greptile.com/posthog-org-19734/-/custom-context/knowledge-base/posthog/code/-/docs/shared-foundation.md)
   
   ---
   
   For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Prompt To Fix All With AI

### Issue 1
packages/core/src/pi-runtime/piSessionController.ts:1146-1148
**Deferred config lost on retry**

When the initial send fails with "No active sandbox", this retry replaces the session without reapplying the deferred model and thinking level. The prompt then runs with the previous configuration, and the successful submission causes the UI to clear the user's pending selection.

### Issue 2
apps/web/src/web-host-router.ts:7
**Harness import bypasses web alias**

The web production build resolves workspace subpaths through `posthogSrcAliases` because their fallback exports do not resolve under Rollup, but the new `@posthog/harness` import has no corresponding alias. As a result, the web build cannot resolve this module.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "fix(pi): preserve cloud model selection" | Re-trigger Greptile}

[greptile-apps]

Harness import bypasses web alias

The web production build resolves workspace subpaths through posthogSrcAliases because their fallback exports do not resolve under Rollup, but the new @posthog/harness import has no corresponding alias. As a result, the web build cannot resolve this module.

Context Used: CLAUDE.md (source)

Knowledge Base Used:

• apps/web and apps/mobile: browser and mobile clients
• Harness (hog/harness CLI)

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/web/src/web-host-router.ts
Line: 7

Comment:
**Harness import bypasses web alias**

The web production build resolves workspace subpaths through `posthogSrcAliases` because their fallback exports do not resolve under Rollup, but the new `@posthog/harness` import has no corresponding alias. As a result, the web build cannot resolve this module.

**Context Used:** CLAUDE.md ([source](https://github.com/posthog/code/blob/main/CLAUDE.md))

**Knowledge Base Used:**
- [apps/web and apps/mobile: browser and mobile clients](https://app.greptile.com/posthog-org-19734/-/custom-context/knowledge-base/posthog/code/-/docs/client-apps-web-mobile.md)
- [Harness (`hog`/`harness` CLI)](https://app.greptile.com/posthog-org-19734/-/custom-context/knowledge-base/posthog/code/-/docs/harness-cli.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[tatoalo]

Cloudflare GLM 5.2

Is this a worker limitation on CF side or model-wide? meaning, will this impact the baseten rollout as well?

[jonathanlab]

Cloudflare GLM 5.2

Is this a worker limitation on CF side or model-wide? meaning, will this impact the baseten rollout as well?

Cloudflare specific limitation