Vaia - logged in user identity is not passed into the prompt context - requests require extra MCP tool calls

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

The AI Agent prompt exposes five user context tokens, language, locale, timezone, date_format and unit_of_measure, and carries no logged in user name, user id or resource id. A user scoped request such as "my open tasks on this project" cannot filter by the current user without first running MCP calls

STEPS TO REPRODUCE:

1. Connect to an environment with Vaia enabled
2. Create a new AI Agent with Type Project, Context Object Chat panel, Tool enabled Yes, Allow User Input Yes
3. Set the agent prompt to the text below
   You are a Clarity PPM assistant for the project with code $[project.unique_code]Help the user with questions about this project's tasks, staff and status.Never guess an id, code or attribute name.
4. Open a Project in the Modern UX, go to its Tasks, and assign at least one open task to the user who will run the test as Assigned Resource and also Task Owner.
5. As that user, open the same Project. The AI chat panel icon and the free-form input box are shown.
6. In the chat panel ask: What are my open tasks on this project?
7. Watch the tool call trace on that response.

Expected Results: The agent has the signed in user's resource id in context and returns that user's open tasks on the project in a single filtered data fetch. 
Actual Results: The agent has no user identity in context, so to resolve the user it first runs extra tool calls to find out who the caller is before it can filter tasks by resource id. With no reliable identity it may filter on the wrong resource,  ask the user to identify themselves or indicate there were no tasks found

Environment

Clarity 16.4.3

Cause

DE211472

Resolution

In Review by Engineering