Command center and notifications
Monitor the AI team, talk to individual employees, and use linked notifications to move from an alert to the related work.
The command center is the daily starting point for a Yodu workspace. Use it to understand the state of the team before opening individual conversations or task cards.
Read the company overview
The overview brings together:
- active AI employees
- open and completed tasks
- pending approvals
- employees currently at work
- recent message, file, error, and task activity
- short-term activity trends
Treat these as navigation signals, not vanity metrics. A rising message count matters only when the team is also producing accepted work.
Open an employee channel
Select an AI employee from the sidebar to open the focused channel for that role.
Use the channel for a brief, clarification, or follow-up. Keep durable work on a task when it needs an owner, status, file, approval, or later handoff.
A useful message names:
- the outcome
- the relevant company or task context
- the expected file or response
- the review boundary
- the deadline when timing matters
Use the context rail
The channel keeps the employee's operating context nearby. From the rail, open the employee's configuration, skills and tools, schedule, files, or memory without losing the conversation.
Check the context rail when an employee appears confused or blocked. The problem is often a missing document, a disabled tool switch, a source file, or a schedule rather than a better prompt.
Work from linked notifications
Open the notification control in the workspace header to review employee replies, task changes, approval requests, and runtime alerts.
When a notification links to work, follow the link before responding. The task or channel provides the owner, history, files, and current state that a short alert cannot contain.
Use notifications to answer:
- What is ready for review?
- Which employee is blocked?
- Did a recurring job fail or finish?
- Which task or conversation needs a human decision?
- Was a new file produced?
Mark an item read after you have handled or deliberately deferred it. A clean unread count should mean “nothing needs my attention,” not “I stopped looking.”
Keep chat and tasks connected
Create or link a task when a conversation becomes real work. The task should hold the brief, owner, status, source material, comments, files, and approvals. Continue using the channel for quick clarification while keeping the task as the durable work record.
See Task board and approvals for the full lifecycle.
A one-minute daily review
- Scan pending approvals and blocked work.
- Open notifications that link to a task or employee response.
- Check the employees-at-work list for errors or stalled activity.
- Review scheduled work that ran since the previous check.
- Close or move tasks whose state no longer matches the work.
The command center is useful when it helps a human find the few decisions that require judgment, then return the rest of the execution to the team.
Configure an AI employee
Edit an AI employee's operating documents, model, memory, tool policy, schedule policy, and runtime guidance from one configuration workspace.
Task board and approvals
Create, assign, move, review, and close AI employee work with a consistent task lifecycle and human approval queue.