Chatti Live – Agent
⚠ DEPRECATED (2026-03-15)
This route concept is deprecated. Individual agent configuration is now handled via the Agent edit modal in the workspace Agents tab. See Workspace – Agents Tab.
Route (deprecated)
Section titled “Route (deprecated)”- Path:
/chatti-live/agents/:agentId(never shipped) - Parent:
agents.md
Purpose (business goal)
Section titled “Purpose (business goal)”View and configure an individual agent’s settings, permissions, and routing behavior.
User roles & permissions
Section titled “User roles & permissions”- Manager, Workspace Admin
- Permissions:
agents.manage(TBD)
Reference: Roles & Permissions Model
Layout structure
Section titled “Layout structure”- Agent profile summary
- Configuration panels (routing, skills, permissions) (TBD)
Components used
Section titled “Components used”- Agent Configuration: Component: Agent Configuration
States
Section titled “States”- Empty: N/A (agent id required)
- Loading: fetch agent
- Error: not found / permission denied
- Complete: agent configuration displayed
Business logic (high-level)
Section titled “Business logic (high-level)”- Agent configuration influences assignment logic.
Domain refs: Domain: Chatti Live
API dependencies
Section titled “API dependencies”GET /agents/{id}PUT /agents/{id}
Enterprise constraints
Section titled “Enterprise constraints”- Agent configuration is workspace-scoped and may affect routing/outbound behavior.
- Changes must be auditable and attributable.
Edge cases
Section titled “Edge cases”- Agent has active assignments; deactivation and reassignment behavior is TBD.
- Concurrent edits to agent configuration; conflict handling is TBD.
Security & compliance considerations
Section titled “Security & compliance considerations”- Audit configuration changes
Reference: Security & Compliance
Analytics events (if applicable)
Section titled “Analytics events (if applicable)”TBD
Reference: Analytics Events (MVP)