Prepare a new submission with LEGA
Chat, clarify, review, apply, undo, and understand what is shared with the assistant.
LEGA is an AI assistant for preparing new submissions. It is available in new custom and Quick submission forms and the Quick catalog. It does not control a running job or modify existing results. An Edit or permitted public-copy action may open a new-submission form; changes there create a new child submission, not an edit to the original run. Problem Builder and continuation dialogs use their own workflows.
Access¶
LEGA requires an active Premium subscription, an active trial, or granted premium access. Credits alone do not unlock the agent. LEGA does not currently deduct credits or charge per conversation. The platform checks access again when starting preparation or applying settings; expired access cannot be bypassed by leaving a tab open.
Free users still see the floating button. Opening it displays a Premium information modal with Cancel and Subscribe. Manual submission forms, drafts, and reading your existing conversation history remain available under their normal limits.
Open the assistant¶
The floating original B agent logo stays available as you scroll. On desktop, click to open; hover reveals its small close button. On mobile, the first tap reveals the close button and the second tap opens the assistant. Tap elsewhere to reset the first-tap state. Keyboard activation opens it directly. Feedback uses the same interaction.
A brief combined greeting plays on desktop hover, on the first mobile tap, and when the overlay opens: the eyes glance and blink, the antenna and star sparkle, and light travels along the chromosome. The head stays still. It does not run continuously. Your device's reduced-motion preference disables the animation.
The overlay shows the LEGA name and logo above the conversation. Close the overlay with X or the shaded area outside it. On narrow screens it fills the width, so use X. Hiding the floating launcher hides it for this page view only; it returns on a fresh page load.
Describe and clarify¶
- Describe your goal, variables, allowed values, and constraints in Message LEGA.
- Choose Send, or press Enter. Shift+Enter inserts a new line.
- Answer clarification questions in a new message. Earlier descriptions and questions are included in follow-ups.
- Review the reply at the bottom of the conversation.
After every message you send, LEGA shows its animated logo while preparing the reply. The animation continues until the reply, cancellation, or error arrives, then the same message becomes the response. Every LEGA message has its logo beside the name. If you close the chat while a reply is pending, the floating LEGA button keeps animating until the request finishes. Reopening the chat preserves the conversation. Reduced-motion preferences keep the waiting logos still.
The composer clears immediately when you send a message, on mobile and desktop. If sending fails, the text is restored unless you have edited the composer since sending. Text you type while a request is pending is kept. The composer grows to a limit, then scrolls internally for long messages. You can write the next message while preparation is in progress; Send is disabled until it finishes. Stop requests cancellation. Cancellation and failures remain visible in the conversation.
New replies scroll into view. While you read earlier content, progress updates offer Jump to latest message. Copy copies a message, including proposal text and code inside collapsed details. You can also select text normally.
Review and apply¶
Expand View proposed changes and details to inspect assumptions, fitness previews, field values, and reasons. Select the changes you want, then choose Approve & apply to form. You do not need to send an “Approved” message. Request changes focuses the message box so you can explain what to revise. The reply explicitly states that settings have not been applied yet; after application, View updated form closes the chat so you can check the filled form. If no changes are proposed, LEGA says that there is nothing to apply rather than asking for approval. Unresolved questions or validation issues prevent application. Earlier proposals stay readable, with their controls disabled once replaced.
If a proposal fails host validation, LEGA automatically tries one correction using the previous proposal and the reported issues. Both passes share the original time limit and model budget; a correction is skipped if accounting is unavailable or the budget is exhausted. The waiting animation continues during correction. LEGA is instructed to preserve your requirements and ask a clarification question with alternatives when a decision is needed. Questions stop automatic correction.
If issues remain, Retry correction requests another preparation attempt, or Request changes lets you give your own instructions. For an incomplete starting population, Use automatic population remains a shortcut to request PyGAD initialization within the proposed gene limits. These actions return a proposal for approval; they never apply or submit it. Unsent composer text is preserved. Cancellation or provider unavailability stops correction without switching to paid API access.
Applying changes updates the new-submission form only. It does not start optimization or submit a run. The form's ordinary Submit action still checks validity, confirmations, access, and usage limits.
Changes made manually after preparation are protected by conflict checks. Undo applied changes restores the last applied values where possible and keeps newer manual edits. For Quick submissions, existing builders still derive fitness and gene settings from problem inputs. Unsupported problem details may need clarification, custom code, or another form. A suggested form opens in a new tab.
Privacy, retention, and limits¶
Use the info icon for instructions and Current form context. LEGA receives your descriptions, clarification context, problem type, and form values you explicitly edited, including code entered there. Untouched form defaults stay in Vilvik for conflict checking but are not sent as requirements. Edited values are context rather than immutable constraints; an explicit conversation instruction may replace them. If you omit an objective-evaluation budget or ask LEGA to decide, Vilvik supplies a preparation ceiling of 110 evaluations so the assistant does not ask you to invent one. Custom data attachment contents and unrelated account data are not sent. Do not include secrets in descriptions or code.
Vilvik uses LEGA's minimum preparation workflow: intake, Parser, and GALA prepare the proposal without the full workflow's Critic review gates or running an optimization. Vilvik automatically sends host-validation errors back for one bounded correction attempt. Documentation checks, field mapping, and the mechanics of applying a proposal are internal concerns and are not shown as questions for you. A clarification is shown only when LEGA still needs a problem-domain fact or a meaningful preference from you.
The displayed chat stays in the page when you close and reopen the overlay. Sent messages and results are also saved privately in LEGA conversations, accessible from the left sidebar or the history icon in the overlay. Submission drafts are separate. Unsent text is not saved to conversation history. Refreshing or leaving with unfinished progress still warns you; browser refresh/close controls may use a native warning. Starting the prepared submission is an intentional completion action and does not show that warning. If submission fails, the warning is restored while your form and conversation remain on the page.
Preparation context is limited to 16,000 characters, including earlier messages and clarification questions. If it exceeds that limit, your unsent message is kept so you can shorten it. Only one LEGA request can run per account at a time. If another tab has an active request, View conversation opens its history and Cancel previous request lets you stop it. You can then send the message from your current chat. Expired or abandoned requests are cleared automatically when you start a new request, so they cannot block the account indefinitely. Sessions also have server-side revision and daily limits; an error explains when one is reached. A fresh page starts a new conversation, so save the submission form and copy any chat text you need first.
When LEGA is unavailable¶
The panel says LEGA is unavailable at this time and disables Send. Choose Try again later. Expired authentication, subscription limits, or service interruptions can cause this state. There is no automatic switch to paid API access. Your existing form and draft controls remain usable.
Saved conversations and reuse¶
Open LEGA conversations to browse your history and read every recorded user message and agent response. Expand proposed settings to inspect or select and copy code. History remains readable if your trial or premium access ends.
Past messages and proposals are read-only. Choose Reuse in new submission on a turn to start a separate branch, preserving the original conversation. The new form shows the saved conversation and rebases its proposed changes against the current form values. Review the selected changes before applying; normal validation and manual-edit conflict checks still apply. Reuse itself makes no provider request. Sending a follow-up does.
Each turn lists submissions created with it as their most recently applied source, including new submissions from branched conversations. Applying a later turn replaces the pending source association. Applying does not itself create a submission. The form remains editable, so a linked submission may include later manual edits. Undo removes that pending association. This provenance starts with this feature; older submissions cannot be linked retrospectively with certainty.
Older conversations may contain only their last retained request and response, since earlier turns were not stored separately before this feature. New conversations retain each sent turn. A new branch links back to its source turn. Files are not copied through conversation history: select any required attachments on the new form.