Credits and settings

What credits cover

Only requests explicitly routed to Iterel Cloud · Claude or Iterel Cloud · GPT consume managed text-generation credits. Image generation and composer voice follow their specialized accounting. The composer labels credit-funded choices before a run starts.

What uses your own plan

Claude Code, Codex, Cursor, and other connected engines run tasks and guided capabilities through their CLI authentication on your Mac. Iterel does not convert a ChatGPT or Claude consumer session into a hidden third-party API token, and it never falls back to credits silently.

Free local and cloud allowance

Free includes unlimited machine-local projects plus one active collaborative cloud project. Local rounds use the user's connected engine and create no normal Iterel-funded model cost. Managed generation uses atomic reservations and a budget firewall; when a paid path is unavailable, Iterel fails honestly or selects a deterministic/connected-engine path permitted by the request rather than hiding spend.

Settings boundaries

• App settings — account, appearance, credits, machine Build engines, provider keys, and preferred IDE.
• Project settings — workspace defaults, project design system, members, and exact product-integration bindings.

These settings are reached from the account footer and project row; they are not top-level making modes.