AI Wiz

AI Wiz is ioLoop's AI development assistant inside the Project Editor. Describe what you want to build or change in natural language, and AI Wiz can explain the Project, propose an approach, and create or modify supported Project components.

AI Wiz works with the Project's structured resources. Changes remain available through the corresponding Project Editor tools, so you can inspect the result, continue editing visually or with code, and return to AI Wiz for further refinement.

AI-generated results can be incomplete or incorrect. Review and test every change before publishing it or relying on it for important application behavior.

AI Wiz and AI Agents

AI Wiz and AI Agents serve different purposes:

Capability	Purpose
AI Wiz	Helps Creators develop and maintain a Project from within the Project Editor.
AI Agents	Provide AI-powered functionality that you build into the application for Project Users, visitors, or automated workflows.

AI Wiz can help configure supported parts of an existing AI Agent, but it does not become part of the published application. Application users do not interact with your AI Wiz development chats.

For application-facing AI behavior, see AI Agents.

Opening AI Wiz

To open AI Wiz:

1. Open a Project in the Project Editor.
2. Select AI Wiz at the bottom of the editor.

AI Wiz opens in a floating window. You can move or resize the window, maximize it when you need more room, and close it without leaving the current editor area.

AI Wiz can use the currently open editor resource as context. For example, opening AI Wiz while working with a Page, Database table, Cloud Flow module, AI Agent, or Code asset helps establish what you are currently editing.

Current editor context reduces ambiguity, but it does not replace a clear request. Include the target resource's name when the Project contains similarly named or related components.

What AI Wiz Can Help With

AI Wiz can assist with many development tasks across supported Project resources. Examples include:

• Create and modify Pages, Forms, layouts, Page Flow, and frontend code.
• Create and modify Database tables, fields, named queries, access settings, and supported development data.
• Create and configure Cloud Flow modules and their workflow logic.
• Create or modify JavaScript and CSS Code assets.
• Configure supported properties, access settings, flows, and Knowledge Sources for existing AI Agents.
• Adjust supported Project-wide settings, fonts, HTML head content, CSS, and asset inclusion.
• Explain existing components and help investigate problems or refine an implementation.
• Coordinate a feature that requires changes across multiple supported parts of the Project.

AI Wiz does not operate every Project Editor control. If a requested operation is unsupported, complete that part directly in the appropriate editor area.

Writing Effective Requests

A useful request states the intended result, identifies the relevant resources, and includes important constraints.

For example:

Create a contact Form named SupportRequest. Store the subject, message, category, and signed-in username in a new Database table. Validate the required fields and show a success message after submission.

For an existing component, describe what should remain unchanged:

Update the Orders Page so the status filter appears above the table. Keep the existing table, Page Flow behavior, access settings, and mobile layout.

For larger work, ask AI Wiz to proceed in reviewable stages. A useful sequence is:

1. Describe the feature and its intended users.
2. Ask AI Wiz to explain the proposed components.
3. Request the first bounded set of changes.
4. Review and test the result.
5. Continue with the next part of the feature.

Include relevant security, validation, responsive-design, and error-handling requirements in the request. Do not assume AI Wiz will infer application-specific business rules that were not provided.

Providing Additional Context

You can provide context in several ways:

• Continue in the same chat when a request builds on earlier work.
• Open the relevant resource in the Project Editor before submitting the request.
• Attach a Screenshot of editor when the visible design or current editor state is important.
• Select files from your device.
• Paste or drag files into the AI Wiz prompt area.

Review attachment names before sending the prompt. Remove any attachment that is not needed.

Do not include passwords, API keys, Web Hook Keys, access tokens, or other credentials in prompts, screenshots, or attachments. Avoid providing sensitive application data unless it is necessary and appropriate for the task.

Reviewing and Allowing Actions

AI Wiz can respond with guidance, generated content, or actions that modify the Project. The action permission setting determines whether generated actions require confirmation.

Setting	Behavior
Always ask	AI Wiz waits for you to select Allow this turn or Reject before executing generated actions.
Always allow	AI Wiz can execute generated actions without requesting confirmation for each turn.

Use Always ask when you want to review each proposed action set. This is especially useful for multi-resource changes, access settings, Database structure, Cloud Flow, and existing application behavior.

Use Always allow only when you are comfortable allowing subsequent AI Wiz requests to make supported changes without per-turn confirmation. You can change the setting again before another request.

When permission is requested:

• Select Allow this turn to execute the proposed actions.
• Select Reject to leave those proposed actions unexecuted.

AI Wiz displays progress while it performs approved actions. Do not refresh or close the editor while actions are executing.

Multi-Step Changes and Errors

AI Wiz may use multiple actions to complete one request, and an individual action can fail during execution.

