GDevelop AI Agent

Current project context, actions, Auto edit, restore points, dynamic usage, failure handling, and AI privacy statements.

Official description of the in-editor Agent and the need to split and review complex tasks.

Current plan allowances, publishing benefits, and company eligibility. Paid prices are loaded dynamically.

Active default-region USD records used for the September 6, 2026 pricing snapshot.

General-credit uses; the exact conversion into the weekly AI allowance is not published.

Engine license, user responsibilities, service changes, and general legal boundaries. Not legal advice.

General privacy disclosures; the AI documentation supplies additional product-specific statements.

Official open-source repository and MIT export boundary. The hosted AI service itself is not established as open source.

Commercial derivative use and restrictions on redistributing assets themselves.

Version and repair timeline checked September 6, 2026; release notes do not prove every service incident is resolved.

A GDevelop team reply confirms the Agent cannot currently read external events, extensions, or custom-object events.

Official explanation for older third-party prices that no longer match new subscriptions.

Pro-plan requirement for qualifying company or client revenue/funding scenarios.

Current cancellation timing; a general refund window was not found.

An open community contribution, not a released BYOK or local-model capability.

A creator with two to three years of GDevelop use describes AI-assisted prototypes and four exported casual games; the Agent's exact share is unknown.

An art-background user reports help with math and first mechanisms alongside extensive rework. Their percentage is not generalized.

A time-series account combines earlier useful builds with later failed edits and repeated credit use.

A programmer reports that vague debugging guesses missed a concrete expression error.

A user says a few requests exhausted available credits without reaching the target, motivating a switch and a BYOK request.

A bounded 60-second timer task reached variable creation but not event writing during a confirmed service incident.

A single thread contains both dissatisfaction and successful iterative use, showing how task scope and supervision change outcomes.

A current-version incident report with corroborating users and a team investigation; later release notes do not establish complete recovery.

A lower-weight reputation and disclosure signal, not evidence about technical quality.

A learner reports failed external-event work and credit friction while still finding condition and action discovery useful.

A modular-project user reports the Agent can see references but not the external contents it needs to debug.

Multiple users report repeatable event-writing failures across Web and desktop; counted as one incident group.

A recent paid-user report of lost credits and inaccessible history, paired in the review with the founder's partial-fix reply.

A specific annual-plan complaint reports 500-plus credits spent on one movement issue. It does not represent support overall.

A current visible mobile review describes confusion and quickly exhausted credits; the page does not expose a reliable year.

A concrete user request for provider, cost, privacy, and data-residency control. A request is not a released interface.

A user with Web-programming experience says the event page remained learnable after AI credits ran out. This supports manual fallback, not Agent quality.

A lower-specificity cross-engine signal that beginners value starter projects, next-step explanations, and in-context answers.