Project management

Projects are the main unit of work: one chat product’s LLM defaults, board graph, agents, project-level tools, and inbox links live together.

This page follows BoardLayout left-to-right: rails, canvas, detail panels, test mode, AI Builder.

Project list (/projects)

• Cards/list of your org’s projects.
• Create is usually ORG_ADMIN + subscription projects limits; members may edit but not create.
• Open detail at /projects/[id] for board + settings.

Screenshot

Project card grid — include search/filter if your UI has it.

Create / edit project

Typical fields (aligned with API DTOs):

• Name and description
• System prompt — default behavior when agents do not override
• LLM config — model, temperature, maxTokens, topP; stay inside the plan allowedModels

After create, dashboard activity may log PROJECT_CREATED (deployment-dependent).

Board layout (BoardLayout)

The board runs inside the React Flow provider. Main regions:

Region	FE file	Role
Header	board-header	Name, save state, shortcuts
Left rail	board-sidebar	Node palette / nav
Canvas	board-canvas	Drag/drop graph
Right panel	board-detail-panel	Selected node/edge fields
Settings	board-settings-panel	Global project settings tab
Test	test-mode-panel	Send messages + highlights
AI Builder	ai-builder-panel / ai-builder-chat	NL session
Inbox	inbox-detail-panel	Inbox detail

Selecting a node opens the matching form in the detail panel: agent edit, tool wiring, integration secrets, etc.

Node types (operations)

Type	Tip
Router	Intent split; write routing copy with test users
Sub-agent	Persona / responsibility split
Tool	Function calling to HTTP/KB
Integration	Shared base URL + auth
Knowledge base	Makes the RAG path visible
Inbox	Which platform line binds here

Edges represent sequencing / “next step” semantics — confirm with your version docs.

Screenshot

Canvas + selected node + right panel is the key trio.

Project tools and linking

• Project tools are defined once; link/unlink them to agents (onLinkTool, onUnlinkTool).
• Tool dialogs may include proxy/security tabs — follow corporate policies for outbound HTTP.

Test mode

Via TestModePanel:

1. Type a user message and send.
2. The backend test queue / SSE stream responds (deployment-dependent).
3. A highlight map (NodeHighlightState) may color which agent/tool fired.

Success: Replaying the same input shows a stable execution path; inconsistency usually means router copy or missing edges.

Not production-identical

Test mode does not always mirror live traffic — human handoffs and queue latency differ.

AI Builder

Chat in a side panel to shape the project; backend lives under projects/:appId/builder. Never ship without verifying the board.

See AI Builder.

Live chat linkage

• Bind projects to inboxes and manage live agent assignments via API + admin UI.
• Channel events are handled through the platform webhook ingress; workers process messages.

See Live chat and messaging.

Chat route (/projects/[id]/chat)

Some builds expose a simplified chat test page separate from the board.

API and activity

• CRUD: Projects endpoints
• Activity: Dashboard API

Next steps

• Agents
• Tools
• Orchestration