Add agent harnesses using AI SDK HarnessAgent#890
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Fix/harness session keying
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
Multiple chats in one session share the sandbox, but the harness bridge used a single hardcoded port (5001), so concurrent external-harness runs would collide. Expose a pool of bridge ports (5001-5008) and hand it to the AI SDK harness, which leases one port per concurrent session. Also exclude the whole pool from dev-server-eligible ports. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The external-harness ownership claim enforced one active harness per session, which blocked the legitimate case of multiple chats (tabs) running concurrently in the same shared sandbox. Now that each chat leases its own bridge port, the claim is unnecessary and harmful. Removes the workflow claim/release, the dedicated db helpers, and the ownership module. Leaves the activeHarnessRunId column in place (no migration); it is simply unused. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…-claim Fix/harness remove ownership claim
fix(harness): lease bridge ports from a pool for concurrent chats
Uses the new AI SDK harness support to add agent harnesses like:
Tries to map to Open Agents tool calls where possible. Also adds snapshot pre-warming.