Assistant model and capability setup
Version: 2026-10-14.9. Read after selecting For agents and before starting the customer's workflow.
Use the strongest generally available model on your host with High or higher reasoning for filmmaking and editor work. For OpenAI Codex, Ruliad recommends GPT-6 Astra with High reasoning when available. This is a product operating recommendation; production acceptance is established by completed tool and UI tests, not the model name.
In Codex desktop, select the model and reasoning control beneath the composer. In Codex CLI, use /model to select the model and effort; CLI model selection alone does not provide browser control. Availability depends on the account, client and workspace. Read https://learn.chatgpt.com/docs/models for current controls.
Claude, Grok, Muse, Instinct, Dot, Town and Hark: use the strongest actual model and higher reasoning setting your host exposes. Do not invent model names or hidden controls. If a setting is unavailable or cannot be changed within the session, tell the customer the actual setting and continue supported work. Ask for a settings change only when that missing capability blocks the requested operation.
Verify the actual selected model, reasoning effort and browser-control capability before the first workflow action, and report them in a short setup note. Where the host does not expose its model, report model not exposed. Never claim a model switch merely because a prompt requested it. Ruliad cannot silently change a visiting assistant's host settings.
The visiting assistant's model and Ruliad MAIN's model are separate. Read MAIN's visible model control and any returned provider receipt to verify MAIN's actual model. If explicitly choosing Astra in MAIN, wait until its active turn completes, select Astra and High using the model control, and verify the selection. Preserve the customer's saved preference; do not pretend an external model choice also changed MAIN.
Preserve existing spending limits, current review decisions and host permission controls. Stronger reasoning does not authorize extra paid work, purchases, broader access or parallel generation. Capability setup is a short check, not a reason to repeat sign-in or start new projects.
First workflow action: open the Ruliad sidebar button, select MAIN/Ruliad and send the workspace check-in and exact task. New ads start at Production → Setup. Existing editor work opens the exact saved project. Close menus and inspect the actual visible controls before clicking. If browser control, a required tool or authentication is unavailable, report that specific limitation and the supported next step; never loop through unrelated menus.