Все статьи

Getting Started

Что такое CICDoo Начало работы: мастер настройки Панель и карта инфраструктуры

Concepts

Стадии: продакшн, staging и разработка Домены, поддомены и SSL Версии и редакции Odoo (Community или Enterprise) Воркспейсы и командная работа

Servers

Добавление сервера Домены сервера и DNS Использование балансировщика нагрузки Действия с сервером: деплой, логи и графики Deleting a server

Projects & Git

Создание проекта Подключение GitHub Project GitHub settings and webhook Подключение GitLab Ветки и инстансы Теги и фильтрация проектов Высокая доступность с узлами приложения Project environments, extensions and deletion

Instances & Console

Создание инстанса Перезапуск, остановка и удаление инстанса Слияние веток между стадиями Web IDE и удалённый доступ SSH access to instances Настройки инстанса Деплои и очередь задач

Agent Tasks

Что такое задачи агента Настройка задач агента Запуск задачи и разбор результата Время агента и его пополнение Agent insights and task filters

Monitoring & Backups

Мониторинг инстанса Резервные копии и восстановление S3 storage, uploads and bulk backup actions Уведомления об инцидентах (email и SMS)

Workspaces & Permissions

Приглашение участников в воркспейс Права участников и доступ к ресурсам Участник не видит ресурс или не может им пользоваться Audit log and server activity

Account & Security

Двухфакторная аутентификация (2FA) Настройки профиля и интеграций Пароли и восстановление доступа

Billing & Plans

Тарифы и цены Повышение тарифа и управление подпиской Если подписка на проект не оплачена Партнёрская программа Onboarding a client as a partner

Support & Tickets

Создание тикета в поддержку Помощь от команды CICDoo

Troubleshooting

Устранение неполадок: не удаётся подключить сервер Устранение неполадок: деплой завершился ошибкой Устранение неполадок: git push возвращает 403 после переноса репозитория Устранение неполадок: инстанс недоступен или работает медленно Устранение неполадок: проблемы с доменом или SSL

Agent Tasks

Agent insights and task filters

Using the Agents page and a project's Dashboard tab to see agent activity, tokens and agent time over a period, and filtering the task list by project, person, CLI and state.

Agent insights show what your agents have done over a period: how many tasks finished and how, how many tokens they used, and how much agent time went into planning and execution. The same charts appear in two places:

  • Across all projects: the "Agents" item in the main menu opens the "Agent" page, covering every project in the workspace that you can see agent tasks on.
  • For one project: the project's "Agent Tasks" page has a "Dashboard" tab, shown once agent tasks are enabled on that project.

You need the "Agent tasks" permission on at least one project for the "Agents" menu item to appear.

Opening the insights

  1. Click "Agents" in the main menu, or open a project's "Agent Tasks" page from the console sidebar.
  2. Click the "Dashboard" tab if it is not already open.
  3. Read the totals at the top of the "Insights" card: "Tasks", "Tokens" and "Agent time" for the chosen period.

If nothing has run in the period, the card says "No agent activity in this period yet." Charts appear once tasks have finished planning or executing.

Choosing the time range

  1. In the "Insights" card header, click "30 days", "90 days" or "12 months".
  2. For a custom range, fill in both date boxes next to these buttons (from and to). The charts reload once both dates are set.
  3. Click "Clear" to drop the custom range and go back to the last 30 days.

Reading the charts

  • "Tasks by outcome": tasks over time, split into "Executed", "Failed" and "Cancelled".
  • "Token consumption": tokens over time, split into input, output, cache read and cache write.
  • "Agent time by phase": agent time split between "Planning" and "Execution". Agent time is what your hours are drawn down by; see Agent time and top-ups.
  • "Consumption by CLI": compares the coding CLIs your tasks ran on. Use the buttons beside the title to switch the measure between "Agent time", "Tasks" and "Tokens". This chart is hidden when a single CLI did all the work in the period.
  • "Tasks by person" and "Activity by person": tasks per person over time, and people ranked by the chosen measure, so you can see who is setting the agent to work. "Activity by person" has the same "Agent time", "Tasks" and "Tokens" switch. Both are hidden when no task in the period is attributed to a person.

Filtering the task list

The task list is on the "Tasks" tab of the Agents page, and on the "Tasks" tab of a project's Agent Tasks page.

  1. Click the "Tasks" tab.
  2. Use the dropdowns above the list. The list reloads as soon as you change one:
    • Project: pick one project, or "All projects". Only on the Agents page.
    • Person: pick who the task is attributed to, or "Anyone". Shown once tasks have people against them.
    • Agent CLI: pick a CLI, or "All CLIs". Shown only when tasks used more than one CLI.
    • State: pick a task state, or "All states".
  3. Click a task to open it.

The list shows each task's instance, CLI, state, who created it, its last activity, tokens, time and creation date. An "Auto" badge marks tasks set to auto-execute. If no task matches, the list says "No tasks match these filters." with a "Clear filters" button.

If the Agents page is empty

When no project in the workspace has agent tasks enabled, the Agents page shows "Let an agent do the work" with the three setup steps instead of charts.

  1. Click "Set up agents". It opens the Agent tab of the first project whose settings you can change. If you cannot change any project's settings, the button reads "Choose a project" and opens the Projects page instead.
  2. Follow Setting up agent tasks.

Related: What agent tasks are, Running a task and reviewing the result, Agent time and top-ups, Member permissions and resource access.

If you get stuck, open a support ticket from the Tickets page or the chat widget.

Назад Время агента и его пополнение Далее Тарифы и цены

Всё ещё не получается? Откройте тикет из приложения или свяжитесь с инженером.