[Story] Context Budget Configuration for Agents and Pipelines

[epamLDadayan]

User Story: Context Budget Configuration for Agents and Pipelines

Description:

As a user, I want to configure Context Budget for each run of Agents and Pipelines, allowing me to manage and limit context usage. This configuration should be available from the Run Tab and Configuration Tab in both menus. The entire setup process must be intuitive, matching the workflow in the Chat menu (Conversations), with settings enabled at the project level.

---

Acceptance Criteria:

1. Context Budget Enablement:

• By default, the Context Budget feature is disabled for the entire project unless explicitly enabled in Project Settings → Secrets Page.
• Users can toggle Context Budget on or off in the Run Tab and Configuration Tab of both the Agents Menu and Pipelines Menu.

2. Context Budget Card in UI:

• Add a dedicated Context Budget Card for both Agents and Pipelines menus in:
  • Run Tab.
  • Configuration Tab.
• The card must include:
  • A description of the feature (e.g., "Manage and limit the context usage for each run of the Agent or Pipeline").
  • A pencil icon to allow editing Context Budget settings.

3. Context Budget Settings Modal:

• When the pencil icon on the Context Budget Card is clicked, a Context Management Settings modal opens. In the modal, users can:
  • Enable/Disable Context Budget.
  • Configure context-specific limits and thresholds (e.g., maximum token limit).
  • Apply changes using an Apply button or discard changes using a Cancel button.

4. Real-Time Application of Changes:

• Any changes made in the Context Management Settings modal are reflected immediately:
  • In both the Run Tab and Configuration Tab.
  • In the next execution of the selected Agent or Pipeline run.

5. Parity with Chat Menu Design:

• The design and workflow for configuring Context Budget must align with the existing implementation in the Chat Menu (Conversations).
• Ensure a consistent user experience across all menus (Chat, Agents, Pipelines).

6. Access Restriction:

• If Context Budget is disabled at the project level, the card and settings related to Context Budget are not visible in the Agents and Pipelines menus.
• A tooltip or inline message should specify, "Enable Context Budget from Project Settings → Secrets Page to access this configuration."

---

Notes for Developers and QA:

1. Backend Ready:

   • The backend functionality for Context Budget is already implemented. Ensure seamless integration with the frontend during development.

2. Modal Consistency:

   • The Context Management Settings modal must follow the same UX/UI design and behavior as implemented in the Chat → Conversations menu.
   • Make sure to provide real-time previews or error messages while users configure settings (e.g., warnings for invalid token limits).

3. UI Elements:

   • Verify the proper placement of the Context Budget Card in both the Run Tab and Configuration Tab for Agents and Pipelines menus. Double-check visibility states and enablement based on the project's configuration setting.

---

Design Links:

• https://www.figma.com/design/5vWxC85QBhqbzPU30RP7LH/Alita.-Prompt-Library?node-id=19289-310240&p=f&t=wHXGXCuAAhpZwRhC-0