Project

General

Profile

Actions
Copy link

Bug #3898

open
« Previous | 1 of 34 | Next »

Fix navigation model ownership for explicit multi-agent setups

Added by Joshua Zhao 4 days ago. Updated 4 days ago.

Status:
New
Priority:
Normal
Assignee:
Joshua Zhao
Start date:
09/10/2026
Due date:
% Done:

0%

Estimated time:

Description

Identity Vault ambient model navigation must resolve the configured system agent in explicit multi-agent setups. Falling directly through resolveDefaultAgentId can fail because the SDK refuses to guess an owner.

Implemented behavior:
  • Resolve agents.defaults.systemAgent.agentId first and trim it.
  • Retain resolveDefaultAgentId as the fallback for older and sole-agent configurations.
  • Use the resolved owner for both model navigation decisions and prospect ranking.
  • Include regression coverage for configured system-agent ownership and the sole-agent fallback.

The implementation was originally committed as cf8d6f5e71843ddde2148bf7ee46c40445d385da without an issue reference. Correct its local commit message to reference this issue while preserving the source tree.

Completed source bookkeeping:
Corrected local commit: fd4798b12d62b1a0833c429974feba3142ee7da1 — Refs #3898: Fix navigation model ownership for explicit multi-agent setups.
Supersedes cf8d6f5e71843ddde2148bf7ee46c40445d385da. The source tree and existing commit body were preserved; this correction changes the issue reference only.
Included in local release tag v0.1.2; release tracking issue #3897. No push was performed.

Actions
Copy link

Also available in: Atom PDF