Skip to Content

Approving expensive runs

How CodeLynq estimates what a run will cost, and how spend limits make expensive runs wait for an admin's approval.

Runs use AI models, and what a run costs depends on the size of the task. To keep that predictable, CodeLynq estimates the cost of a run before it starts, and your organization can decide what happens to expensive ones.

The cost estimate

Before a run starts, CodeLynq estimates its cost from what comparable runs in the same project actually cost. On the task's Runs tab you see a rough per-run figure next to Trigger New Run, in the same currency and on the same basis as the approval.

A new project has no history yet, so there is no estimate - and a run is never held back by a number CodeLynq does not have.

Spend limits

An organization admin sets the limits under Settings → Usage & billing → Spend limits:

  • Runs freely up to - runs estimated above this amount wait for approval.
  • Never more than - per run. A run estimated above this is refused.
  • Per month - the total across every project. When this month's spend reaches it, new runs are refused until next month or until the limit is raised.

Leave a field empty for no limit; all three are empty unless an admin sets them. Click Save limits. A bar shows how much of the monthly limit has been used.

Members who are not admins can see the limits but not change them. When your organization uses its own AI provider key, spend limits are not shown.

When a run waits for approval

A run estimated above Runs freely up to does not start. Its status is Needs approval, and on the run you see This run is waiting for approval with the estimated amount. Nothing has started, and nothing has been charged. The run also appears in the Inbox.

An organization admin or the project's owner decides:

  • Approve and run - the run is queued and starts as usual. The limits are checked again at that moment: if the monthly limit was reached in the meantime, the run cannot start.
  • Don't run it - the run is cancelled. The task stays approved, so you can split it into smaller tasks or start a new run later.

You can also approve or decline a held run in the mobile app.

When a run is refused

A run above Never more than, or any run once the Per month limit is reached, does not start at all. You see the reason straight away when you click Trigger New Run. Ask an admin to raise the limit, or make the task smaller.

Credit and plan limits

Separately from spend limits, a run also needs model credit and an active plan:

  • When the organization's credit is used up, new runs do not start until it is topped up. Runs already in progress finish.
  • Your plan sets how many runs you can do per month and how many can run at the same time.

See Billing and credits. For what was spent per project and per task, see Analytics and costs.

Tips

  • Set Runs freely up to to an amount that covers your everyday tasks, so only the unusual ones need a decision.
  • A task that keeps needing approval is often too large. Splitting it - or turning it into an epic - gives better pull requests as well as smaller bills.

Test it on a task from your own backlog

Send us one real task. We run CodeLynq on your repository and you review the pull request. Free, within 5 working days of approving the spec.