If an action fails, later actions in that sequence may not run. Earlier actions may already have completed, so an error should not be treated as an automatic rollback.

After an error:

1. Read the action result and identify where processing stopped.
2. Inspect the affected resources in the Project Editor.
3. Confirm which changes completed successfully.
4. Correct any prerequisite or invalid configuration.
5. Ask AI Wiz to continue only with the remaining work, or complete it directly in the editor.

You can stop a running prompt from the AI Wiz window. Stopping a prompt prevents it from continuing, but it does not undo Project changes that already completed.

For a recoverable point before substantial development work, consider creating a Checkpoint. Checkpoint limitations still apply, including the treatment of Database data and Media.

Operations AI Wiz Does Not Perform

Deleting Project resources

AI Wiz does not delete Project resources. When a resource must be deleted, perform the deletion directly in the appropriate Project Editor area after reviewing its dependencies and downstream effects.

Deleting an AI Wiz chat is different. It removes that development conversation from Chat History; it does not delete Pages, tables, flows, assets, or other Project resources.

Creating Connections and Profiles

AI Wiz does not create Connections or their authentication Profiles. These can require service-specific credentials, authorization, provider accounts, and choices that must be completed by a Creator under Integrations.

Create and authorize the required Connection and Profile yourself. After the Connection is available, AI Wiz can help build supported Page Flow, Cloud Flow, code, or AI Agent behavior that uses it.

Never provide Connection credentials to AI Wiz as a substitute for configuring them through the appropriate Integration controls.

For setup and credential guidance, see Connections.

Publishing the Project

AI Wiz does not publish the Project. Its changes are development changes and follow the normal save, Preview, testing, and publishing lifecycle.

After using AI Wiz:

1. Inspect the affected components.
2. Preview and test representative behavior.
3. Verify access rules and denied cases where applicable.
4. Test external integrations with the intended accounts and environments.
5. Publish the Project when the changes are ready.
6. Launch and verify the published application.

See Publish for the release workflow.

Bypassing permissions

AI Wiz does not expand a Creator's Project permissions. Generated actions must still be allowed by the Creator's assigned access. A Viewer cannot use AI Wiz as a way to gain write access, and publishing still requires the applicable publishing permission.

Creator permissions are separate from the Users and User Groups configured for the published application. See Creators, Users, and User Groups.

Models and Reasoning

AI Wiz provides model and reasoning controls for each request.

The available model choices are:

• Ion
• Vector
• Nova
• Apex

The models available to select depend on the account's plan. An unavailable model appears locked and requires an eligible plan.

The reasoning choices are:

Level	General use
Low	Straightforward questions and focused changes.
Medium	General development work and requests involving several considerations.
High	Complex planning, investigation, or coordinated changes across multiple components.

A higher reasoning level does not remove the need to review the result. Choose a level appropriate to the task and refine the request if the output is too broad or does not account for an important constraint.

HyperBoost requests faster AI responses. Its availability depends on the account's plan, and the control appears locked when it is unavailable.

Credits and Usage

AI Wiz requests consume AI Wiz credits. The remaining credit balance appears in the AI Wiz window.

Select the credit balance to review AI Wiz credit usage for the previous seven days. Individual AI Wiz responses can also display the credits used for that response.

The selected model, reasoning level, request complexity, context, attachments, and response can affect usage. If no credits remain, AI Wiz cannot start another request until additional credits are available. Use Buy Credits from the displayed notice when additional credits are needed.

For account-level plan and billing management, see Billing.

Managing Chats

AI Wiz maintains Chat History so that you can return to earlier development conversations.

From the AI Wiz window, you can:

• Start a new chat.
• Open Chats to view Chat History.
• Switch between chats.
• Rename the current chat.
• Refresh the current conversation.
• Delete a chat you no longer need.

Use the same chat for related follow-up work because the earlier conversation can provide useful context. Start a new chat when moving to an unrelated feature or investigation.

Deleting a chat removes the conversation itself. It does not reverse actions from that chat or remove any Project resources that were created or modified while using it.

Review Checklist

Before considering AI-assisted work complete:

• Inspect every affected Project resource.
• Confirm names, references, and dependencies.
• Review generated JavaScript, CSS, and Custom Code.
• Test success, validation, error, and denied-access paths.
• Verify responsive behavior for affected Pages and Forms.
• Confirm Database structure and development data are appropriate.
• Confirm external operations use the intended Connections and provider accounts.
• Create or update supporting application documentation where needed.
• Publish and verify the application when the changes are ready for users.

Treat AI Wiz as a development collaborator, not as a substitute for application ownership, security review, testing, or release verification.

Related Topics

• Project Editor
• Frontend
• Backend
• AI Agents
• Connections
• Checkpoints
• Publish