Changelog
Notes de Mise à Jour
Back to All

Fuel iX Copilots — Week 35 · August 24–30

August 31st, 2026 by Leonardo Fullana

This week brought a solid mix of new visibility tools and quality-of-life improvements. Admins and managers gain new ways to track costs and team performance, while everyday interactions get a little smoother with fixes to agent behavior and knowledge base management.

  • /cost command available by default in official copilots: The /cost command is now automatically enabled in organization default copilots and official assistants, so you can check AI usage costs without any extra setup. Find more about it on docs.fuelix.ai/docs/slash-commands.
    • Currently available only for TELUS organizations.

  • Detach Knowledge Bases from the selection interface: It's now possible to remove a Knowledge Base from a copilot's configuration directly from the selection screen, making it simpler to update or swap out the knowledge sources your agent uses.

  • No more unnecessary follow-up questions after completed tasks: The assistant no longer asks for clarification on tasks it has already carried out — for example, a reminder that's already been set won't prompt a follow-up question. Interactions should feel more accurate and less repetitive.

  • Improved access control for team management: Administrators now have more precise, role-based control over team resources, ensuring users can only access or modify the teams they're permitted to manage.

  • Team Performance tab and Daily Active Users chart: Managers and admins can now explore team performance across custom date ranges, including summary scores, skill breakdowns, and per-agent detail tables. The Account Overview tab also features a new Daily Active Users line chart with a shared date-range filter.

  • Consistent login redirects for protected pages: Users who aren't logged in are now reliably redirected to the login page when trying to access protected areas of the developer and admin portals.

  • More reliable file deletion behavior: Fixed an issue where deleting a file that had already been removed could surface a false error. These operations now behave correctly and consistently.