fix: treat absent harness.kind as pi_core to match runner default

[waterWang]

Description

When an agent config omits harness.kind, the runner treats the harness as pi_core — all seven Pi built-ins are active and the harness.permissions allow/ask/deny rules are enforced at runtime. However, the UI kept harnessValue as null when harness.kind was absent, making isPiHarness and hasPiPermissions evaluate to false, which hid the Pi permissions controls.

Fix

Changed the default value of harnessValue from null to pi_core when harness.kind is not a string, matching the runner's default behavior. This covers both:

• Absent harness.kind: {harness: {}} — the kind field is undefined
• Missing harness block entirely: the hook receives an empty default

Changes

- const harnessValue = typeof harness.kind === "string" ? (harness.kind as string) : null
+ const harnessValue = typeof harness.kind === "string" ? (harness.kind as string) : "pi_core"

Fixes #5661

[vercel]

@waterWang is attempting to deploy a commit to the agenta projects Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

Hi @waterWang, thanks for opening a pull request. 🙏

This PR was automatically closed because it does not yet meet our contribution requirements:

• The Summary section is missing or empty. Describe what changed and why using the PR template.
• This PR changes functional code (SDK, API, or frontend) but includes no demo. Add a screenshot or short video of the change. Only test-only, docs-only, or chore changes may skip it.

We ask for this so every change is documented and demonstrably tested before review.

How to get it reopened
Update the PR description (and add a demo recording if your change touches functional code). The bot reopens the PR automatically once the requirements are met. No need to open a new one.

See the Contributing guide and Creating your first PR. If you think this was closed in error, leave a comment and a maintainer will take a look.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ac8065bf-6393-4b91-b4a1-fe11d706ac20

📥 Commits

Reviewing files that changed from the base of the PR and between 99ab003 and d1c0a99.

📒 Files selected for processing (1)

• web/packages/agenta-entity-ui/src/DrillInView/SchemaControls/agentTemplate/useModelHarness.tsx

Disabled knowledge base sources:

• Linear integration is disabled

You can enable these sources in your CodeRabbit configuration.

---

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes
  • Improved model harness behavior by defaulting to the standard harness when no harness type is specified.

Walkthrough

The UI now defaults an absent harness.kind to "pi_core" in useModelHarness.

Changes

Harness selection

Layer / File(s)	Summary
Default harness selection web/packages/agenta-entity-ui/src/DrillInView/SchemaControls/agentTemplate/useModelHarness.tsx	useModelHarness now uses "pi_core" instead of null when harness.kind is absent or not a string.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• Agenta-AI/agenta#5461: This PR also modifies useModelHarness.tsx, but it changes model-label generation rather than harness defaults.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}