Central service for connecting AI agents to our websites. It stores websites, agents, and chats, facilitates communication between visitors and the agent, and allows managers to participate. Additionally, it receives raw events from websites for subsequent analysis by the agents.

Unified AI agents and chats service for our websites.

AI Agents Center

Implement client-side integration for our websites: a visitor opens a chat on the site, messages are sent to the central agent, and responses are returned to the website interface. Connecting a new website should require minimal manual configuration.

Create a simple way to connect our websites to the central service.

Connect an AI agent to websites

Create an interface where active and past visitor dialogs with the agent can be viewed. A manager must be able to stop automated responses, continue the conversation manually, and then return control to the agent.

Personal account for viewing dialogs and human participation.

Implement dialog management and manager takeover

Store the list of our connected websites, their agents, and core context. The central agent needs the ability to understand which websites and agents exist and to communicate with the appropriate agent.

A unified internal directory of connected websites and their agents.

Add website and agent directory

# Create your own embedded chat widget

## Objective
Create a minimal custom chat UI that can be embedded into our websites and connected to the already implemented server-side HTTP/agent layer without using the old interface as a permanent solution.

## What to Implement
- a simple way to embed the widget on a website with minimal manual configuration;
- sending user messages to the central service;
- streaming display of the agent's response;
- a Stop button with actual cancellation of the current execution;
- correct UI states for started / streaming / done / error / cancelled;
- basic transmission of the website identifier and page context;
- defining a visitor/session identification contract without mixing the states of different tabs and users;
- defining CORS and the access model for the public HTTP endpoint for the external widget;
- testing operation through a real proxy path, not just directly to the application.

## Out of Scope for the Minimum Viable Phase
- manager dashboard;
- full conversation history in the UI;
- complex analytics;
- visual agent builder.

## Definition of Done
- the widget connects to at least one test website without using the legacy chat;
- responses are streamed;
- Stop actually cancels the server-side execution;
- parallel visitors do not mix states;
- streaming and cancellation have been tested through a working Traefik/Varnish/proxy path;
- the connection contract is documented so that the next website can be added without modifying the core.

A minimal widget for connecting to websites via a central agent with streaming responses and Stop functionality.

Create your own embedded chat widget

# User Admin Panel and JWT Token Management

## Context
The main subsequent goal is to manage JWT tokens, which are used to identify the user to whom a message is addressed.

Server requests for working with users already exist. As part of the first stage, do not refactor the user backend.

## First Stage — To Be Completed Now
Create a user management admin panel:

- user list;
- "Add user" action;
- ability to open a user card;
- user editing;
- use existing GraphQL queries and mutations;
- add client-side GraphQL operations and regenerate types.

## UI-kit
Along the way, start building a custom `ui-kit` on top of the already installed React Aria:

- use React Aria as a headless foundation;
- implement each UI component required by the application as a separate component in `ui-kit`;
- immediately add a Storybook story for each new component;
- use components from `ui-kit` in product screens rather than React Aria directly.

## Next Stage — JWT Tokens
Following the user admin panel, add management for JWT tokens intended to identify the user to whom a message is sent. Do not mix this task with the existing login and session logic.

## Technical Notes
- Hot reload is already working, no separate configuration is needed.
- React Aria is already installed.
- User CRUD backend already exists.

## First Stage Acceptance Criteria
From the interface, the administrator can view users, add a user, open an existing user, and modify their data. Client-side GraphQL operations have been added, types are successfully regenerated, and the UI elements used are structured via `ui-kit` and have Storybook stories.

Create a user management admin panel and lay the UI foundation for subsequent management of user identification JWT tokens.

Tasks

Add user management admin panel and prepare JWT token management

Create your own embedded chat widget

Add website and agent directory

Implement dialog management and manager takeover

Connect an AI agent to websites