
Agent overview
See total agent usage and spend at a glance.
Total expense, token use, sessions, provider ratio, most-used agents, and failed runs reveal the operating mix behind AI work.
AI agent teams
Give every specialist a clear role, model, memory, tools, project access, and budget—then bring that agent into the work.
See what agents can do
What it covers
A clear role, chosen model, memory, capabilities, and access rules travel with the agent wherever it appears.
Create, clone, import, export, group, and template agents with stable role and instruction definitions.
Select provider profiles and models per agent, with runtime setup verification before use.
Configure memory behavior, image generation, and provider-supported voices independently for each agent.
Separate permissions cover project reads, project creation, subprojects, task changes, broader structure, processes, workspace files, storage catalogs, and secret references.
Attach tools, skills, and MCP servers from one searchable catalogue while keeping the assigned surface inspectable.
Open focused or floating chats from projects, Gantt, workflows, processes, calendars, and scheduler surfaces.
Use the built-in HR agent to identify the right specialist and help create or configure agents for the work.
Review approvals, artifacts, checkpoints, tool receipts, logs, usage, known cost, and recent failures.
Bind a CRM / HR AI party to a technical agent so organizational roles resolve to a governed runtime identity.
Agent settings
Start with identity and runtime. Add only the memory, tools, project access, secrets, process access, and voice that the role needs.

Use the arrows or choose a setting to inspect the current interface. Selecting a step stops the automatic tour and keeps that screen in place.
Agent and project analytics
CanDoItAll captures activity from chats, workflows, and processes and, whenever project context is available, attributes that activity to the project that authorized it.
Compare providers and agents, review project history against the remaining plan, search process cost over time, and ask a process manager about a specific run.
The deeper Economy module is planned for later. Today’s operational records keep the available cost trail—and any unknown or estimated values—visible.

Agent overview
Total expense, token use, sessions, provider ratio, most-used agents, and failed runs reveal the operating mix behind AI work.

Project costs
Known and estimated history sit beside planned cost, category ratios, recent activity, and trends for the selected project scope.

Plan exposure
The Gantt view keeps task dependencies, delivery and pure effort, assignments, dates, and expected cost in one planning scope.

Activity costs
Filter agents, workflows, or processes by outcome to review activity time, known cost, recorded estimates, and status.

Process trends
History filters reveal cost, token, runtime, manager-signal, and tool-usage patterns across process runs.

Ask a run
A run-scoped manager can explain actual cost, token breakdown, outcome, and execution context without leaving process history.
Retain provider, model, tokens, duration, status, known cost, estimates, and run context for conversations and automated work.
Connect chats, agents, workflows, processes, people, and planned work to the project scope whenever the relationship is available.
Move from summary ratios and trends to individual activities, then ask the process manager about the exact run that needs attention.
How it connects
Microsoft Agent Framework provides the core runtime for agent execution and orchestration. CanDoItAll adds the adoption layer around it: reusable agent identities, provider profiles, voice, permissions, project assignments, budgets, cost tracking, and governance.