Alle Artikel
Getting Started
Was ist CICDoo Erste Schritte: der Onboarding-Assistent Das Dashboard und die InfrastrukturkarteConcepts
Produktions-, Staging- und Development-Stages Domains, Subdomains und SSL Odoo-Versionen und -Editionen (Community vs. Enterprise) Workspaces und TeamzusammenarbeitServers
Einen Server hinzufügen Server-Domains und DNS Einen Load Balancer verwenden Server-Aktionen: Deploy, Logs und Diagramme Deleting a serverProjects & Git
Ein Projekt erstellen GitHub verbinden Project GitHub settings and webhook GitLab verbinden Branches und Instanzen Projekte mit Tags versehen und filtern Hochverfügbarkeit mit App-Knoten Project environments, extensions and deletionInstances & Console
Eine Instanz erstellen Eine Instanz neu starten, stoppen und entfernen Branches zwischen Stages mergen Web-IDE und Fernzugriff SSH access to instances Instanzeinstellungen erklärt Deployments und die Job-WarteschlangeAgent Tasks
Was Agent-Aufgaben sind Agent-Aufgaben einrichten Eine Aufgabe ausführen und das Ergebnis prüfen Agent-Zeit und Aufstockungen Agent insights and task filtersMonitoring & Backups
Deine Instanz überwachen Backups und Wiederherstellung S3 storage, uploads and bulk backup actions Warnbenachrichtigungen (E-Mail und SMS)Workspaces & Permissions
Workspace-Mitglieder einladen Mitgliederberechtigungen und Ressourcenzugriff Ein Mitglied kann eine Ressource nicht sehen oder nutzen Audit log and server activityAccount & Security
Zwei-Faktor-Authentifizierung (2FA) Profil- und Integrationseinstellungen Passwörter und KontowiederherstellungBilling & Plans
Tarife und Preise Dein Abonnement upgraden und verwalten Wenn ein Projekt-Abonnement unbezahlt bleibt Das Channel-Partner-Programm Onboarding a client as a partnerSupport & Tickets
Ein Support-Ticket eröffnen Hilfe vom CICDoo-Team erhaltenTroubleshooting
Fehlerbehebung: Server kann nicht verbunden werden Fehlerbehebung: ein Deployment ist fehlgeschlagen Fehlerbehebung: git push schlägt mit 403 fehl nach Verschieben eines Repositorys Fehlerbehebung: meine Instanz ist ausgefallen oder langsam Fehlerbehebung: Domain- oder SSL-ProblemeAgent 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
- Click "Agents" in the main menu, or open a project's "Agent Tasks" page from the console sidebar.
- Click the "Dashboard" tab if it is not already open.
- 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
- In the "Insights" card header, click "30 days", "90 days" or "12 months".
- For a custom range, fill in both date boxes next to these buttons (from and to). The charts reload once both dates are set.
- 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.
- Click the "Tasks" tab.
- 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".
- 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.
- 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.
- 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.
Kommst du nicht weiter? Erstelle ein Ticket in der App oder sprich mit einem Techniker.