All articles

Getting Started

What is CICDoo Getting started: the onboarding wizard The Dashboard and Infrastructure Map

Concepts

Production, staging and development stages Domains, subdomains and SSL Odoo versions and editions (Community vs Enterprise) Workspaces and team collaboration

Servers

Adding a server Server domains and DNS Using a load balancer Server actions: deploy, logs and charts

Projects & Git

Creating a project Connecting GitHub Connecting GitLab Branches and instances

Instances & Console

Creating an instance Restarting, stopping and removing an instance Merging branches between stages Web IDE and remote access Instance settings explained Deployments and the job queue

Agent Tasks

What agent tasks are Setting up agent tasks Running a task and reviewing the result Agent time and top-ups

Monitoring & Backups

Monitoring your instance Backups and restore Alert notifications (email and SMS)

Workspaces & Permissions

Inviting workspace members Member permissions and resource access A member cannot see or use a resource

Account & Security

Two-factor authentication (2FA) Profile and integrations settings Passwords and account recovery

Billing & Plans

Plans and pricing Upgrading and managing your subscription If a project subscription goes unpaid The channel partner program

Support & Tickets

Opening a support ticket Getting help from the CICDoo team

Troubleshooting

Troubleshooting: cannot connect a server Troubleshooting: a deployment failed Troubleshooting: git push fails with 403 after moving a repository Troubleshooting: my instance is down or slow Troubleshooting: domain or SSL problems

Agent Tasks

Agent time and top-ups

How agent time is measured, what your projects include, how the allowance and purchased credit work together, and what happens when you run out.

How agent time is measured

Agent tasks are metered by time, not by tokens. Each run of the agent, whether it was planning or implementing, contributes the time it actually spent working.

Runs that succeeded and runs that failed both count: they used the same resources, and a task that took four attempts genuinely cost four attempts. Runs that failed on our side do not count, so a timeout against our own limit, a container that died mid-work, or a run that produced unusable output are not charged to you.

Where the hours come from

There are two pools, and they are used in a fixed order.

  1. Your plan allowance. Every project includes agent hours. The allowance resets each billing month and does not carry over.
  2. Purchased credit. Hours you have topped up. Credit never expires and is only touched once the allowance for the month is spent.

Both belong to the billing account, not to a single project, and are shared across every project that account owns. That is why the balance lives on Settings → Billing rather than on one project's settings.

The Billing tab shows all three figures: allowance left of the month's total, credit balance with what has been added and used, and the two added together as what is actually available.

Topping up

On Settings → Billing, the Agent hours card offers top-up packs. Bigger packs carry a discount, and the exact figures are shown on the buttons themselves. Payment goes through Stripe, and the hours land on the balance as soon as it clears.

Purchased hours never expire, so a top-up is not a use-it-or-lose-it commitment the way the monthly allowance is.

Running out

When the balance reaches zero, queued tasks stay queued. They are not cancelled and not lost; the agent simply stops picking new work up until there are hours again. Anything already running finishes.

Top up, or wait for the monthly allowance to reset, and queued tasks start again on their own.

If you are not the workspace owner you will not see the top-up buttons. Ask the owner to top up.

What else can stop a task

Agent time is only one of the things that has to be in order:

  • The project's subscription. If a project has gone read-only or been stopped for non-payment, agent tasks are refused there along with every other action. See If a project subscription goes unpaid.
  • Your provider's own limit. The agent runs on your Claude, Gemini or OpenAI account. If that account hits its usage limit, the task pauses and tells you when it resets, separately from anything to do with CICDoo hours.
  • Configuration. A project with agent tasks switched off, or with no credential stored, has nothing to run tasks with.

What it costs

Agent hours are priced separately from platform access. The current rate and the pack prices are shown on the top-up card in your account, before you buy anything. Projects themselves are quoted rather than picked off a price list, so there is no public price page to compare against.

Next steps

For what a project includes, see Plans and pricing. For the tasks themselves, see Running a task and reviewing the result.

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

Previous Running a task and reviewing the result Next Plans and pricing

Still stuck? Open a ticket from the app or talk to an engineer.